160.202.84.0/24
At a glance
Addresses
/24 block
Visibility
76 of 76 vantage points
RPKI
Registry
USAllocated 2nd March 2016
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS64267seen on 7,752 paths from 76 vantage points
- Peer of AS62610seen on 61,891 paths from 139 vantage points
- Peer of AS21859seen on 12,706 paths from 121 vantage points
- Peer of AS3257seen on 222,667 paths from 32 vantage points
- Peer of AS3491seen on 86,410 paths from 2 vantage points
HK
KHOne 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, UK64267626102185912998529This path
- Sao Paulo642676261021859129935280This path
- Singapore6426762610218593257349123673Shown above
- Oregon, US6426762610218594229693920130This path
- Amsterdam64267626102185942296461250918298This 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
100%
Seen by 76 of 76 full-feed vantage points
Globally propagatedObserved 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
- ARIN — North America
- Country
- United States
- Allocated
- 2nd March 2016
- Allocation block
- 160.202.64.0/18
- 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.
Covering announcements
No less specific announcement covers this prefix.
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 160.202.85.0/24 | 256 | AS174Cogent Communications, LLC | 75/76 |
History
- AS6426722nd September 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 160.202.84.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.