2.27.72.0/23
At a glance
Addresses
/23 block
Visibility
76 of 76 vantage points
RPKI
Registry
USAllocated 21st September 2010
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS209604seen on 304 paths from 76 vantage points
- Peer of AS135523seen on 4,466 paths from 139 vantage points
- Peer of AS9260seen on 19,192 paths from 139 vantage points
- Peer of AS38193seen on 10,543 paths from 73 vantage points
TR
PK
AEOne 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
- Amsterdam2096041355239260381938298This path
- London, UK2096041355239260381938529Shown above
- Singapore20960413552392603819323673This path
- Oregon, US209604135523926038193855142013This path
- Sao Paulo209604135523926038193174645335280This 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
- RIPE NCC — Europe, Middle East, Central Asia
- Country
- United States
- Allocated
- 21st September 2010
- Allocation block
- 2.26.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 |
|---|---|---|
| 2.27.72.0/23 | AS209604 | /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 |
|---|---|---|---|
| 2.27.74.0/23 | 512 | AS207461HOSTING INDUSTRY LIMITED | 1/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 2.27.72.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.