Observed topology
AS61049 EXASCALE
Residential RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS61049: 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 | 290 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 249 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 126 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 72 |
| AS50304 | Blix Solutions AS | Unclassified | IPv4 IPv6 | 46 |
| AS24482 | SG.GS | Hosting | IPv4 IPv6 | 23 |
| AS48185 | team.blue NV | Unclassified | IPv4 IPv6 | 23 |
| AS50300 | CustodianDC Limited | Unclassified | IPv4 IPv6 | 23 |
| AS204092 | Association GRIFON | Unclassified | IPv4 IPv6 | 23 |
| AS48362 | Stadtwerke Feldkirch | Residential | IPv4 IPv6 | 21 |
Transit
Downstream networks
Networks for which AS61049 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS41847 | Daniel O'Mahony | Unclassified | IPv4 IPv6 | 477 |
| AS199462 | NETISP LTD | Unclassified | IPv4 IPv6 | 242 |
| AS215000 | Country Connect Ltd | Unclassified | IPv4 IPv6 | 222 |
| AS215047 | DSV Communications Limited | Unclassified | IPv4 IPv6 | 208 |
| AS36231 | FZCO | Hosting | IPv4 IPv6 | 195 |
| AS31493 | TWENTYTWENTYMEDIA LIMITED | Unclassified | IPv4 IPv6 | 165 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 120 |
| AS208804 | Technological Services Limited | Unclassified | IPv4 | 120 |
| AS210757 | Blackbird Solutions Limited | Unclassified | IPv4 | 120 |
| AS48070 | DSM (GB) Limited | Hosting | IPv4 IPv6 | 118 |
Adjacency
Adjacent networks
Every AS seen directly next to AS61049 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS174 | Cogent Communications, LLC | Transit | IPv4 | 1,103 |
| AS34927 | iFog GmbH | Hosting | IPv4 IPv6 | 1,069 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 790 |
| AS41847 | Daniel O'Mahony | Unclassified | IPv4 IPv6 | 768 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 IPv6 | 717 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 497 |
| AS44355 | Colocation Ltd | Hosting | IPv4 IPv6 | 420 |
| AS207841 | Inferno Communications Ltd | Unclassified | IPv4 IPv6 | 413 |
| AS401753 | BIXCE Inc | Unclassified | IPv4 IPv6 | 323 |
| AS215000 | Country Connect Ltd | Unclassified | IPv4 IPv6 | 284 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-14 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.25M 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.