SUBNET.IM

202.128.74.0/23

At a glance

Addresses

512

/23 block

Visibility

31%

25 of 80 vantage points

RPKI

No ROA

Registry

APNICGU

Allocated 3rd June 1999

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.

OriginVantage points
  1. London, UK36051374098529This path
  2. Singapore36056939132337This path
  3. Oregon, US3605693920130This path
  4. Sao Paulo36057195262355266213This path
  5. Amsterdam360569395829941051213151This 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

31%

Seen by 25 of 80 full-feed vantage points

Seen by few vantage points

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
Guam
Allocated
3rd June 1999
Allocation block
202.128.64.0/19
Status
allocated
Origin validation
No ROA

No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.

Prefix hierarchy

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

CoveringMore specific
Prefix hierarchy for 202.128.74.0/23: the announcements covering it on the left, the announcements inside it on the right. Every prefix drawn is also listed in the tables below.202.128.64.0/20AS3605202.128.64.0/19AS3605202.128.74.0/23AS3605This prefix

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 202.128.74.0/23
PrefixAddressesOriginVisibility
202.128.64.0/204.1kAS3605Guam Cablevision, LLC.25/80
202.128.64.0/198.2kAS3605Guam Cablevision, LLC.79/80

More specific announcements

Nothing inside this block is announced separately.

Sibling prefixes

No prefix of the same length in the same parent block is announced.

History

  1. AS360512th 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 202.128.74.0/23 in the calculator/23 reference

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