Observed topology
AS22216 SIEMENS-PLM
Unclassified ARIN
Transit
Upstream networks
Networks observed carrying traffic for AS22216: 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 |
|---|---|---|---|---|
| AS26554 | US Signal Company, L.L.C. | Unclassified | IPv4 | 293 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 207 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 99 |
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 91 |
| AS702 | Verizon Business | Unclassified | IPv4 | 58 |
| AS40107 | Quality Technology Services, LLC | Unclassified | IPv4 | 53 |
| AS33651 | Comcast Cable Communications, LLC | Unclassified | IPv4 | 40 |
| AS5488 | Proximus NV | Unclassified | IPv4 | 20 |
| AS33667 | Comcast Cable Communications, LLC | Unclassified | IPv4 | 20 |
Transit
Downstream networks
Networks for which AS22216 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS65115 | unnamed | Unclassified | IPv4 | 2 |
Adjacency
Adjacent networks
Every AS seen directly next to AS22216 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS26554 | US Signal Company, L.L.C. | Unclassified | IPv4 | 293 |
| AS7018 | AT&T Enterprises, LLC | Residential | IPv4 IPv6 | 207 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 | 99 |
| AS4230 | CLARO S.A. | Residential | IPv4 IPv6 | 91 |
| AS702 | Verizon Business | Unclassified | IPv4 | 58 |
| AS40107 | Quality Technology Services, LLC | Unclassified | IPv4 | 55 |
| AS33651 | Comcast Cable Communications, LLC | Unclassified | IPv4 | 40 |
| AS5488 | Proximus NV | Unclassified | IPv4 | 20 |
| AS33667 | Comcast Cable Communications, LLC | Unclassified | IPv4 | 20 |
| AS65115 | unnamed | Unclassified | IPv4 | 2 |
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.