Observed topology
AS200449 QRATOR-CZ Qrator Labs CZ s.r.o.
Unclassified RIPE
Transit
Upstream networks
Networks observed carrying traffic for AS200449: 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 |
|---|---|---|---|---|
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 148 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 141 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 130 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 103 |
| AS8966 | EMIRATES TELECOMMUNICATIONS GROUP COMPANY (ETISALAT GROUP) PJSC | Mobile | IPv4 IPv6 | 96 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 86 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 86 |
| AS6939 | Hurricane Electric LLC | Transit | IPv4 IPv6 | 73 |
| AS9002 | RETN Limited | Unclassified | IPv4 IPv6 | 67 |
| AS9583 | Sify Limited | Unclassified | IPv6 | 32 |
Transit
Downstream networks
Networks for which AS200449 was observed as the last hop before the origin, meaning it appears to provide them transit.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS209671 | Qrator Labs CZ s.r.o. | Unclassified | IPv4 IPv6 | 269 |
| AS203976 | QUAD CODE (GB) LTD | Unclassified | IPv4 | 118 |
| AS211112 | Qrator Technologies FZ-LLC | Unclassified | IPv4 IPv6 | 91 |
| AS201910 | Pragma Security SASU | Unclassified | IPv4 | 86 |
| AS201936 | REDSTART GROUP HOLDING LTD | Unclassified | IPv4 | 59 |
| AS12993 | Sabiedriba ar ierobezotu atbildibu DELSKA Latvia | Hosting | IPv4 | 58 |
| AS42865 | WEB3 Leaders INC | Unclassified | IPv4 | 58 |
| AS59655 | Exinity works (CY) LTD | Hosting | IPv4 | 58 |
Adjacency
Adjacent networks
Every AS seen directly next to AS200449 in a routing path, in either direction.
| AS | Network | Type | Families | Paths seen |
|---|---|---|---|---|
| AS197068 | HLL LLC | Hosting | IPv4 IPv6 | 5,528 |
| AS6461 | Zayo Bandwidth | Transit | IPv4 IPv6 | 1,714 |
| AS3356 | Level 3 Parent, LLC | Transit | IPv4 IPv6 | 1,603 |
| AS174 | Cogent Communications, LLC | Transit | IPv4 IPv6 | 977 |
| AS1299 | Arelion Sweden AB | Transit | IPv4 IPv6 | 696 |
| AS2914 | NTT America, Inc. | Transit | IPv4 IPv6 | 602 |
| AS3491 | PCCW Global (HK) Ltd. | Transit | IPv4 IPv6 | 411 |
| AS209671 | Qrator Labs CZ s.r.o. | Unclassified | IPv4 IPv6 | 269 |
| AS203976 | QUAD CODE (GB) LTD | Unclassified | IPv4 | 234 |
| AS6453 | TATA COMMUNICATIONS (AMERICA) INC | Transit | IPv4 IPv6 | 194 |
Provenance
Where this comes from
Derived from routing tables collected at 2026-11-08 10:00 UTC by route-views2,rrc00, as seen from 75 BGP vantage points across 73.00M 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.