2a0d:b287:da01::/48
At a glance
Subnets
/48 block
Visibility
15 of 62 vantage points
RPKI
Registry
ITAllocated 26th February 2018
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS212539seen on 15 paths from 15 vantage points
- Peer of AS208437seen on 396 paths from 108 vantage points
- Peer of AS9002seen on 185,530 paths from 99 vantage points
- Peer of AS3356seen on 1,045 paths from 32 vantage points
- Peer of AS6461seen on 8,292 paths from 13 vantage points
- Peer of AS7473seen on 4,810 paths from 9 vantage points
- Peer of AS8966seen on 133,632 paths from 2 vantage points
GB
US
SG
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, UK21253920843790023356646182183428851907This path
- Singapore21253920843790023356646174738966132337Shown above
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
24%
Seen by 15 of 62 full-feed vantage points
Seen by few vantage pointsObserved at 2 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
- Italy
- Allocated
- 26th February 2018
- Allocation block
- 2a0d:b280::/29
- 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.
Left to right is specificity: a shorter mask covering more address space, then this prefix, then the announcements carved out inside it. Only the first few of each are drawn — the tables below list them all.
Covering announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a0d:b280::/29 | 34.4B × /64 | AS41720Revolution Provider S.r.l. | 61/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a0d:b287:da00::/48 | 65.5k × /64 | AS215146Roberto Santo | 62/62 |
History
- AS21253912th 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.
Routing data derived from RouteViews MRT archives and public registry data.