202.128.0.0/20
At a glance
Addresses
/20 block
Visibility
25 of 80 vantage points
RPKI
Registry
GUAllocated 12th May 1994
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS3605seen on 225 paths from 25 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
US
SGOne path, hop by hop, from the origin outward to the vantage point that saw it. Counts beside each step are how often we see that pair adjacent anywhere in the table, not how often this path was used — BGP carries no traffic figures.
Every path we see
- London, UK36051374098529This path
- Singapore36056939132337Shown above
- Oregon, US3605693920130This path
- Sao Paulo36057195262355266213This path
- 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 pointsObserved 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
- 12th May 1994
- Allocation block
- 202.128.0.0/19
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
Prefix hierarchy
Announcements above, below and beside this one in the real routing table.
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
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 202.128.0.0/19 | 8.2k | AS3605Guam Cablevision, LLC. | 79/80 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 202.128.16.0/20 | 4.1k | AS3605Guam Cablevision, LLC. | 25/80 |
History
- 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.0.0/20 in the calculator/20 reference
Routing data derived from RouteViews MRT archives and public registry data.