103.43.8.0/22
At a glance
Addresses
/22 block
Visibility
75 of 76 vantage points
RPKI
Registry
HKAllocated 14th November 2014
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 AS401701seen on 4,606 paths from 76 vantage points
- Peer of AS40779seen on 6,468 paths from 76 vantage points
- Peer of AS2914seen on 438,988 paths from 6 vantage points
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
- Sao Paulo40170140779291435280Shown above
- Singapore4017014016964077923673This path
- Amsterdam401701407792914250918298This path
- London, UK401696407792376441348529This path
- Oregon, US40170140779180133491174855142013This 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
99%
Seen by 75 of 76 full-feed vantage points
Globally propagatedObserved at 5 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
- Hong Kong SAR China
- Allocated
- 14th November 2014
- Allocation block
- 103.43.8.0/22
- Status
- allocated
- Origin validation
- No ROA
No ROA covers this prefix, so RPKI has nothing to say about it either way. This is still the common case for a large share of the routing table.
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 |
|---|---|---|---|
| 103.43.8.0/23 | 512 | AS137899I LAYER LIMITED | 74/76 |
| 103.43.10.0/23 | 512 | AS137899I LAYER LIMITED | 74/76 |
| 103.43.8.0/24 | 256 | AS35876VoltNet inc | 76/76 |
| 103.43.9.0/24 | 256 | AS35876VoltNet inc | 76/76 |
| 103.43.11.0/24 | 256 | AS35876VoltNet inc | 76/76 |
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.
Open 103.43.8.0/22 in the calculator/22 reference
Routing data derived from RouteViews MRT archives and public registry data.