Observed topology
AS8280 SYNAPSECOM-AS SYNAPSECOM TELECOMS S.A.
Hosting RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS8280: 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 |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,048 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 407 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 326 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 185 |
| AS216285 | MYIP NETWORKS G.P. | Hosting | IPv4 IPv6 | 86 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 | 34 |
| AS208972 | GIBIRNET ILETISIM HIZMETLERI SANAYI VE TICARET LIMITED SIRKETI | Unclassified | IPv4 | 34 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 4 |
Transit
Downstream networks
Networks for which AS8280 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 4,550 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,178 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 1,479 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 1,400 |
| AS8075 | Microsoft Corporation | Hosting | IPv4 IPv6 | 1,314 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,035 |
| AS15169 | Google LLC | Hosting | IPv4 IPv6 | 1,033 |
| AS3329 | Vodafone-panafon Hellenic Telecommunications Company SA | Residential | IPv4 IPv6 | 500 |
| AS25472 | Nova Telecommunications & Media Single Member S.A | Residential | IPv4 IPv6 | 335 |
| AS8254 | GREEN FLOID LLC | Hosting | IPv4 IPv6 | 304 |
Adjacency
Adjacent networks
Every AS seen directly next to AS8280 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS216285 | MYIP NETWORKS G.P. | Hosting | IPv4 IPv6 | 1,247,108 |
| AS6762 | TELECOM ITALIA SPARKLE S.p.A. | Transit | IPv4 IPv6 | 1,174,141 |
| AS137409 | GSL Networks Pty LTD | Unclassified | IPv4 IPv6 | 14,577 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 8,494 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 IPv6 | 7,890 |
| AS13335 | Cloudflare, Inc. | Hosting | IPv4 IPv6 | 7,819 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 6,072 |
| AS15169 | Google LLC | Hosting | IPv4 IPv6 | 5,299 |
| AS16509 | Amazon.com, Inc. | Hosting | IPv4 IPv6 | 4,926 |
| AS3303 | Swisscom (Schweiz) AG | Residential | IPv4 IPv6 | 2,903 |
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.