Observed topology
AS3255 UARNET-AS LLC EKSINTECH
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS3255: 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 | 12,148 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 1,309 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,062 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 792 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 550 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 291 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 279 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 275 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 261 |
| AS28917 | Fiord Networks, UAB | Unclassified | IPv4 | 23 |
Transit
Downstream networks
Networks for which AS3255 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6849 | JSC "Ukrtelecom" | Residential | IPv4 | 2,560 |
| AS34814 | Osnova-Internet LLC | Unclassified | IPv4 | 1,408 |
| AS34661 | TOV TRK "Briz" | Residential | IPv4 IPv6 | 1,118 |
| AS201094 | Mulgin Alexander Sergeevich | Unclassified | IPv4 IPv6 | 1,074 |
| AS197522 | Kaluska informatsiyna merezha LLC | Unclassified | IPv4 IPv6 | 1,030 |
| AS31556 | ARKADA-X Ltd. | Unclassified | IPv4 IPv6 | 924 |
| AS25082 | Viner Telecom LLC | Unclassified | IPv4 | 819 |
| AS43103 | ONE TELECOM ltd | Unclassified | IPv4 | 813 |
| AS24945 | Telecommunication Company Vinteleport Ltd. | Unclassified | IPv4 IPv6 | 767 |
| AS48323 | PP Neiron Systems | Unclassified | IPv4 | 694 |
Adjacency
Adjacent networks
Every AS seen directly next to AS3255 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 44,702 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 3,792 |
| AS2914 | NTT America, Inc. | Transit | IPv4 | 3,755 |
| AS39608 | Lanet Network Ltd | Residential | IPv4 | 2,822 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 2,795 |
| AS6849 | JSC "Ukrtelecom" | Residential | IPv4 | 2,560 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,339 |
| AS43103 | ONE TELECOM ltd | Unclassified | IPv4 | 1,879 |
| AS34814 | Osnova-Internet LLC | Unclassified | IPv4 | 1,656 |
| AS6723 | "AS6723" LIMITED LIABILITY COMPANY | Unclassified | IPv4 IPv6 | 1,568 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-07 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 72.97M 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.