Observed topology
AS206499 MMNETWORKS MM NETWORKS
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS206499: 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.
Transit
Downstream networks
Networks for which AS206499 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 4,840 |
| AS8866 | Vivacom Bulgaria EAD | Residential | IPv4 | 978 |
| AS12735 | TurkNet Iletisim Hizmetleri A.S. | Unclassified | IPv4 | 582 |
| AS7713 | PT Telekomunikasi Indonesia | Residential | IPv4 | 506 |
| AS9658 | Eastern Telecoms Phils., Inc. | Unclassified | IPv4 | 445 |
| AS9541 | Cyber Internet Services (Pvt) Ltd. | Hosting | IPv4 | 322 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 235 |
| AS20911 | Net-Surf.net Ltd. | Residential | IPv4 | 175 |
| AS25374 | Haskovo | Residential | IPv4 | 145 |
| AS14593 | Space Exploration Technologies Corporation | Residential | IPv4 | 106 |
Adjacency
Adjacent networks
Every AS seen directly next to AS206499 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 919,595 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 97,108 |
| AS9498 | BHARTI Airtel Ltd. | Mobile | IPv4 | 28,282 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 4,601 |
| AS24482 | SG.GS | Hosting | IPv4 | 3,437 |
| AS29049 | Delta Telecom Ltd | Residential | IPv4 | 2,394 |
| AS14840 | BR.Digital Telecom | Unclassified | IPv4 | 2,152 |
| AS57344 | Telehouse EAD | Residential | IPv4 | 1,503 |
| AS8866 | Vivacom Bulgaria EAD | Residential | IPv4 | 1,428 |
| AS55818 | MC-IX Matrix Internet Exchange RS-1 | Residential | IPv4 | 1,273 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-24 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.94M 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.