Observed topology
AS260 GTT-DXB
Unclassified ARIN NSP
Transit
Upstream networks
Networks observed carrying traffic for AS260: 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.
Transit
Downstream networks
Networks for which AS260 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS19905 | Vercara, LLC | Hosting | IPv4 IPv6 | 633 |
| AS9009 | M247 Europe SRL | Hosting | IPv4 | 388 |
| AS51857 | MTel B.V. | Unclassified | IPv4 IPv6 | 186 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 126 |
| AS213931 | Alaitisal Computers and Requisites Trading LLC | Unclassified | IPv4 | 101 |
| AS206168 | JFS B.V. | Unclassified | IPv4 IPv6 | 91 |
| AS44444 | Forcepoint UK Limited | Hosting | IPv4 | 74 |
| AS53766 | Arista Networks, Inc. | Unclassified | IPv4 IPv6 | 43 |
| AS29457 | Options Technology Ltd | Unclassified | IPv4 | 4 |
| AS40934 | Fortinet Inc. | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS260 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS15412 | Flag Telecom UK Limited | Unclassified | IPv4 IPv6 | 1,231 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 784 |
| AS19905 | Vercara, LLC | Hosting | IPv4 IPv6 | 633 |
| AS9009 | M247 Europe SRL | Hosting | IPv4 | 436 |
| AS51857 | MTel B.V. | Unclassified | IPv4 IPv6 | 186 |
| AS213931 | Alaitisal Computers and Requisites Trading LLC | Unclassified | IPv4 | 168 |
| AS200612 | Gulf Bridge International Inc. | Unclassified | IPv4 | 131 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 126 |
| AS206168 | JFS B.V. | Unclassified | IPv4 IPv6 | 91 |
| AS44444 | Forcepoint UK Limited | Hosting | IPv4 | 74 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-26 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.