222.126.245.0/24
At a glance
Addresses
/24 block
Visibility
10 of 81 vantage points
RPKI
Registry
CNAllocated 30th August 2006
AS paths to this prefix
All pathsOne observed path, hop by hop, from the origin out to Singapore.
Seen from Singapore
- Peer of AS37965seen on 43 paths from 10 vantage points
- Peer of AS17621seen on 53,844 paths from 144 vantage points
- Peer of AS4837seen on 279 paths from 4 vantage points
- Peer of AS9808seen on 3,437,082 paths from 145 vantage points
- Peer of AS58453seen on 21,221 paths from 14 vantage points
- Peer of AS15802seen on 40,291 paths from 90 vantage points
- Peer of AS8966seen on 208,809 paths from 2 vantage points
HK
AE
SGOne 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 Paulo37965176214837413423764771335280This path
- London, UK3796517621483798085845315802896635280This path
- Singapore37965176214837980858453158028966132337Shown 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
12%
Seen by 10 of 81 full-feed vantage points
Seen by few vantage pointsObserved at 3 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
- 30th August 2006
- Allocation block
- 222.126.128.0/17
- 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 |
|---|---|---|---|
| 222.126.244.0/23 | 512 | AS7468Cyber Express Communication Ltd. | 79/81 |
| 222.126.244.0/23 | 512 | AS37965Pacnet Business Solutions LTD | 2/81 |
| 222.126.244.0/22 | 1k | AS37965Pacnet Business Solutions LTD | 81/81 |
| 222.126.240.0/20 | 4.1k | AS37965Pacnet Business Solutions LTD | 81/81 |
| 222.126.128.0/17 | 32.8k | AS7468Cyber Express Communication Ltd. | 81/81 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 222.126.244.0/24 | 256 | AS7468Cyber Express Communication Ltd. | 79/81 |
| 222.126.244.0/24 | 256 | AS37965Pacnet Business Solutions LTD | 2/81 |
History
- AS3796522nd September 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.
Open 222.126.245.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.