asn.dev

Observed topology

AS8879 DTS-Systeme DTS Systeme GmbH

Hosting RIPE NSP

Upstreams 18 carry this network
Downstreams 2 this network carries
Adjacent (IPv4) 17
Adjacent (IPv6) 12
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 18

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 IPv6226
AS6939Hurricane Electric LLCTransitIPv4 IPv667
AS198949Radware LtdUnclassifiedIPv441
AS3320Deutsche Telekom AGMobileIPv4 IPv628
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv622
AS24482SG.GSHostingIPv4 IPv68
AS48362Stadtwerke FeldkirchResidentialIPv4 IPv68
AS212024Marc SchmittUnclassifiedIPv4 IPv68
AS6797GlobalConnect ABUnclassifiedIPv47
AS8551Bezeq International Ltd.UnclassifiedIPv47

All 18 upstreams →

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. KGUnclassifiedIPv498
AS12437DTS Systeme Muenster GmbHUnclassifiedIPv4 IPv667

Adjacency

Adjacent networks

All 20

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

ASNetworkTypeFamiliesPaths seen
AS13237euNetworks GmbHUnclassifiedIPv4 IPv6308
AS6939Hurricane Electric LLCTransitIPv4 IPv6107
AS39077Aschendorff Medien GmbH & Co. KGUnclassifiedIPv498
AS12437DTS Systeme Muenster GmbHUnclassifiedIPv4 IPv667
AS198949Radware LtdUnclassifiedIPv441
AS34549meerfarbig GmbH & Co. KGHostingIPv4 IPv632
AS3320Deutsche Telekom AGMobileIPv4 IPv628
AS24482SG.GSHostingIPv4 IPv612
AS212024Marc SchmittUnclassifiedIPv4 IPv612
AS8551Bezeq International Ltd.UnclassifiedIPv410

All 20 adjacent →

Provenance

Where this comes from

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