2.26.83.0/24
At a glance
Addresses
/24 block
Visibility
80 of 80 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 Amsterdam.
Seen from Amsterdam
- Peer of AS215439seen on 2,580 paths from 141 vantage points
- Peer of AS49581seen on 45,406 paths from 123 vantage points
- Peer of AS44592seen on 13,658 paths from 65 vantage points
- Peer of AS6453seen on 82,525 paths from 3 vantage points
- Peer of AS34549seen on 716,762 paths from 2 vantage points
GB
DE
NLOne 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, UK21543949581445928529This path
- Singapore2154394958144592132337This path
- Oregon, US2154394958144592693920130This path
- Amsterdam2154394958144592645334549213151Shown above
- Sao Paulo2154394958144592642893356266213This 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 80 of 80 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.26.80.0/21 | AS215439 | /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.82.0/24 | 256 | AS215439PLAY2GO INTERNATIONAL LIMITED | 80/80 |
History
- AS21543912th August 2026 — present
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.83.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.