2400:c700:87::/48
At a glance
Subnets
/48 block
Visibility
57 of 62 vantage points
RPKI
Registry
INAllocated 12th May 2011
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 AS55410seen on 61,966 paths from 142 vantage points
- Peer of AS3491seen on 43,423 paths from 8 vantage points
- Peer of AS12956seen on 476,587 paths from 4 vantage points
HK
ES
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
- Amsterdam5541034916939213151This path
- London, UK554103491900251907This path
- Sao Paulo5541034911295632590Shown above
- Singapore5541034916939132337This 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
92%
Seen by 57 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
- India
- Allocated
- 12th May 2011
- Allocation block
- 2400:c700::/32
- 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 |
|---|---|---|---|
| 2400:c700::/32 | 4.3B × /64 | AS55644Vodafone Idea Ltd | 62/62 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 2400:c700:86::/48 | 65.5k × /64 | AS55410Vodafone Idea Ltd | 57/62 |
| 2400:c700:86::/48 | 65.5k × /64 | AS55644Vodafone Idea Ltd | 4/62 |
History
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.