2.26.12.0/24
Ace Data Centers II, L.L.C.AS401152
Announced by more than one origin AS (MOAS).
At a glance
Addresses
/24 block
Visibility
56 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 AS199180seen on 203 paths from 118 vantage points
- Peer of AS58212seen on 13,624 paths from 57 vantage points
- Peer of AS6453seen on 76,461 paths from 2 vantage points
AM
DE
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
- London, UK1991805821264538529Shown above
- Sao Paulo19918058212645335280This path
- Amsterdam199180582126453250918298This path
- Singapore401152117986461335623673This path
- Oregon, US1991805821232571299855142013This 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
74%
Seen by 56 of 76 full-feed vantage points
Partially 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.26.12.0/24 | AS199180 | /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.26.13.0/24 | 256 | AS199180Lagom Products LLC | 56/76 |
| 2.26.13.0/24 | 256 | AS401152Ace Data Centers II, L.L.C. | 19/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.26.12.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.