187.97.174.0/24
At a glance
Addresses
/24 block
Visibility
75 of 76 vantage points
RPKI
Registry
VGAllocated 13th October 2009
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 AS17561seen on 326,137 paths from 76 vantage points
- Peer of AS17497seen on 291,977 paths from 134 vantage points
- Peer of AS174seen on 638,691 paths from 47 vantage points
- Peer of AS6453seen on 652,531 paths from 6 vantage points
HK
US
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
- London, UK175611749717412998529This path
- Sao Paulo1756117497174645335280Shown above
- Singapore1756117497174335623673This path
- Oregon, US1756117497174855142013This path
- Amsterdam17561174971746762250918298This 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
99%
Seen by 75 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- British Virgin Islands
- Allocated
- 13th October 2009
- Allocation block
- 187.96.0.0/15
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 187.97.174.0/24 | AS17561 | /24 |
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 |
|---|---|---|---|
| 187.96.0.0/15 | 131k | AS26615TIM S/A | 1/76 |
| 187.96.0.0/14 | 262k | AS26615TIM S/A | 1/76 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 187.97.175.0/24 | 256 | AS17561LARUS Limited | 75/76 |
History
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 187.97.174.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.