Observed topology
AS213753 INTEREDGE
Unclassified Spamhaus ASN-DROP RIPE Enterprise
Transit
Upstream networks
Networks observed carrying traffic for AS213753: 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 | 97 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 77 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 31 |
| AS1103 | SURF B.V. | Unclassified | IPv4 | 3 |
| AS24482 | SG.GS | Hosting | IPv4 | 3 |
| AS37721 | Virtual Technologies & Solutions | Residential | IPv4 | 3 |
| AS204092 | Association GRIFON | Unclassified | IPv4 | 3 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 | 2 |
| AS6696 | VERIXI SA | Unclassified | IPv4 | 1 |
| AS20764 | CJSC RASCOM | Unclassified | IPv4 | 1 |
Transit
Downstream networks
Networks for which AS213753 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS213035 | Des Capital B.V. | Hosting | IPv4 | 936 |
| AS49585 | CoreRoute UG | Unclassified | IPv4 | 173 |
| AS207489 | RDK IT Solutions B.V. | Unclassified | IPv4 | 154 |
| AS26954 | Mikhail Fedorov | Unclassified | IPv4 | 144 |
| AS11967 | Hop179 OU | Unclassified | IPv4 IPv6 | 100 |
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 | 80 |
| AS209675 | Jelle Hofstee trading as AxisNetworks | Hosting | IPv4 IPv6 | 79 |
| AS21478 | Plex BV | Unclassified | IPv4 | 64 |
| AS215296 | Raoul Brouns is trading as LowPing NL | Unclassified | IPv4 IPv6 | 64 |
| AS216078 | Liam Kremer | Hosting | IPv6 | 38 |
Adjacency
Adjacent networks
Every AS seen directly next to AS213753 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,929 |
| AS213035 | Des Capital B.V. | Hosting | IPv4 | 936 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 812 |
| AS11967 | Hop179 OU | Unclassified | IPv4 IPv6 | 603 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 440 |
| AS215296 | Raoul Brouns is trading as LowPing NL | Unclassified | IPv4 IPv6 | 385 |
| AS50917 | Diederik Focko de Zee | Unclassified | IPv4 | 315 |
| AS49585 | CoreRoute UG | Unclassified | IPv4 | 205 |
| AS207489 | RDK IT Solutions B.V. | Unclassified | IPv4 | 154 |
| AS26954 | Mikhail Fedorov | Unclassified | IPv4 | 144 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-11 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.47M 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.