Observed topology
AS43668 BIGNET-AS
Residential Spamhaus ASN-DROP RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS43668: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 445 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 251 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 104 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 76 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 | 36 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 22 |
| AS8218 | Zayo Infrastructure France SA | Unclassified | IPv6 | 14 |
| AS34927 | iFog GmbH | Hosting | IPv4 | 8 |
Transit
Downstream networks
Networks for which AS43668 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS211707 | LLC "IT NETWORKS CHAT" | Unclassified | IPv4 IPv6 | 274 |
| AS57234 | LLC "IT NETWORKS CHAT" | Unclassified | IPv6 | 238 |
| AS35144 | Dream Line LTD | Unclassified | IPv4 | 210 |
| AS57999 | LLC DataNet ISP | Residential | IPv4 | 143 |
| AS43050 | Ivankov Daniil Eliseevich | Unclassified | IPv4 | 141 |
| AS51124 | FOP Dolgiy Andriy Fedorovuch | Unclassified | IPv4 | 122 |
| AS28858 | Lecos Online Ltd. | Unclassified | IPv4 | 120 |
| AS43743 | Kruiz LLC | Unclassified | IPv4 | 120 |
| AS20516 | Sky Vision Ukraine Ltd | Residential | IPv4 | 104 |
| AS210373 | IrpenComunikaciaService LLC | Unclassified | IPv6 | 102 |
Adjacency
Adjacent networks
Every AS seen directly next to AS43668 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,726 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 684 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 646 |
| AS50263 | A-Systems Sp. z o.o. | Unclassified | IPv4 IPv6 | 319 |
| AS211707 | LLC "IT NETWORKS CHAT" | Unclassified | IPv4 IPv6 | 274 |
| AS35144 | Dream Line LTD | Unclassified | IPv4 | 264 |
| AS57234 | LLC "IT NETWORKS CHAT" | Unclassified | IPv6 | 238 |
| AS6768 | "EUROTELE-PLUS" LLC | Unclassified | IPv4 | 211 |
| AS28858 | Lecos Online Ltd. | Unclassified | IPv4 | 180 |
| AS57999 | LLC DataNet ISP | Residential | IPv4 | 143 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.