asn.dev

Observed topology

AS203724 MGG4-AS1 Musarubra Germany GmbH

Unclassified RIPE

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

Transit

Upstream networks

All 48

Networks observed carrying traffic for AS203724: 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
AS31898Oracle CorporationHostingIPv42,079
AS3356Level 3 Parent, LLCTransitIPv41,031
AS3257GTT Communications Inc.TransitIPv4615
AS6939Hurricane Electric LLCTransitIPv4406
AS3491PCCW Global (HK) Ltd.TransitIPv4299
AS7195EDGEUNO S.A.SUnclassifiedIPv4292
AS18229CtrlSHostingIPv4240
AS34372VegaSystems GmbH & Co. KGHostingIPv4 IPv6212
AS8220COLT Technology Services Group LimitedHostingIPv4154
AS4637Telstra GlobalUnclassifiedIPv4132

All 48 upstreams →

Transit

Downstream networks

inferred

Networks for which AS203724 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 48

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

ASNetworkTypeFamiliesPaths seen
AS31898Oracle CorporationHostingIPv42,079
AS3356Level 3 Parent, LLCTransitIPv41,031
AS3257GTT Communications Inc.TransitIPv4615
AS6939Hurricane Electric LLCTransitIPv4406
AS3491PCCW Global (HK) Ltd.TransitIPv4299
AS7195EDGEUNO S.A.SUnclassifiedIPv4292
AS18229CtrlSHostingIPv4240
AS34372VegaSystems GmbH & Co. KGHostingIPv4 IPv6212
AS8220COLT Technology Services Group LimitedHostingIPv4154
AS4637Telstra GlobalUnclassifiedIPv4132

All 48 adjacent →

Provenance

Where this comes from

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