QTS Ashburn
BGP inherited
Cluster stats
| Netblocks | 6 |
| All fragments | 43 blocks across 12 clusters |
| Cluster ID | 193382479 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 1 shared RIR contact/maintainer handle |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-06
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 206.53.170.39/32 | QTS Ashburn | PEERINGDB | ASSIGNED | ● high |
| 206.55.197.226/32 | QTS Ashburn | PEERINGDB | ASSIGNED | ● high |
| 206.126.236.135/32 | QTS Ashburn | PEERINGDB | ASSIGNED | ● high |
| 2001:504:0:2:0:2:9748:1/128 | QTS Ashburn | PEERINGDB | ASSIGNED | ● high |
| 2001:504:31::7434:1/128 | QTS Ashburn | PEERINGDB | ASSIGNED | ● high |
| 2606:a980:0:3::27/128 | QTS Ashburn | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(4 of 6)
No discrepancies found among checked blocks.
NIC Handles
AS29748