Observed topology
AS1764 NEXTLAYER-AS
Unclassified RIPE NSP
Transit
Upstream networks
Networks observed carrying traffic for AS1764: 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 |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 680 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 588 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 493 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 492 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 223 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 220 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 212 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 212 |
| AS1836 | green.ch AG | Residential | IPv4 IPv6 | 83 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 83 |
Transit
Downstream networks
Networks for which AS1764 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS5403 | APA-IT Informations Technologie G.m.b.H | Hosting | IPv4 IPv6 | 2,913 |
| AS9009 | M247 Europe SRL | Hosting | IPv4 IPv6 | 2,294 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,093 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 1,654 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 1,476 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 1,272 |
| AS25255 | Hutchison Drei Austria GmbH | Residential | IPv4 IPv6 | 1,048 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 965 |
| AS44133 | IPAX GmbH | Unclassified | IPv4 IPv6 | 959 |
| AS28771 | Flughafen Wien Aktiengesellschaft | Unclassified | IPv4 IPv6 | 701 |
Adjacency
Adjacent networks
Every AS seen directly next to AS1764 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 316,416 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 104,343 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 76,520 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 63,445 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 23,386 |
| AS4134 | No.31,Jin-rong Street | Residential | IPv4 IPv6 | 23,288 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 16,370 |
| AS25255 | Hutchison Drei Austria GmbH | Residential | IPv4 IPv6 | 9,335 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 7,732 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 5,494 |
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.