asn.dev

Observed topology

AS31317 ANSCHLUSSWERK

Residential RIPE Cable/DSL/ISP

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

Transit

Upstream networks

All 21

Networks observed carrying traffic for AS31317: 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
AS6939Hurricane Electric LLCTransitIPv4 IPv6379
AS1299Arelion Sweden ABTransitIPv4 IPv6375
AS3257GTT Communications Inc.TransitIPv4236
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv662
AS12859BIT BVHostingIPv4 IPv626
AS24482SG.GSHostingIPv4 IPv626
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv626
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv626
AS212024Marc SchmittUnclassifiedIPv4 IPv626
AS1836green.ch AGResidentialIPv418

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS198444Stadtwerke Dorfen GmbHUnclassifiedIPv4 IPv6103
AS198893ITF-Systemhaus GmbHUnclassifiedIPv4 IPv671

Adjacency

Adjacent networks

All 25

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

ASNetworkTypeFamiliesPaths seen
AS6939Hurricane Electric LLCTransitIPv4 IPv6442
AS1299Arelion Sweden ABTransitIPv4 IPv6378
AS3257GTT Communications Inc.TransitIPv4282
AS198444Stadtwerke Dorfen GmbHUnclassifiedIPv4 IPv6103
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv673
AS198893ITF-Systemhaus GmbHUnclassifiedIPv4 IPv671
AS24482SG.GSHostingIPv4 IPv631
AS29504Freenet Liberec, z.s.UnclassifiedIPv4 IPv631
AS212024Marc SchmittUnclassifiedIPv4 IPv631
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv629

Provenance

Where this comes from

Derived from routing tables collected at 2026-10-29 10:00 UTC by route-views2,rrc00, as seen from 76 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.