Observed topology
AS43139 MAXIMUMA-AS
Unclassified RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS43139: 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 |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 | 432 |
| AS35297 | Dataline LLC | Unclassified | IPv4 IPv6 | 201 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 97 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 33 |
| AS35320 | Eurotranstelecom Ltd | Unclassified | IPv4 | 31 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 15 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 14 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 10 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv4 | 4 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 4 |
Transit
Downstream networks
Networks for which AS43139 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213724 | Maximum-Net LLC | Unclassified | IPv4 | 725 |
| AS201041 | Obltelecom LLC | Unclassified | IPv4 | 305 |
| AS209548 | IrpenComunikaciaService LLC | Unclassified | IPv4 | 183 |
| AS41586 | Ukrainian Internet Company LLC | Unclassified | IPv4 | 161 |
| AS25514 | Modus-Global LLC | Unclassified | IPv4 | 122 |
| AS42259 | "BILHORODNET" Limited Liability Company | Unclassified | IPv4 | 122 |
| AS48019 | Terra-Telecom LLC | Unclassified | IPv4 | 122 |
| AS12545 | Transcom Ltd | Unclassified | IPv4 | 61 |
| AS41467 | "DOMINET" LLC | Unclassified | IPv4 | 61 |
| AS45017 | "DOMINET" LLC | Unclassified | IPv4 | 61 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43139 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS9002 | RETN Limited | Unclassified | IPv4 | 1,847 |
| AS213724 | Maximum-Net LLC | Unclassified | IPv4 | 725 |
| AS35297 | Dataline LLC | Unclassified | IPv4 IPv6 | 495 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 431 |
| AS201041 | Obltelecom LLC | Unclassified | IPv4 | 305 |
| AS35320 | Eurotranstelecom Ltd | Unclassified | IPv4 | 267 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 | 217 |
| AS45017 | "DOMINET" LLC | Unclassified | IPv4 | 183 |
| AS209548 | IrpenComunikaciaService LLC | Unclassified | IPv4 | 183 |
| AS41586 | Ukrainian Internet Company LLC | Unclassified | IPv4 | 161 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-20 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.16M 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.