AS22653
GLOBALCOMPASS
Cyber Wurx LLC
Registry
Authoritative registration data
- AS number
- 22653
- Name
- GLOBALCOMPASS
- Organisation
- Cyber Wurx LLC
- Country
- —
- RIR
- ARIN
- Registered
Source:asn:rdap
retrieved
IPv4 prefixes
18
IPv6 prefixes
3
Total announced
21
Announced prefixes
Observed in BGP by route collectors, not a registry allocation list
matching
| 69.61.0.0/17 | IPv4 | /17 | not checked | |
| 66.154.0.0/18 | IPv4 | /18 | not checked | |
| 66.154.64.0/19 | IPv4 | /19 | not checked | |
| 84.75.236.0/22 | IPv4 | /22 | not checked | |
| 84.75.248.0/22 | IPv4 | /22 | not checked | |
| 93.123.76.0/22 | IPv4 | /22 | not checked | |
| 45.41.186.0/23 | IPv4 | /23 | not checked | |
| 69.61.116.0/23 | IPv4 | /23 | not checked | |
| 69.61.38.0/23 | IPv4 | /23 | not checked | |
| 104.194.222.0/24 | IPv4 | /24 | not checked | |
| 104.234.75.0/24 | IPv4 | /24 | not checked | |
| 104.238.248.0/24 | IPv4 | /24 | not checked | |
| 104.238.35.0/24 | IPv4 | /24 | not checked | |
| 142.202.205.0/24 | IPv4 | /24 | not checked | |
| 172.93.166.0/24 | IPv4 | /24 | not checked | |
| 45.56.165.0/24 | IPv4 | /24 | not checked | |
| 45.61.113.0/24 | IPv4 | /24 | not checked | |
| 69.61.106.0/24 | IPv4 | /24 | not checked | |
| 2607:1a00::/32 | IPv6 | /32 | not checked | |
| 2602:ff75:1000::/36 | IPv6 | /36 | not checked | |
| 2607:1a00:2::/48 | IPv6 | /48 | not checked |
No rows match “”.
Showing – of
Source:ripestat:announced-prefixes
observed
Observed adjacencies
Networks seen next to AS22653 in BGP paths by route collectors.
Observed upstreams
4 networks seen before AS22653 in AS paths
Observed downstreams
3 networks seen after AS22653 in AS paths
Uncertain adjacencies
5 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.