170.76.211.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 vantage points
RPKI
Registry
USAllocated 9th November 2017
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS54421seen on 46 paths from 46 vantage points
- Peer of AS20298seen on 285 paths from 97 vantage points
- Peer of AS13855seen on 2,911 paths from 116 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
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, UK54421612233568529This path
- Amsterdam5442120298138556939213151This path
- Sao Paulo5442120298138556939266213This path
- Singapore5442120298138556939132337Shown above
- Oregon, US544212029813855693920130This 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 80 of 80 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
- 9th November 2017
- Allocation block
- 170.76.211.0/24
- 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.
Covering announcements
No less specific announcement covers this prefix.
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
- AS5442112th 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 170.76.211.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.