Observed topology
AS13009 VDATA
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS13009: 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 |
|---|---|---|---|---|
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 681 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 385 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 239 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 65 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 42 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 26 |
| AS3741 | Dimension Data | Unclassified | IPv4 | 24 |
| AS12552 | GlobalConnect AB | Unclassified | IPv4 | 24 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 24 |
| AS37100 | SEACOM Limited | Unclassified | IPv4 | 24 |
Transit
Downstream networks
Networks for which AS13009 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31463 | Redcentric Solutions Ltd | Hosting | IPv4 IPv6 | 2,006 |
| AS15533 | Redcentric Solutions Ltd | Hosting | IPv4 IPv6 | 942 |
| AS30914 | Redcentric Solutions Ltd | Hosting | IPv4 | 406 |
| AS8419 | Redcentric Solutions Ltd | Unclassified | IPv4 IPv6 | 327 |
| AS5552 | Redcentric Solutions Ltd | Unclassified | IPv4 IPv6 | 211 |
| AS62364 | Plymouth City Council | Unclassified | IPv4 | 118 |
| AS15324 | Barracuda Networks, Inc. | Unclassified | IPv4 | 59 |
| AS205106 | Pea Soup Hosting Limited | Unclassified | IPv4 | 59 |
| AS51926 | PageOne Communications Ltd | Unclassified | IPv4 | 28 |
| AS207552 | Cambridge Consultants Limited | Unclassified | IPv4 | 26 |
Adjacency
Adjacent networks
Every AS seen directly next to AS13009 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS31463 | Redcentric Solutions Ltd | Hosting | IPv4 IPv6 | 2,270 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,988 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 1,701 |
| AS15533 | Redcentric Solutions Ltd | Hosting | IPv4 IPv6 | 1,348 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 1,132 |
| AS30914 | Redcentric Solutions Ltd | Hosting | IPv4 | 406 |
| AS8419 | Redcentric Solutions Ltd | Unclassified | IPv4 IPv6 | 327 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 276 |
| AS5552 | Redcentric Solutions Ltd | Unclassified | IPv4 IPv6 | 211 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 | 176 |
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.