2001:3a0:f006::/48
At a glance
Subnets
/48 block
Visibility
62 of 62 vantage points
RPKI
Registry
JPAllocated 17th March 2003
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS38644seen on 126 paths from 126 vantage points
- Peer of AS7521seen on 2,540 paths from 141 vantage points
- Peer of AS55391seen on 271 paths from 29 vantage points
- Peer of AS6939seen on 320,794 paths from 2 vantage points
US
SGOne 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
- Amsterdam386447521553916939213151This path
- Singapore386447521553916939132337Shown above
- London, UK386447521553912914900251907This path
- Sao Paulo3864475215539129141295632590This 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 62 of 62 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
- APNIC — Asia-Pacific
- Country
- Japan
- Allocated
- 17th March 2003
- Allocation block
- 2001:3a0:8000::/33
- 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 |
|---|---|---|---|
| 2001:3a0::/32 | 4.3B × /64 | AS7521INTERNET MULTIFEED CO. | 62/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2001:3a0:f007::/48 | 65.5k × /64 | AS131079INTERNET MULTIFEED CO. | 62/62 |
History
- AS3864412th 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.