Skip to main content

AS21804

ACCESS-SK

Access Communications Co-operative Limited

Registry

Authoritative registration data

AS number
21804
Name
ACCESS-SK
Organisation
Access Communications Co-operative Limited
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

24

IPv6 prefixes

3

Total announced

27

Announced prefixes

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

Prefixes announced by AS21804
24.89.64.0/18 IPv4 /18 RPKI not found
24.72.0.0/19 IPv4 /19 RPKI not found
24.72.32.0/19 IPv4 /19 not checked
24.72.64.0/19 IPv4 /19 RPKI not found
24.72.96.0/19 IPv4 /19 RPKI not found
65.87.224.0/19 IPv4 /19 RPKI not found
74.206.128.0/19 IPv4 /19 RPKI not found
184.169.48.0/20 IPv4 /20 RPKI not found
209.34.96.0/20 IPv4 /20 not checked
24.72.128.0/20 IPv4 /20 not checked
74.206.144.0/20 IPv4 /20 not checked
96.63.128.0/20 IPv4 /20 RPKI not found
96.63.144.0/20 IPv4 /20 RPKI not found
96.63.160.0/21 IPv4 /21 not checked
74.206.128.0/22 IPv4 /22 RPKI not found
96.63.168.0/22 IPv4 /22 not checked
74.206.132.0/23 IPv4 /23 RPKI not found
96.63.172.0/23 IPv4 /23 RPKI not found
23.146.176.0/24 IPv4 /24 not checked
23.182.112.0/24 IPv4 /24 RPKI not found
74.206.135.0/24 IPv4 /24 not checked
74.206.147.0/24 IPv4 /24 RPKI not found
96.63.174.0/24 IPv4 /24 RPKI not found
96.63.175.0/24 IPv4 /24 not checked
2605:7200::/32 IPv6 /32 RPKI valid
2605:7200:8000::/33 IPv6 /33 RPKI valid
2605:7200::/33 IPv6 /33 RPKI valid

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 AS21804
Address families
Equinix Chicago 100,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 100,000 Mbps IPv4 · IPv6
TorIX 100,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 AS21804 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS21804 in AS paths

Observed upstreams
Families
AS3257 GTT-BACKBONE 246 4,372
v4 v6
AS6327 SHAW 69 895
v4 v6
AS6939 HURRICANE 77 673
v4 v6
AS174 COGENT-174 18 360
v4
AS9002 RETN-AS 10 168
v4 v6
AS35280 F5 5 49
v4 v6
AS394256 CLOUDSINGULARITY 3 44
v4 v6
AS286 KPN 3 43
v4 v6
AS7575 AARNET-AS-AP 3 41
v4
AS8220 COLT 2 40
v4
AS20473 AS-VULTR 2 3
v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS21804 in AS paths

Observed downstreams
Families
AS53543 ACCESS-COMMUNICATIONS-CO-OPERATIVE 144 2,657
v4
AS397894 REAL-ASN-01 50 76
v4 v6
AS10980 STAFFORD 3 22
v4

No rows match “”.

Showing – of

Uncertain adjacencies

7 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 215
v4 v6
AS49544 i3Dnet 3 44
v4 v6
AS22652 FIBRENOIRE-INTERNET 3 43
v4 v6
AS18106 VIEWQWEST-SG-AP 3 41
v4
AS34927 iFog-GmbH 2 40
v4
AS1403 EBOX 2 6
v6
AS852 ASN852 1 4
v6

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.