2a0f:600:604::/46
At a glance
Subnets
/46 block
Visibility
62 of 63 vantage points
RPKI
Registry
JPAllocated 3rd September 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 AS51044seen on 209 paths from 73 vantage points
- Peer of AS57578seen on 892 paths from 139 vantage points
- Peer of AS210756seen on 6,566 paths from 137 vantage points
- Peer of AS12389seen on 86,343 paths from 81 vantage points
- Peer of AS3491seen on 82,475 paths from 47 vantage points
- Peer of AS6453seen on 652,531 paths from 6 vantage points
US
RU
HK
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
- Singapore5104457578210756123896939132337This path
- Amsterdam5104457578210756123893257250918298This path
- London, UK5104457578210756123893491129935280This path
- Sao Paulo5104457578210756123893491645335280Shown 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
98%
Seen by 62 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
- Japan
- Allocated
- 3rd September 2019
- Allocation block
- 2a0f:600::/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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2a0f:600:604::/47 | 131k × /64 | AS51044Kazuki Yamaguchi | 22/63 |
| 2a0f:600:604::/48 | 65.5k × /64 | AS51044Kazuki Yamaguchi | 14/63 |
| 2a0f:600:605::/48 | 65.5k × /64 | AS51044Kazuki Yamaguchi | 34/63 |
| 2a0f:600:606::/48 | 65.5k × /64 | AS51044Kazuki Yamaguchi | 30/63 |
| 2a0f:600:607::/48 | 65.5k × /64 | AS51044Kazuki Yamaguchi | 48/63 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS5104412th 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.