Observed topology
AS8680 SURE-International-Limited Sure (Guernsey) Limited
Residential RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS8680: 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 | 1,199 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 919 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 520 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 132 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 119 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 88 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 75 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 62 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 62 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 62 |
Transit
Downstream networks
Networks for which AS8680 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS13173 | Foreshore Limited | Unclassified | IPv4 IPv6 | 738 |
| AS17458 | Sure (Diego Garcia) Limited | Unclassified | IPv4 | 324 |
| AS60492 | Mimecast Services Limited | Unclassified | IPv4 | 289 |
| AS61143 | Jersey Airtel Limited | Unclassified | IPv4 | 174 |
| AS34497 | Logicalis Guernsey Ltd | Unclassified | IPv4 | 118 |
| AS201898 | BlueWave Communications Limited | Unclassified | IPv4 IPv6 | 91 |
| AS210841 | Sure South Atlantic Limited | Unclassified | IPv4 | 84 |
| AS211913 | Guernsey Airtel Limited | Unclassified | IPv4 | 59 |
| AS25040 | I.T. Consultancy Limited | Unclassified | IPv4 | 7 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8680 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,873 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,640 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 779 |
| AS13173 | Foreshore Limited | Unclassified | IPv4 IPv6 | 738 |
| AS17458 | Sure (Diego Garcia) Limited | Unclassified | IPv4 | 324 |
| AS60492 | Mimecast Services Limited | Unclassified | IPv4 | 289 |
| AS61143 | Jersey Airtel Limited | Unclassified | IPv4 | 174 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 165 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 | 132 |
| AS34497 | Logicalis Guernsey Ltd | Unclassified | IPv4 | 118 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-05 10:00 UTC by route-views2,rrc00, as seen from 76 BGP vantage points across 73.57M 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.