2400:e500:3d::/48
At a glance
Subnets
/48 block
Visibility
9 of 62 vantage points
RPKI
Registry
AFAllocated 25th May 2011
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS38742seen on 6,388 paths from 142 vantage points
- Peer of AS138322seen on 2,145 paths from 142 vantage points
- Peer of AS38193seen on 2,123 paths from 91 vantage points
- Peer of AS8966seen on 133,632 paths from 2 vantage points
PK
AE
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.
Route visibility
15%
Seen by 9 of 62 full-feed vantage points
Seen by few vantage pointsObserved at 3 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
- Afghanistan
- Allocated
- 25th May 2011
- Allocation block
- 2400:e500::/32
- Status
- allocated
- Origin validation
- Invalid
A ROA covers this prefix but does not authorise this origin AS at this prefix length. That is either a misconfiguration or a hijack, and many networks will drop the route.
ROAs covering this prefix
| ROA prefix | Authorised origin | Max length |
|---|---|---|
| 2400:e500::/32 | AS38742 | /32 |
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 |
|---|---|---|---|
| 2400:e500::/32 | 4.3B × /64 | AS38742Afghan Wireless Communication Company | 62/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2400:e500:3c::/48 | 65.5k × /64 | AS38742Afghan Wireless Communication Company | 9/62 |
History
- AS3874212th 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.