88.80.137.0/24
At a glance
Addresses
/24 block
Visibility
75 of 76 vantage points
RPKI
Registry
BGAllocated 29th November 2005
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS23061seen on 831 paths from 75 vantage points
- Peer of AS17404seen on 3,875 paths from 76 vantage points
- Peer of AS49581seen on 61 paths from 4 vantage points
- Peer of AS23764seen on 30,201 paths from 2 vantage points
US
DE
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
- Amsterdam2306117404495818298This path
- London, UK230611740449581445928529This path
- Singapore2306117404495812376423673Shown above
- Sao Paulo230611740449581445926204645335280This path
- Oregon, US2306117404495814459233891855142013This 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
- Bulgaria
- Allocated
- 29th November 2005
- Allocation block
- 88.80.128.0/20
- 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 |
|---|---|---|
| 88.80.137.0/24 | AS23061 | /24 |
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 |
|---|---|---|---|
| 88.80.136.0/24 | 256 | AS212238Datacamp Limited | 76/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 88.80.137.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.