asn.dev

Observed topology

AS24753 GCE-NET

Unclassified RIPE Cable/DSL/ISP

Upstreams 13 carry this network
Downstreams 0 this network carries
Adjacent (IPv4) 16
Adjacent (IPv6) 0
Upstream graph Who carries AS24753, and who carries them, drawn as a map up to the transit-free core. 2 exchanges Where AS24753 physically turns up to peer, and its address on each fabric.

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS24753: the AS immediately before it in a routing path. Ranked by how many paths showed the relationship, which reflects how widely it is used, not how much traffic crosses it.

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4133
AS20562Broadband Hosting B.V.HostingIPv4105
AS3549Level 3 Parent, LLCTransitIPv456
AS6939Hurricane Electric LLCTransitIPv456
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv47
AS6696VERIXI SAUnclassifiedIPv47
AS20485Joint Stock Company TransTeleComUnclassifiedIPv47
AS24482SG.GSHostingIPv47
AS37100SEACOM LimitedUnclassifiedIPv47
AS37721Virtual Technologies & SolutionsResidentialIPv47

Transit

Downstream networks

inferred

Networks for which AS24753 was observed as the last hop before the origin, meaning it appears to provide them transit.

No downstream observed. This network does not appear to carry transit for anyone.

Adjacency

Adjacent networks

All 16

Every AS seen directly next to AS24753 in a routing path, in either direction.

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4159
AS20562Broadband Hosting B.V.HostingIPv4121
AS6939Hurricane Electric LLCTransitIPv464
AS3549Level 3 Parent, LLCTransitIPv462
AS60815Data Net Telecom Co. LtdUnclassifiedIPv459
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv48
AS6696VERIXI SAUnclassifiedIPv48
AS20485Joint Stock Company TransTeleComUnclassifiedIPv48
AS24482SG.GSHostingIPv48
AS37100SEACOM LimitedUnclassifiedIPv48

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M route entries. These are observations from those vantage points, not a complete or authoritative view of the internet.

Inferred from path position, not from any declaration by either party. A network appearing here is carrying these routes; whether that is a paid transit arrangement, a backup, or something else is not something routing data can tell you. Adjacency is not the same as peering. Being next to each other in a path covers paid transit, settlement-free peering and customer connections alike, and routing data cannot distinguish them. Treat this as "these networks exchange routes", nothing more specific.

Cross-check against RIPEstat or BGP.tools, which observe from a different and larger set of vantage points.