Observed topology
AS41039 DON-FTTH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS41039: 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 |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 1,575 |
| AS201776 | Miranda-Media Ltd | Unclassified | IPv4 | 193 |
| AS62255 | BiMajLink d.o.o. | Unclassified | IPv4 | 158 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 86 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 78 |
| AS50673 | Serverius Holding B.V. | Unclassified | IPv4 | 67 |
| AS24482 | SG.GS | Hosting | IPv4 | 35 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 35 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 35 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 35 |
Transit
Downstream networks
Networks for which AS41039 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS196638 | JSC Promtelecom | Unclassified | IPv4 | 284 |
| AS211101 | Nasteka Maksim Viktorovich | Unclassified | IPv4 | 198 |
| AS197643 | DKT Ltd Television and Radio broadcasting company | Unclassified | IPv4 | 193 |
| AS56766 | Bahilov Ilya Vitalievich PE | Unclassified | IPv4 | 191 |
| AS51725 | Private Enterprise Tron Vitaliy Vladimirovich | Unclassified | IPv4 | 186 |
| AS213544 | OOO TRK "Perspektiva" | Unclassified | IPv4 | 182 |
| AS50052 | TORANET LTD | Unclassified | IPv4 | 128 |
| AS57005 | PE Homich Nataliya G. | Unclassified | IPv4 | 110 |
| AS196767 | INMART.UA LLC | Unclassified | IPv4 | 65 |
| AS39558 | IP Resurs Ltd. | Unclassified | IPv4 | 64 |
Adjacency
Adjacent networks
Every AS seen directly next to AS41039 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS35598 | INETCOM CARRIER LLC | Unclassified | IPv4 | 1,606 |
| AS201776 | Miranda-Media Ltd | Unclassified | IPv4 | 1,281 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 436 |
| AS196638 | JSC Promtelecom | Unclassified | IPv4 | 284 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 274 |
| AS56766 | Bahilov Ilya Vitalievich PE | Unclassified | IPv4 | 270 |
| AS211101 | Nasteka Maksim Viktorovich | Unclassified | IPv4 | 210 |
| AS197643 | DKT Ltd Television and Radio broadcasting company | Unclassified | IPv4 | 193 |
| AS51725 | Private Enterprise Tron Vitaliy Vladimirovich | Unclassified | IPv4 | 186 |
| AS47809 | Private Enterprise Matsak Ivan Anatolievich | Unclassified | IPv4 | 184 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.