Network · data from 2026-11-12
AS394968 QTS Chicago
Registry name: QTS-CHI - Quality Technology Services, LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS394968, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 209.10.244.0/24 | No ROA | Nonecovered by 209.10.240.0/21 | 673 100% |
| 66.197.117.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 69.5.76.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 205.159.128.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 209.10.192.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
| 209.10.240.0/21 | No ROA | Other IRR onlyRADB | 671 100% |
| 2606:c280::/32 | No ROA | Other IRR onlyRADB | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS394968: AS-QTS-394968. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS394968 isn't in the set, or no route object for AS394968 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS394968 in it | Not covered |
|---|---|---|---|---|---|
| AS-QTS-394968 | RADB | 16 | 1 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 18 are in fix.csv.
- ROA: none7
- Route object: none1
- Route object: RIR6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 209.10.244.0/24 | No ROA covers it. Add a ROA for AS394968, maxLength 24. |
| Route object: none | 209.10.244.0/24 | No route object for it. A route object for 209.10.240.0/21 with origin AS394968 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394968 in the RIR database for the space. |
| ROA: none | 66.197.117.0/24 | No ROA covers it. Add a ROA for AS394968, maxLength 24. |
| Route object: RIR | 66.197.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 69.5.76.0/24 | No ROA covers it. Add a ROA for AS394968, maxLength 24. |
| Route object: RIR | 69.5.76.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 205.159.128.0/24 | No ROA covers it. Add a ROA for AS394968, maxLength 24. |
| Route object: RIR | 205.159.128.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.10.192.0/21 | No ROA covers it. Add a ROA for AS394968, maxLength 21. |
| Route object: RIR | 209.10.192.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 209.10.240.0/21 | No ROA covers it. Add a ROA for AS394968, maxLength 21. |
| Route object: RIR | 209.10.240.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2606:c280::/32 | No ROA covers it. Add a ROA for AS394968, maxLength 32. |
| Route object: RIR | 2606:c280::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS394968 whose prefix no peer sees AS394968 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 65.74.136.0/24 | RADB | No ROA |
| 209.10.240.0/20 | RADB | No ROA |
| 209.10.240.0/24 | RADB | No ROA |
| 2001:470:4f6::/48 | ARIN | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.