Skip to main content

AS24956

GDS-1

------ ipv6 ------

Registry

Authoritative registration data

AS number
24956
Name
GDS-1
Organisation
------ ipv6 ------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

2

Total announced

6

Announced prefixes

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

Prefixes announced by AS24956
217.13.64.0/20 IPv4 /20 not checked
185.220.200.0/22 IPv4 /22 RPKI valid
194.120.234.0/24 IPv4 /24 RPKI valid
194.45.135.0/24 IPv4 /24 RPKI valid
2a00:1030::/32 IPv6 /32 RPKI valid
2001:67c:1978::/48 IPv6 /48 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 AS24956
Address families
BCIX: BCIX Peering LAN 10,000 Mbps IPv4 · IPv6
SON-IX 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 AS24956 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS24956 in AS paths

Observed upstreams
Families
AS9136 WOBCOM 191 1,060
v4 v6
AS6939 HURRICANE 73 236
v4 v6
AS3320 DTAG 49 218
v4 v6
AS24482 SGGS-AS-AP 2 50
v4 v6
AS8218 NEO-ASN 4 40
v4 v6
AS9002 RETN-AS 6 18
v6
AS24961 MYLOC-AS 2 12
v4 v6
AS6797 GLOBALCONNECT-NET 1 12
v4 v6
AS39351 ESAB-AS 1 6
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS24956 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS13237 LAMBDANET-AS 1 4
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.