166.0.97.0/24
At a glance
Addresses
/24 block
Visibility
77 of 77 vantage points
RPKI
Registry
USAllocated 10th July 2012
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS213840seen on 1,132 paths from 77 vantage points
- Peer of AS1002seen on 2,765 paths from 77 vantage points
- Peer of AS137409seen on 16,570 paths from 6 vantage points
GB
AU
FROne 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
- Amsterdam21384010021374098298This path
- London, UK21384010021374098529This path
- Sao Paulo213840100213740935280Shown above
- Singapore213840100213740923673This path
- Oregon, US2138401002137409693920130This 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 77 of 77 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
- 10th July 2012
- Allocation block
- 166.0.0.0/15
- 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
No prefix of the same length in the same parent block is announced.
History
- AS21384025th September 2026 — present
- AS879620th October 2026 — 22nd October 2026
- AS879628th September 2026 — 28th September 2026
- AS879627th September 2026 — 27th September 2026
- AS879612th August 2026 — 26th September 2026
- AS21384023rd September 2026 — 24th September 2026
- AS748812th August 2026 — 21st September 2026
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 166.0.97.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.