asn.dev

Observed topology

AS8879 DTS-SYSTEME DTS Systeme GmbH

Hosting RIPE

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

Transit

Upstream networks

All 14

Networks observed carrying traffic for AS8879: 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
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6289
AS6939Hurricane Electric LLCTransitIPv4 IPv683
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS212024Marc SchmittUnclassifiedIPv4 IPv68
AS6797GlobalConnect ABUnclassifiedIPv47
AS20485Joint Stock Company TransTeleComUnclassifiedIPv47
AS34019Hivane AssociationUnclassifiedIPv47
AS37100SEACOM LimitedUnclassifiedIPv47

Transit

Downstream networks

inferred

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

ASNetworkTypeFamiliesPaths seen
AS39077Aschendorff Medien GmbH & Co. KGUnclassifiedIPv4104
AS12437DTS Systeme Muenster GmbHUnclassifiedIPv4 IPv697

Adjacency

Adjacent networks

All 17

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

ASNetworkTypeFamiliesPaths seen
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6393
AS6939Hurricane Electric LLCTransitIPv4 IPv6136
AS39077Aschendorff Medien GmbH & Co. KGUnclassifiedIPv4104
AS12437DTS Systeme Muenster GmbHUnclassifiedIPv4 IPv697
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv632
AS24482SG.GSHostingIPv4 IPv612
AS212024Marc SchmittUnclassifiedIPv4 IPv612
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv611
AS6797GlobalConnect ABUnclassifiedIPv410
AS20485Joint Stock Company TransTeleComUnclassifiedIPv410

Provenance

Where this comes from

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