240a:c000::/20
At a glance
Subnets
/20 block
Visibility
49 of 62 vantage points
RPKI
Registry
CNAllocated 20th August 2018
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 AS137726seen on 49 paths from 49 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
- Amsterdam137726560489808584536939213151This path
- Sao Paulo13772656048980858453335632590Shown above
- Singapore137726560489808584536939132337This path
- London, UK1377265604898085845382201557651907This 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
79%
Seen by 49 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
- 20th August 2018
- Allocation block
- 240a:c000::/20
- 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 |
|---|---|---|
| 240a:c000::/20 | AS137726 | /20 |
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
No less specific announcement covers this prefix.
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 240a:c0c0::/32 | 4.3B × /64 | AS137726China Petroleum & Chemical Corporation | 4/62 |
Sibling prefixes
No prefix of the same length in the same parent block is announced.
History
- AS13772612th 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.