AS55355
ISP-AS-AP
ISP
Registry
Authoritative registration data
- AS number
- 55355
- Name
- ISP-AS-AP
- Organisation
- ISP
- Country
-
HK
Hong Kong SAR China
- RIR
- APNIC
- Registered
Source:asn:rdap
retrieved
IPv4 prefixes
27
IPv6 prefixes
0
Total announced
27
Announced prefixes
Observed in BGP by route collectors, not a registry allocation list
matching
| 118.143.207.0/24 | IPv4 | /24 | not checked | |
| 118.143.209.0/24 | IPv4 | /24 | not checked | |
| 122.8.9.0/24 | IPv4 | /24 | not checked | |
| 156.225.7.0/24 | IPv4 | /24 | not checked | |
| 175.100.201.0/24 | IPv4 | /24 | not checked | |
| 175.100.202.0/24 | IPv4 | /24 | not checked | |
| 175.100.203.0/24 | IPv4 | /24 | not checked | |
| 175.100.204.0/24 | IPv4 | /24 | not checked | |
| 175.100.205.0/24 | IPv4 | /24 | not checked | |
| 175.100.207.0/24 | IPv4 | /24 | not checked | |
| 203.90.239.0/24 | IPv4 | /24 | not checked | |
| 203.90.245.0/24 | IPv4 | /24 | not checked | |
| 203.90.246.0/24 | IPv4 | /24 | not checked | |
| 203.90.247.0/24 | IPv4 | /24 | not checked | |
| 203.90.248.0/24 | IPv4 | /24 | not checked | |
| 203.90.249.0/24 | IPv4 | /24 | not checked | |
| 203.90.250.0/24 | IPv4 | /24 | not checked | |
| 203.90.255.0/24 | IPv4 | /24 | not checked | |
| 218.188.100.0/24 | IPv4 | /24 | not checked | |
| 218.188.101.0/24 | IPv4 | /24 | not checked | |
| 218.188.96.0/24 | IPv4 | /24 | not checked | |
| 218.188.97.0/24 | IPv4 | /24 | not checked | |
| 218.188.98.0/24 | IPv4 | /24 | not checked | |
| 218.188.99.0/24 | IPv4 | /24 | not checked | |
| 218.189.10.0/24 | IPv4 | /24 | not checked | |
| 218.189.124.0/24 | IPv4 | /24 | not checked | |
| 218.189.125.0/24 | IPv4 | /24 | not checked |
No rows match “”.
Showing – of
Source:ripestat:announced-prefixes
observed
Observed adjacencies
Networks seen next to AS55355 in BGP paths by route collectors.
Observed upstreams
12 networks seen before AS55355 in AS paths
Observed downstreams
7 networks seen after AS55355 in AS paths
Uncertain adjacencies
2 adjacencies that may be an artefact of collector peering
Note:
These are observed adjacencies derived from BGP path data, not
confirmed commercial relationships. A network appearing before another in an AS
path does not establish that it is a paying transit customer, a settlement free
peer, or anything else contractual.
Adjacencies marked uncertain were seen only as direct peers of a route
collector, so the collector's own peering may have created them.