103.146.124.0/23
Incomparable(HK)Network Co., LimitedAS141159
Announced by more than one origin AS (MOAS).
AS40065 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/23 block
Visibility
71 of 76 vantage points
RPKI
Registry
CNAllocated 12th December 2019
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS401696seen on 3,962 paths from 76 vantage points
- Peer of AS40779seen on 59 paths from 7 vantage points
- Peer of AS23764seen on 30,201 paths from 2 vantage points
US
HK
KHOne 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
- Singapore401696407792376423673Shown above
- London, UK401696407792376441348529This path
- Amsterdam1411594017014077918013349182838298This path
- Sao Paulo14115940170140779180133491645335280This path
- Oregon, US141159401701407791801334911299855142013This 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
93%
Seen by 71 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
- China
- Allocated
- 12th December 2019
- Allocation block
- 103.146.124.0/23
- 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.146.124.0/24 | 256 | AS401696cognetcloud INC | 4/76 |
| 103.146.124.0/24 | 256 | AS141159Incomparable(HK)Network Co., Limited | 70/76 |
| 103.146.125.0/24 | 256 | AS401696cognetcloud INC | 7/76 |
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 103.146.126.0/23 | 512 | AS4808China Unicom Beijing Province Network | 75/76 |
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.146.124.0/23 in the calculator/23 reference
Routing data derived from RouteViews MRT archives and public registry data.