Observed topology
AS42689 GLIDE
Residential APNIC
Transit
Upstream networks
Networks observed carrying traffic for AS42689: 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 |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 5,784 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 5,097 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,382 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,059 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 371 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 355 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 IPv6 | 354 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 354 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 354 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 354 |
Transit
Downstream networks
Networks for which AS42689 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS49683 | MASSIVEGRID LTD | Unclassified | IPv4 IPv6 | 729 |
| AS207916 | Velocity1 Limited | Unclassified | IPv4 | 295 |
| AS212027 | PebbleHost Ltd | Hosting | IPv4 IPv6 | 200 |
| AS210924 | SSD Networks Limited | Unclassified | IPv4 IPv6 | 151 |
| AS43059 | IT Support Services Team Limited | Unclassified | IPv4 IPv6 | 92 |
| AS47351 | Red Technology Solutions Limited | Unclassified | IPv4 | 61 |
| AS398465 | Rackdog, LLC | Residential | IPv4 | 43 |
| AS48961 | Glide Student & Residential Limited | Unclassified | IPv6 | 33 |
| AS57650 | Nomios UK&I Limited | Unclassified | IPv6 | 3 |
Adjacency
Adjacent networks
Every AS seen directly next to AS42689 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 6,285 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 5,450 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,503 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,203 |
| AS49683 | MASSIVEGRID LTD | Unclassified | IPv4 IPv6 | 729 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 403 |
| AS42708 | Glesys AB | Unclassified | IPv4 | 403 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 IPv6 | 402 |
| AS3741 | Dimension Data | Unclassified | IPv4 | 391 |
| AS31500 | Global Network Management Inc | Unclassified | IPv4 | 372 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-17 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.18M 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.