82.47.26.0/24
At a glance
Addresses
/24 block
Visibility
81 of 81 vantage points
RPKI
Registry
GBAllocated 31st January 2003
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS402628seen on 1,661 paths from 144 vantage points
- Peer of AS36530seen on 2,833 paths from 143 vantage points
- Peer of AS17433seen on 9,205 paths from 144 vantage points
- Peer of AS137409seen on 7,188 paths from 2 vantage points
US
HK
AU
CHOne 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
- Singapore40262836530132337This path
- Oregon, US40262836530693920130This path
- Amsterdam40262836530174331374098298Shown above
- London, UK4026283653017433896635280This path
- Sao Paulo402628365301743313740935280This 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 81 of 81 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 Kingdom
- Allocated
- 31st January 2003
- Allocation block
- 82.47.0.0/16
- Status
- allocated
- Origin validation
- Valid
A ROA exists that authorises this origin AS to announce this prefix at this length.
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 |
|---|---|---|---|
| 82.47.27.0/24 | 256 | AS3320Deutsche Telekom AG | 81/81 |
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 82.47.26.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.