2404:e280:1::/48
At a glance
Subnets
/48 block
Visibility
52 of 62 vantage points
RPKI
Registry
CNAllocated 26th April 2016
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 AS58866seen on 209 paths from 67 vantage points
- Peer of AS56048seen on 63,193 paths from 142 vantage points
- Peer of AS9808seen on 3,373,300 paths from 142 vantage points
- Peer of AS58453seen on 661,390 paths from 44 vantage points
- Peer of AS3356seen on 232,620 paths from 2 vantage points
HK
USOne 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
- Amsterdam58866560489808584536939213151This path
- Sao Paulo5886656048980858453335632590Shown above
- Singapore58866560489808584536939132337This path
- London, UK588665604898085845333561557651907This 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
84%
Seen by 52 of 62 full-feed vantage points
Partially 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
- China
- Allocated
- 26th April 2016
- Allocation block
- 2404:e280::/32
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 2404:e280::/48 | 65.5k × /64 | AS58866China Financial Certification Authority | 52/62 |
History
- AS5886612th 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.