subnet.im

177.3.93.0/24

At a glance

Addresses

256

/24 block

Visibility

75%

60 of 80 vantage points

RPKI

Valid

Registry

APNICHK

Allocated 13th March 2025

AS paths to this prefix

One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.

  1. Oregon, US1375354006181400969886693920130This path
  2. Amsterdam1375354006181400969886291434549213151This path
  3. London, UK1375354006181400969886291464538529This path
  4. Singapore137535400618140096988629148966132337This path

Each row is one path genuinely present in the routing table at our last snapshot, read outward from the origin to the vantage point that saw it. Open a row to follow that one path hop by hop. A heavier line in the graph means more vantage points reach the prefix that same way.

Route visibility

75%

Seen by 60 of 80 full-feed vantage points

Partially propagated

Observed at 5 of our collectors.

What this percentage counts

The denominator counts only full-feed peers — peers carrying a substantially complete routing table at the moment of the snapshot. IXP route-server peers usually feed partial tables and are excluded, because including them would make a normally propagated prefix look as though half the internet could not see it.

It measures how widely an announcement has spread across the networks we can observe. It says nothing about whether the prefix is reachable from any particular place, or how it performs.

Registry and RPKI

RIR
APNIC — Asia-Pacific
Country
Hong Kong SAR China
Allocated
13th March 2025
Allocation block
177.3.80.0/20
Status
allocated
Origin validation
Valid

A ROA exists that authorises this origin AS to announce this prefix at this length.

ROAs covering this prefix

Route Origin Authorisations covering 177.3.93.0/24
ROA prefixAuthorised originMax length
177.3.88.0/21AS137535/24
177.3.88.0/21AS140227/24
177.3.88.0/21AS153517/24
177.3.88.0/21AS395886/24
177.3.88.0/21AS40115/24
177.3.88.0/21AS7607/24
177.3.88.0/21AS8796/24

Prefix hierarchy

Announcements above, below and beside this one in the real routing table.

CoveringMore specific
Prefix hierarchy for 177.3.93.0/24: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.177.3.92.0/23AS140227177.3.92.0/22AS137535177.3.92.0/24AS137535177.3.93.0/24AS137535This prefix177.3.92.0/24AS140227

Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.

Covering announcements

Announcements that contain 177.3.93.0/24
PrefixAddressesOriginVisibility
177.3.92.0/23512AS140227Hong Kong Communications International Co., Limited4/80
177.3.92.0/221kAS137535JT TELECOM INTERNATIONAL PTE.LTD.77/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

Prefixes of the same length sharing a parent block with 177.3.93.0/24
PrefixAddressesOriginVisibility
177.3.92.0/24256AS137535JT TELECOM INTERNATIONAL PTE.LTD.60/80
177.3.92.0/24256AS140227Hong Kong Communications International Co., Limited1/80

History

  1. AS14022712th August 2026 present
  2. AS13753512th August 2026 present
Why these dates start where they do

A first-seen date is the first time we saw that origin, not the first time it appeared in BGP. Our history is forward-only with no backfill, so it says nothing about the period before we started collecting — treat the earliest dates with suspicion.

Open 177.3.93.0/24 in the calculator/24 reference

Routing data derived from RouteViews MRT archives and public registry data.