Observed topology
AS28876 SUEC-DACOR-AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS28876: 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.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 263 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 181 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 54 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 51 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 19 |
| AS34019 | Hivane Association | Unclassified | IPv4 IPv6 | 19 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 19 |
| AS212024 | Marc Schmitt | Unclassified | IPv4 IPv6 | 15 |
| AS6797 | GlobalConnect AB | Unclassified | IPv4 | 13 |
| AS8551 | Bezeq International Ltd. | Unclassified | IPv4 | 13 |
Transit
Downstream networks
Networks for which AS28876 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS50064 | TK Networks GmbH | Unclassified | IPv4 IPv6 | 560 |
| AS24978 | Telenec Telekommunikation Neustadt GmbH | Unclassified | IPv4 IPv6 | 216 |
| AS50642 | DNCC GmbH | Unclassified | IPv4 IPv6 | 214 |
| AS44974 | RegioNet Schweinfurt GmbH | Unclassified | IPv4 IPv6 | 139 |
| AS29008 | Niedermayr IT GmbH | Unclassified | IPv4 IPv6 | 121 |
| AS198570 | Stadtnetz Bamberg Gesellschaft fuer Telekommunikation mbH | Unclassified | IPv4 | 26 |
| AS207749 | Staedtische Werke Ueberlandwerke Coburg GmbH | Unclassified | IPv4 | 14 |
| AS200062 | Optitrust GmbH | Hosting | IPv4 | 7 |
| AS205100 | F3 Netze e.V. | Hosting | IPv6 | 5 |
Adjacency
Adjacent networks
Every AS seen directly next to AS28876 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 1,239 |
| AS50064 | TK Networks GmbH | Unclassified | IPv4 IPv6 | 560 |
| AS44974 | RegioNet Schweinfurt GmbH | Unclassified | IPv4 IPv6 | 270 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 267 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 264 |
| AS50642 | DNCC GmbH | Unclassified | IPv4 IPv6 | 229 |
| AS24978 | Telenec Telekommunikation Neustadt GmbH | Unclassified | IPv4 IPv6 | 216 |
| AS29008 | Niedermayr IT GmbH | Unclassified | IPv4 IPv6 | 182 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 123 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 43 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-28 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.21M 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.