175.99.192.0/19
AS9924 is not currently observed originating this prefix. The origins we do see are listed above.
At a glance
Addresses
/19 block
Visibility
76 of 76 vantage points
RPKI
Registry
TWAllocated 16th December 2009
AS paths to this prefix
One real path per vantage point, fanning out from the origin. Where two reach the prefix the same way, those hops are drawn once. Open a path to follow it hop by hop.
- Amsterdam13162834628298This path
- London, UK131628346269398529This path
- Singapore1316283462335623673This path
- Oregon, US1316283462855142013This path
- Sao Paulo131628992434911295635280This 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
100%
Seen by 76 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
- Taiwan
- Allocated
- 16th December 2009
- Allocation block
- 175.96.0.0/14
- 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 |
|---|---|---|---|
| 175.99.192.0/18 | 16.4k | AS9924Taiwan Fixed Network, Telco and Network Service Provider. | 76/76 |
| 175.99.0.0/16 | 65.5k | AS9924Taiwan Fixed Network, Telco and Network Service Provider. | 76/76 |
| 175.96.0.0/14 | 262k | AS9924Taiwan Fixed Network, Telco and Network Service Provider. | 76/76 |
More specific announcements
| Prefix | Addresses | Origin | Visibility |
|---|---|---|---|
| 175.99.198.0/24 | 256 | AS131628Tai-Fu Cloud Co., Ltd. | 76/76 |
| 175.99.199.0/24 | 256 | AS131628Tai-Fu Cloud Co., Ltd. | 76/76 |
| 175.99.200.0/24 | 256 | AS131628Tai-Fu Cloud Co., Ltd. | 76/76 |
| 175.99.201.0/24 | 256 | AS131628Tai-Fu Cloud Co., Ltd. | 76/76 |
| 175.99.210.0/24 | 256 | AS131628Tai-Fu Cloud Co., Ltd. | 76/76 |
| 175.99.214.0/24 | 256 | AS131628Tai-Fu Cloud Co., Ltd. | 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 175.99.192.0/19 in the calculator/19 reference
Routing data derived from RouteViews MRT archives and public registry data.