Observed topology
AS43048 MITIGATOR-CLOUD
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS43048: 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 |
|---|---|---|---|---|
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 161 |
| AS8732 | JSC Comcor | Unclassified | IPv4 IPv6 | 78 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 68 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 60 |
| AS201589 | "EDGEAM" LLC | Unclassified | IPv4 | 28 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 8 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 8 |
| AS56655 | Gigahost AS | Unclassified | IPv4 IPv6 | 8 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 IPv6 | 8 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 7 |
Transit
Downstream networks
Networks for which AS43048 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS207104 | "BiZone" LLC | Unclassified | IPv4 IPv6 | 313 |
| AS51464 | MITIGATOR CLOUD LLC | Unclassified | IPv4 | 304 |
| AS206955 | EVOTOR LLC | Unclassified | IPv4 | 180 |
| AS201804 | National Insurance Information System JSC | Unclassified | IPv4 | 130 |
| AS52016 | JSC ADFACT | Unclassified | IPv4 | 120 |
| AS215259 | Evotor OFD LLC | Unclassified | IPv4 | 60 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43048 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS202984 | Chernyshov Aleksandr Aleksandrovich | Unclassified | IPv4 | 526 |
| AS207104 | "BiZone" LLC | Unclassified | IPv4 IPv6 | 313 |
| AS51464 | MITIGATOR CLOUD LLC | Unclassified | IPv4 | 304 |
| AS57304 | JSC "RetnNet" | Unclassified | IPv4 IPv6 | 252 |
| AS8732 | JSC Comcor | Unclassified | IPv4 IPv6 | 241 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 199 |
| AS206955 | EVOTOR LLC | Unclassified | IPv4 | 180 |
| AS201804 | National Insurance Information System JSC | Unclassified | IPv4 | 130 |
| AS52016 | JSC ADFACT | Unclassified | IPv4 | 120 |
| AS201589 | "EDGEAM" LLC | Unclassified | IPv4 | 84 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-19 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.