Skip to main content

AS57907

CLOUDCONNX

-----------------------------------------------

Registry

Authoritative registration data

AS number
57907
Name
CLOUDCONNX
Organisation
-----------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS57907
37.152.48.0/21 IPv4 /21 not checked
212.162.156.0/22 IPv4 /22 not checked
2a09:d800::/29 IPv6 /29 not checked

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 AS57907
Address families
LINX LON1: Main 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 AS57907 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

18 networks seen before AS57907 in AS paths

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS57907 in AS paths

Observed downstreams
Families
AS211067 LEC 144 169
v4

No rows match “”.

Showing – of

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 7
v4 v6
AS35280 F5 1 4
v4 v6
AS12779 ITGATE 1 3
v4 v6
AS17639 CONVERGE-AS 1 3
v4 v6
AS34288 AS34288 1 3
v4 v6
AS37721 ORG-VTS1-AFRINIC 1 3
v4 v6
AS48185 team_blue 1 3
v4 v6
AS49544 i3Dnet 1 3
v4 v6
AS50300 CUSTDC 1 3
v4 v6
AS61573 ASN61573 1 3
v4 v6
AS13237 LAMBDANET-AS 1 2
v4
AS50304 BLIX 1 2
v4
AS18106 VIEWQWEST-SG-AP 1 1
v6
AS34927 iFog-GmbH 1 1
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.