1.193.223.0/24
AS4134 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/24 block
Visibility
7 of 81 vantage points
RPKI
Registry
CNAllocated 19th June 2010
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 AS139018seen on 1,018 paths from 84 vantage points
- Peer of AS4134seen on 2,354 paths from 4 vantage points
- Peer of AS9808seen on 3,439,062 paths from 145 vantage points
- Peer of AS58453seen on 21,337 paths from 14 vantage points
- Peer of AS15802seen on 40,432 paths from 90 vantage points
- Peer of AS8966seen on 63,038 paths from 6 vantage points
HK
AE
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, UK139018413498085845315802896635280This path
- Sao Paulo139018413498085845315802896635280Shown 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
9%
Seen by 7 of 81 full-feed vantage points
Seen by few vantage pointsObserved 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
- 19th June 2010
- Allocation block
- 1.192.0.0/13
- 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 |
|---|---|---|---|
| 1.193.220.0/22 | 1k | AS139018Henan Luoyang IDC | 8/81 |
| 1.192.0.0/13 | 524k | AS4134China Telecom Backbone | 80/81 |
More specific announcements
Nothing inside this block is announced separately.
Sibling prefixes
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 1.193.222.0/24 | 256 | AS139018Henan Luoyang IDC | 8/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 1.193.223.0/24 in the calculator/24 reference
Routing data derived from RouteViews MRT archives and public registry data.