2001:df2:4280::/48
At a glance
Subnets
/48 block
Visibility
63 of 63 vantage points
RPKI
Registry
BDAllocated 4th December 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Amsterdam.
Seen from Amsterdam
- Peer of AS139826seen on 139 paths from 139 vantage points
- Peer of AS139009seen on 3,209 paths from 110 vantage points
- Peer of AS58453seen on 6,437 paths from 2 vantage points
HK
CHOne 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
- Amsterdam139826139009584538298Shown above
- London, UK1398261390095845335280This path
- Singapore139826139009132602132337This path
- Sao Paulo13982613900958453423035280This 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 63 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
- APNIC — Asia-Pacific
- Country
- Bangladesh
- Allocated
- 4th December 2019
- Allocation block
- 2001:df2:4280::/48
- Status
- assigned
- 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 |
|---|---|---|
| 2001:df2:4280::/48 | AS139826 | /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
No prefix of the same length in the same parent block is announced.
History
- AS13982614th October 2026 — present
- AS655312nd November 2026 — 2nd November 2026
- AS6553129th October 2026 — 1st November 2026
- AS6553127th October 2026 — 28th October 2026
- AS13982612th August 2026 — 13th October 2026
- AS6553127th September 2026 — 27th September 2026
- AS6553122nd September 2026 — 22nd September 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.