2407:9a00:3::/48
CENTRE FOR DEVELOPMENT OF TELEMATICSAS55446
Mahanagar Telephone Nigam LimitedAS17813
Announced by more than one origin AS (MOAS).
At a glance
Subnets
/48 block
Visibility
53 of 64 vantage points
RPKI
Registry
INAllocated 5th March 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 AS55446seen on 349 paths from 131 vantage points
- Peer of AS55824seen on 37,529 paths from 145 vantage points
- Peer of AS9885seen on 8,389 paths from 138 vantage points
- Peer of AS55836seen on 534,381 paths from 144 vantage points
- Peer of AS64049seen on 29,482 paths from 54 vantage points
- Peer of AS2914seen on 447,736 paths from 6 vantage points
SG
US
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
- London, UK55446178139829949835280This path
- Singapore554461781398299498132337This path
- Amsterdam55446558249885558366404932590This path
- Sao Paulo554465582498855583664049291435280Shown 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
83%
Seen by 53 of 64 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
- India
- Allocated
- 5th March 2011
- Allocation block
- 2407:9a00::/32
- Status
- allocated
- 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 |
|---|---|---|
| 2407:9a00:3::/48 | AS55446 | /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
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.