Observed topology
AS8767 MNET-AS M-net Telekommunikations GmbH
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8767: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 719 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 544 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 524 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 457 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 214 |
| AS3333 | Reseaux IP Europeens Network Coordination Centre (RIPE NCC) | Unclassified | IPv4 IPv6 | 76 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 75 |
| AS3320 | Deutsche Telekom AG | Mobile | IPv4 IPv6 | 75 |
| AS17639 | Converge ICT Solutions Inc. | Unclassified | IPv4 IPv6 | 75 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 75 |
Transit
Downstream networks
Networks for which AS8767 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS42821 | K&K Kommunikationssysteme GmbH | Unclassified | IPv4 IPv6 | 890 |
| AS12886 | LEW TelNet GmbH | Residential | IPv4 IPv6 | 581 |
| AS24845 | Landeshauptstadt Muenchen, it@M | Unclassified | IPv4 IPv6 | 341 |
| AS205666 | ACP IT Solution AG | Unclassified | IPv4 | 295 |
| AS197909 | EDEKA Rechenzentrum Sued Betriebs GmbH | Unclassified | IPv4 IPv6 | 287 |
| AS12657 | BayCIX GmbH | Unclassified | IPv4 IPv6 | 285 |
| AS48328 | retarus GmbH | Unclassified | IPv4 IPv6 | 273 |
| AS203989 | Landeshauptstadt Muenchen, it@M | Unclassified | IPv4 IPv6 | 270 |
| AS215866 | ACP IT Solutions AG | Unclassified | IPv4 IPv6 | 268 |
| AS41086 | N-ERGIE Aktiengesellschaft | Unclassified | IPv4 | 245 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8767 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 2,215 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,787 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,369 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,057 |
| AS42821 | K&K Kommunikationssysteme GmbH | Unclassified | IPv4 IPv6 | 890 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 797 |
| AS12886 | LEW TelNet GmbH | Residential | IPv4 IPv6 | 723 |
| AS12657 | BayCIX GmbH | Unclassified | IPv4 IPv6 | 375 |
| AS24845 | Landeshauptstadt Muenchen, it@M | Unclassified | IPv4 IPv6 | 341 |
| AS29504 | Freenet Liberec, z.s. | Unclassified | IPv4 IPv6 | 340 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.