Skip to main content

AS20598

CYBERSPACE-AS

Autonomous System number for Cyber Space,

Registry

Authoritative registration data

AS number
20598
Name
CYBERSPACE-AS
Organisation
Autonomous System number for Cyber Space,
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

65

IPv6 prefixes

0

Total announced

65

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS20598
41.71.128.0/17 IPv4 /17 RPKI not found
41.138.192.0/18 IPv4 /18 RPKI not found
102.128.74.0/24 IPv4 /24 RPKI not found
158.26.160.0/24 IPv4 /24 not checked
212.100.64.0/24 IPv4 /24 not checked
212.100.65.0/24 IPv4 /24 RPKI not found
212.100.66.0/24 IPv4 /24 RPKI not found
212.100.67.0/24 IPv4 /24 not checked
212.100.68.0/24 IPv4 /24 not checked
212.100.69.0/24 IPv4 /24 RPKI not found
212.100.70.0/24 IPv4 /24 not checked
212.100.71.0/24 IPv4 /24 RPKI not found
212.100.72.0/24 IPv4 /24 not checked
212.100.73.0/24 IPv4 /24 not checked
212.100.74.0/24 IPv4 /24 RPKI not found
212.100.75.0/24 IPv4 /24 RPKI not found
212.100.76.0/24 IPv4 /24 not checked
212.100.77.0/24 IPv4 /24 not checked
212.100.78.0/24 IPv4 /24 not checked
212.100.79.0/24 IPv4 /24 RPKI not found
212.100.80.0/24 IPv4 /24 RPKI not found
212.100.81.0/24 IPv4 /24 RPKI not found
212.100.82.0/24 IPv4 /24 not checked
212.100.85.0/24 IPv4 /24 RPKI not found
212.100.86.0/24 IPv4 /24 RPKI not found
212.100.87.0/24 IPv4 /24 RPKI not found
212.100.88.0/24 IPv4 /24 not checked
212.100.89.0/24 IPv4 /24 not checked
212.100.90.0/24 IPv4 /24 RPKI not found
212.100.91.0/24 IPv4 /24 RPKI not found
212.100.92.0/24 IPv4 /24 not checked
212.100.93.0/24 IPv4 /24 RPKI not found
212.100.94.0/24 IPv4 /24 RPKI not found
212.100.95.0/24 IPv4 /24 RPKI not found
41.138.138.0/24 IPv4 /24 RPKI not found
41.138.161.0/24 IPv4 /24 not checked
41.138.162.0/24 IPv4 /24 not checked
41.138.163.0/24 IPv4 /24 not checked
41.138.164.0/24 IPv4 /24 RPKI not found
41.138.165.0/24 IPv4 /24 not checked
41.138.166.0/24 IPv4 /24 RPKI not found
41.138.167.0/24 IPv4 /24 not checked
41.138.169.0/24 IPv4 /24 not checked
41.138.170.0/24 IPv4 /24 not checked
41.138.171.0/24 IPv4 /24 not checked
41.138.172.0/24 IPv4 /24 not checked
41.138.173.0/24 IPv4 /24 not checked
41.138.174.0/24 IPv4 /24 RPKI not found
41.138.180.0/24 IPv4 /24 RPKI not found
41.138.181.0/24 IPv4 /24 not checked
41.138.182.0/24 IPv4 /24 RPKI not found
41.138.183.0/24 IPv4 /24 RPKI not found
41.138.184.0/24 IPv4 /24 RPKI not found
41.138.185.0/24 IPv4 /24 not checked
41.138.186.0/24 IPv4 /24 not checked
41.138.187.0/24 IPv4 /24 not checked
41.138.188.0/24 IPv4 /24 RPKI not found
41.138.189.0/24 IPv4 /24 RPKI not found
41.138.190.0/24 IPv4 /24 RPKI not found
41.138.191.0/24 IPv4 /24 not checked
41.138.192.0/24 IPv4 /24 not checked
41.138.197.0/24 IPv4 /24 not checked
41.71.128.0/24 IPv4 /24 RPKI not found
41.71.129.0/24 IPv4 /24 RPKI not found
41.71.131.0/24 IPv4 /24 RPKI not found

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS20598
Address families
IXPN Lagos 10,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS20598 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS20598 in AS paths

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS20598 in AS paths

Observed downstreams
Families
AS328128 ORG-TBDL1-AFRINIC 231 284
v4
AS37056 ORG-ZBP1-AFRINIC 77 200
v4
AS329404 ORG-PP1-AFRINIC 61 82
v4

No rows match “”.

Showing – of

Uncertain adjacencies

2 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS36236 NETACTUATE 1 31
v4
AS37721 ORG-VTS1-AFRINIC 1 31
v4

No rows match “”.

Showing – of

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.