asn.dev

Observed topology

AS203649 goInternet GO INTERNET LTD

Residential RIPE

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

Transit

Upstream networks

All 13

Networks observed carrying traffic for AS203649: 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
AS8801Rocket Fibre LtdUnclassifiedIPv4 IPv6381
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv626
AS174Cogent Communications, LLCTransitIPv424
AS50304Blix Solutions ASUnclassifiedIPv416
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv69
AS24482SG.GSHostingIPv4 IPv69
AS48185team.blue NVUnclassifiedIPv4 IPv69
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv69
AS3741Dimension DataUnclassifiedIPv48
AS6797GlobalConnect ABUnclassifiedIPv48

All 13 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34134FreeClix LtdHostingIPv416

Adjacency

Adjacent networks

All 14

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

ASNetworkTypeFamiliesPaths seen
AS8801Rocket Fibre LtdUnclassifiedIPv4 IPv6381
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv630
AS174Cogent Communications, LLCTransitIPv424
AS34134FreeClix LtdHostingIPv416
AS50304Blix Solutions ASUnclassifiedIPv416
AS24482SG.GSHostingIPv4 IPv613
AS3741Dimension DataUnclassifiedIPv412
AS37100SEACOM LimitedUnclassifiedIPv412
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv69
AS48185team.blue NVUnclassifiedIPv4 IPv69

All 14 adjacent →

Provenance

Where this comes from

Derived from routing tables collected at 2026-11-09 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.03M 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.