Observed topology
AS49535 EMIND E-Mind Srl
Residential RIPE Cable/DSL/ISP
Transit
Upstream networks
Networks observed carrying traffic for AS49535: 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 |
|---|---|---|---|---|
| AS12874 | Fastweb SpA | Residential | IPv4 | 394 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 312 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 13 |
| AS31543 | myNet GmbH | Residential | IPv4 IPv6 | 13 |
| AS21309 | HERABIT S.p.A. | Residential | IPv4 | 12 |
| AS59919 | Brainbox S.r.l. | Residential | IPv4 | 12 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 1 |
Transit
Downstream networks
Networks for which AS49535 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS204903 | FLASHSTART GROUP SRL | Unclassified | IPv4 | 1 |
Adjacency
Adjacent networks
Every AS seen directly next to AS49535 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS12874 | Fastweb SpA | Residential | IPv4 | 394 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 312 |
| AS6939 | Hurricane Electric LLC | Transit | IPv6 | 14 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 13 |
| AS31543 | myNet GmbH | Residential | IPv4 IPv6 | 13 |
| AS59919 | Brainbox S.r.l. | Residential | IPv4 | 13 |
| AS21309 | HERABIT S.p.A. | Residential | IPv4 | 12 |
| AS29632 | Netassist International EOOD | Unclassified | IPv6 | 1 |
| AS204903 | FLASHSTART GROUP SRL | Unclassified | IPv4 | 1 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.