43.226.56.0/24
At a glance
Addresses
/24 block
Visibility
80 of 81 vantage points
RPKI
Registry
CNAllocated 14th December 2014
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to London, UK.
Seen from London, UK
- Peer of AS151300seen on 2,098 paths from 80 vantage points
- Peer of AS4134seen on 5,014 paths from 83 vantage points
- Peer of AS4837seen on 2,098 paths from 80 vantage points
- Peer of AS58453seen on 2,098 paths from 80 vantage points
- Peer of AS151300seen on 2,098 paths from 80 vantage points
- Peer of AS3223seen on 1,921 paths from 6 vantage points
ID
HK
GB
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, UK1513004134483758453151300322335280Shown above
- Amsterdam15130041344837584531513003223335625091→ ⋯This path
- Sao Paulo15130041344837584531513003223291435280This path
- Singapore151300413448375845315130032236939132337This path
- Oregon, US15130041344837584531513003223693920130This 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 80 of 81 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
- 14th December 2014
- Allocation block
- 43.226.56.0/22
- 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 |
|---|---|---|---|
| 43.226.56.0/21 | 2k | AS23650China Telecom Jiangsu Province IDC Network | 81/81 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 43.226.57.0/24 | 256 | AS151300APNIC ASN block | 6/81 |
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 43.226.56.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.