Skip to main content

AS42909

COMMUNITYDNS

Community DNS Limited

Registry

Authoritative registration data

AS number
42909
Name
COMMUNITYDNS
Organisation
Community DNS Limited
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS42909
194.0.1.0/24 IPv4 /24 not checked
194.0.2.0/24 IPv4 /24 not checked
74.116.176.0/24 IPv4 /24 not checked
74.116.178.0/24 IPv4 /24 not checked
74.116.179.0/24 IPv4 /24 not checked
2001:678:4::/48 IPv6 /48 not checked
2001:678:5::/48 IPv6 /48 RPKI valid
2620:7d:e000::/48 IPv6 /48 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 AS42909
Address families
AKL-IX (Auckland NZ): AKL-IX 10,000 Mbps IPv4 · IPv6
ArmIX: Peering 1,000 Mbps IPv4 · IPv6
BKNIX (Thailand): Bangkok 10,000 Mbps IPv4 · IPv6
IX Australia Perth (WA-IX): WA-IX 100,000 Mbps IPv4 · IPv6
JINX: JINX Peering 10,000 Mbps IPv4 · IPv6
KazNIX 10,000 Mbps IPv4 · IPv6
LU-CIX 10,000 Mbps IPv4 · IPv6
MSK-IX Moscow: MSK-IX peering network 1,000 Mbps IPv4 · IPv6
MSK-IX Saint-Petersburg: MSK-IX Saint-Petersburg peering network 2,000 Mbps IPv4 · IPv6
OpenIXP / NiCE 10,000 Mbps IPv4 · IPv6
SGIX: Peering LAN 10,000 Mbps IPv4 · IPv6
TREX Tampere: Unicast Peering 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 AS42909 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

25 networks seen before AS42909 in AS paths

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS42909 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

26 adjacencies that may be an artefact of collector peering

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.