asn.dev

Observed topology

AS201494 MODULUS

Residential RIPE

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

Transit

Upstream networks

inferred

Networks observed carrying traffic for AS201494: 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
AS56910Digital Realty Hellas Single Member S.AUnclassifiedIPv443
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv412
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS34019Hivane AssociationUnclassifiedIPv41
AS37100SEACOM LimitedUnclassifiedIPv41
AS48362Stadtwerke FeldkirchResidentialIPv41
AS212024Marc SchmittUnclassifiedIPv41

Transit

Downstream networks

inferred

Networks for which AS201494 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

observed

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

ASNetworkTypeFamiliesPaths seen
AS56910Digital Realty Hellas Single Member S.AUnclassifiedIPv443
AS6762TELECOM ITALIA SPARKLE S.p.A.TransitIPv412
AS34549meerfarbig GmbH & Co. KGHostingIPv43
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv42
AS20485Joint Stock Company TransTeleComUnclassifiedIPv41
AS24482SG.GSHostingIPv41
AS34019Hivane AssociationUnclassifiedIPv41
AS37100SEACOM LimitedUnclassifiedIPv41
AS48362Stadtwerke FeldkirchResidentialIPv41
AS212024Marc SchmittUnclassifiedIPv41

Provenance

Where this comes from

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