asn.dev

Observed topology

AS49436 STADTWERKE-SOEST

Unclassified RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS49436: 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
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6129
AS6939Hurricane Electric LLCTransitIPv4 IPv684
AS50873David DoepelheuerHostingIPv460
AS24961WIIT AGHostingIPv4 IPv644
AS24482SG.GSHostingIPv4 IPv68
AS34019Hivane AssociationUnclassifiedIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS212024Marc SchmittUnclassifiedIPv4 IPv68
AS6797GlobalConnect ABUnclassifiedIPv44
AS17639Converge ICT Solutions Inc.UnclassifiedIPv64

All 14 upstreams →

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS41451Dominik SchlueterUnclassifiedIPv4 IPv693

Adjacency

Adjacent networks

All 15

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

ASNetworkTypeFamiliesPaths seen
AS50629LWLcom GmbHUnclassifiedIPv4 IPv6168
AS41451Dominik SchlueterUnclassifiedIPv4 IPv6131
AS6939Hurricane Electric LLCTransitIPv4 IPv6119
AS50873David DoepelheuerHostingIPv475
AS24961WIIT AGHostingIPv4 IPv656
AS24482SG.GSHostingIPv4 IPv612
AS34019Hivane AssociationUnclassifiedIPv4 IPv612
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv612
AS212024Marc SchmittUnclassifiedIPv4 IPv612
AS17639Converge ICT Solutions Inc.UnclassifiedIPv4 IPv68

All 15 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.