Observed topology
AS11967 HOP179 Hop179 OU
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS11967: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 628 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 106 |
| AS835 | GoCodeIT Inc | Unclassified | IPv4 IPv6 | 101 |
| AS215828 | Tizian Maxime Weigt trading as "TMW Global Networks" | Hosting | IPv4 IPv6 | 76 |
| AS214809 | Jere Kiitola trading as Stocade | Unclassified | IPv4 IPv6 | 72 |
| AS213753 | InterEdge B.V. | Unclassified | IPv4 | 65 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 27 |
| AS37989 | DCS1 Pte. Ltd. | Hosting | IPv4 IPv6 | 26 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 26 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 25 |
Transit
Downstream networks
Networks for which AS11967 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS218343 | Mikhail Popov | Unclassified | IPv6 | 512 |
| AS215017 | EMIRASLAN EMIRASLANOV | Unclassified | IPv4 IPv6 | 172 |
| AS204921 | zhenyun sun | Unclassified | IPv4 IPv6 | 163 |
| AS213423 | Lukas Hagen | Unclassified | IPv4 IPv6 | 161 |
| AS154950 | CRAPPLET INFOTECH PRIVATE LIMITED | Unclassified | IPv4 | 158 |
| AS208694 | LEON AARON TIEKOETTER | Unclassified | IPv6 | 148 |
| AS209710 | SNRD NETWORKS LIMITED | Hosting | IPv6 | 148 |
| AS208753 | Marco d'Angelo | Unclassified | IPv4 IPv6 | 142 |
| AS218995 | Bobeica Mihaita David | Unclassified | IPv6 | 142 |
| AS59449 | Mitja Herbaj | Unclassified | IPv6 | 106 |
Adjacency
Adjacent networks
Every AS seen directly next to AS11967 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 2,580 |
| AS213753 | InterEdge B.V. | Unclassified | IPv4 IPv6 | 882 |
| AS215828 | Tizian Maxime Weigt trading as "TMW Global Networks" | Hosting | IPv4 IPv6 | 785 |
| AS218343 | Mikhail Popov | Unclassified | IPv6 | 512 |
| AS214809 | Jere Kiitola trading as Stocade | Unclassified | IPv4 IPv6 | 366 |
| AS218995 | Bobeica Mihaita David | Unclassified | IPv6 | 229 |
| AS197324 | Vladyslav Koba | Unclassified | IPv4 IPv6 | 210 |
| AS215017 | EMIRASLAN EMIRASLANOV | Unclassified | IPv4 IPv6 | 204 |
| AS204921 | zhenyun sun | Unclassified | IPv4 IPv6 | 163 |
| AS213423 | Lukas Hagen | Unclassified | IPv4 IPv6 | 161 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.