asn.dev

Observed topology

AS197731 TUXIS The Internet Engineering Group B.V.

Hosting RIPE

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

Transit

Upstream networks

All 20

Networks observed carrying traffic for AS197731: 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
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6395
AS6939Hurricane Electric LLCTransitIPv4 IPv686
AS8455atom86 BVHostingIPv479
AS39637ADES BVUnclassifiedIPv4 IPv614
AS24482SG.GSHostingIPv4 IPv613
AS58057Securebit AGUnclassifiedIPv4 IPv613
AS3333Reseaux IP Europeens Network Coordination Centre (RIPE NCC)UnclassifiedIPv4 IPv612
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv612
AS48185team.blue NVUnclassifiedIPv4 IPv612
AS50300CustodianDC LimitedUnclassifiedIPv4 IPv612

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS34233Superior B.V.HostingIPv4 IPv6158
AS204983Cyberfusion B.V.UnclassifiedIPv4 IPv696

Adjacency

Adjacent networks

All 22

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

ASNetworkTypeFamiliesPaths seen
AS137409GSL Networks Pty LTDUnclassifiedIPv4 IPv6540
AS34233Superior B.V.HostingIPv4 IPv6158
AS6939Hurricane Electric LLCTransitIPv4 IPv6120
AS8455atom86 BVHostingIPv4112
AS204983Cyberfusion B.V.UnclassifiedIPv4 IPv696
AS39637ADES BVUnclassifiedIPv4 IPv621
AS24482SG.GSHostingIPv4 IPv618
AS58057Securebit AGUnclassifiedIPv4 IPv618
AS37721Virtual Technologies & SolutionsResidentialIPv4 IPv617
AS213241TECHIT.BE SRLResidentialIPv4 IPv617

Provenance

Where this comes from

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