Observed topology
AS21949 BEANFIELD - Beanfield Technologies Inc.
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS21949: 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 |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 1,147 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 587 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 464 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 450 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 406 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 396 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 190 |
| AS1403 | EBOX | Residential | IPv4 IPv6 | 134 |
| AS22652 | Videotron Ltee | Residential | IPv4 IPv6 | 132 |
| AS852 | TELUS Communications Inc. | Residential | IPv4 IPv6 | 67 |
Transit
Downstream networks
Networks for which AS21949 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS18986 | Calligo (Canada) Inc. | Hosting | IPv4 | 2,546 |
| AS31798 | DataCity | Hosting | IPv4 | 2,136 |
| AS26832 | Rica Web Services | Hosting | IPv4 IPv6 | 1,317 |
| AS395570 | Beanfield Technologies Inc. | Unclassified | IPv4 | 1,121 |
| AS23498 | Beanfield Technologies Inc. | Unclassified | IPv4 | 986 |
| AS394520 | The Law Society of Upper Canada | Unclassified | IPv4 IPv6 | 934 |
| AS395569 | Konica Minolta Business Solutions (Canada) LTD | Unclassified | IPv4 | 812 |
| AS33549 | Whipcord Edge Data Centers Inc. | Hosting | IPv4 IPv6 | 656 |
| AS30236 | Cronomagic Canada Inc. | Unclassified | IPv4 | 631 |
| AS21548 | Beanfield Technologies Inc. | Unclassified | IPv4 IPv6 | 594 |
Adjacency
Adjacent networks
Every AS seen directly next to AS21949 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 6,375 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 4,216 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 3,561 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 3,496 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 2,555 |
| AS18986 | Calligo (Canada) Inc. | Hosting | IPv4 | 2,546 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 2,543 |
| AS31798 | DataCity | Hosting | IPv4 | 2,206 |
| AS23498 | Beanfield Technologies Inc. | Unclassified | IPv4 | 1,743 |
| AS34549 | meerfarbig GmbH & Co. KG | Hosting | IPv4 IPv6 | 1,535 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-11 10:00 UTC by route-views2,rrc00, as seen from 74 BGP vantage points across 73.24M 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.