asn.dev

Observed topology

AS31298 AS-ZULU-

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS31298: 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.TransitIPv4255
AS34224Neterra Ltd.UnclassifiedIPv4251
AS57463NetIX Communications JSCUnclassifiedIPv4152
AS6939Hurricane Electric LLCTransitIPv490
AS3303Swisscom (Schweiz) AGResidentialIPv415
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv415
AS20764CJSC RASCOMUnclassifiedIPv415
AS24482SG.GSHostingIPv415
AS34019Hivane AssociationUnclassifiedIPv415
AS34927iFog GmbHHostingIPv415

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS57546Bul Ins ADUnclassifiedIPv4120

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS3257GTT Communications Inc.TransitIPv4301
AS34224Neterra Ltd.UnclassifiedIPv4275
AS57463NetIX Communications JSCUnclassifiedIPv4160
AS57546Bul Ins ADUnclassifiedIPv4120
AS6939Hurricane Electric LLCTransitIPv4106
AS3303Swisscom (Schweiz) AGResidentialIPv417
AS8280SYNAPSECOM S.A. Provider of Telecommunications and Internet ServicesHostingIPv417
AS20764CJSC RASCOMUnclassifiedIPv417
AS24482SG.GSHostingIPv417
AS34019Hivane AssociationUnclassifiedIPv417

All 17 adjacent →

Provenance

Where this comes from

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