Observed topology
AS42668 NEVALINK-AS
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS42668: 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 |
|---|---|---|---|---|
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 95 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 74 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 71 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 30 |
| AS24482 | SG.GS | Hosting | IPv4 | 5 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 5 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 5 |
| AS56655 | Gigahost AS | Unclassified | IPv4 | 5 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 5 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 4 |
Transit
Downstream networks
Networks for which AS42668 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS39033 | Mediaoperator LLC | Unclassified | IPv4 | 26 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42668 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 95 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 85 |
| AS31133 | PJSC MegaFon | Mobile | IPv4 | 84 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 30 |
| AS39033 | Mediaoperator LLC | Unclassified | IPv4 | 26 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 6 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 5 |
| AS24482 | SG.GS | Hosting | IPv4 | 5 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 5 |
| AS49673 | Truenetwork LLC | Unclassified | IPv4 | 5 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-21 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.14M 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.