asn.dev

Observed topology

AS15817 MITTWALD-AS Robert Meyer trading as "Mittwald CM Service GmbH & Co. KG"

Hosting RIPE

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

Transit

Upstream networks

All 17

Networks observed carrying traffic for AS15817: 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
AS33891Core-Backbone GmbHHostingIPv4 IPv6586
AS1299Arelion Sweden ABTransitIPv4 IPv6379
AS6939Hurricane Electric LLCTransitIPv4 IPv6158
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv677
AS3320Deutsche Telekom AGMobileIPv4 IPv676
AS24482SG.GSHostingIPv4 IPv626
AS34019Hivane AssociationUnclassifiedIPv4 IPv626
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv626
AS212024Marc SchmittUnclassifiedIPv4 IPv626
AS213241TECHIT.BE SRLResidentialIPv4 IPv626

All 17 upstreams →

Transit

Downstream networks

inferred

Networks for which AS15817 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 17

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

ASNetworkTypeFamiliesPaths seen
AS33891Core-Backbone GmbHHostingIPv4 IPv6586
AS1299Arelion Sweden ABTransitIPv4 IPv6379
AS6939Hurricane Electric LLCTransitIPv4 IPv6158
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv677
AS3320Deutsche Telekom AGMobileIPv4 IPv676
AS24482SG.GSHostingIPv4 IPv626
AS34019Hivane AssociationUnclassifiedIPv4 IPv626
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv626
AS212024Marc SchmittUnclassifiedIPv4 IPv626
AS213241TECHIT.BE SRLResidentialIPv4 IPv626

All 17 adjacent →

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.