Observed topology
AS211826 ISTQSERVERS-AS
Unclassified DROP-listed space RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS211826: 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,055 |
| AS5511 | Orange S.A. | Transit | IPv4 | 341 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 219 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 188 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 157 |
| AS50670 | VTEL HOLDINGS LIMITED/JORDAN CO. | Unclassified | IPv4 | 118 |
| AS64289 | Macarne.com | Unclassified | IPv4 IPv6 | 113 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 91 |
| AS13287 | FALBOX S.L. trading as NIXVAL | Hosting | IPv4 | 58 |
| AS9002 | RETN Limited | Unclassified | IPv4 | 49 |
Transit
Downstream networks
Networks for which AS211826 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS141718 | haoxiangyun | Unclassified | IPv4 | 1,854 |
| AS214467 | DIGIDED LTD | Unclassified | IPv4 | 543 |
| AS208949 | HBING LIMITED | Unclassified | IPv4 | 477 |
| AS211484 | YSZ TRADING CO., LIMITED | Unclassified | IPv4 | 315 |
| AS214760 | LS4KDC LIMITED | Unclassified | IPv4 | 250 |
| AS142270 | ohae/posinet | Unclassified | IPv4 | 241 |
| AS212042 | Stability for Integrated Server Hosting Ltd | Unclassified | IPv4 | 184 |
| AS133153 | IPv4 Superhub Limited | Unclassified | IPv4 | 178 |
| AS199458 | LLC Rusbuilding | Unclassified | IPv4 | 120 |
| AS215821 | London Digital Systems LTD | Unclassified | IPv4 | 59 |
Adjacency
Adjacent networks
Every AS seen directly next to AS211826 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 2,997 |
| AS141718 | haoxiangyun | Unclassified | IPv4 | 2,677 |
| AS214467 | DIGIDED LTD | Unclassified | IPv4 IPv6 | 1,401 |
| AS3257 | GTT Communications Inc. | Transit | IPv4 | 1,237 |
| AS5511 | Orange S.A. | Transit | IPv4 | 818 |
| AS33891 | Core-Backbone GmbH | Hosting | IPv4 | 687 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 | 653 |
| AS5405 | Inter.link GmbH | Unclassified | IPv4 | 507 |
| AS142270 | ohae/posinet | Unclassified | IPv4 | 487 |
| AS208949 | HBING LIMITED | Unclassified | IPv4 | 477 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-10-25 12:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.17M 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.