2a0f:85c1:d37::/48
AS212895 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Subnets
/48 block
Visibility
61 of 63 vantage points
RPKI
Registry
GBAllocated 15th November 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Sao Paulo.
Seen from Sao Paulo
- Peer of AS204994seen on 58 paths from 58 vantage points
- Peer of AS212895seen on 11,172 paths from 72 vantage points
- Peer of AS6939seen on 303,463 paths from 6 vantage points
DE
US
FROne 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
- Amsterdam2049942128958298This path
- London, UK20499421289535280This path
- Sao Paulo204994212895693935280Shown above
- Singapore2049942128956939132337This 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
97%
Seen by 61 of 63 full-feed vantage points
Globally propagatedObserved at 4 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
- 15th November 2019
- Allocation block
- 2a0f:85c0::/29
- 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 |
|---|---|---|
| 2a0f:85c1:d37::/48 | AS204994 | /48 |
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 |
|---|---|---|---|
| 2a0f:85c1:d36::/48 | 65.5k × /64 | AS205018Irsyad Khoirul Anwar | 62/63 |
History
- AS20499412th August 2026 — present
- AS20953310th November 2026 — present
- AS2128951st November 2026 — 10th November 2026
- AS2095331st November 2026 — 1st November 2026
- AS21289529th October 2026 — 31st October 2026
- AS20953328th October 2026 — 28th October 2026
- AS21289520th October 2026 — 28th October 2026
- AS20953320th October 2026 — 20th October 2026
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.
Routing data derived from RouteViews MRT archives and public registry data.