QTS Richmond
BGP inherited
Cluster stats
Netblocks8
All fragments 43 blocks across 12 clusters
Cluster ID191871307
RegistryPEERINGDB
Customersfind 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

3 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-12

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
206.53.137.38/32 QTS Richmond PEERINGDB ASSIGNED ● high
206.53.170.36/32 QTS Richmond PEERINGDB ASSIGNED ● high
206.55.197.243/32 QTS Richmond PEERINGDB ASSIGNED ● high
206.71.9.11/32 QTS Richmond PEERINGDB ASSIGNED ● high
2001:504:31::d293:1/128 QTS Richmond PEERINGDB ASSIGNED ● high
2001:504:44::5:3907:1/128 QTS Richmond PEERINGDB ASSIGNED ● high
2001:504:79::11/128 QTS Richmond PEERINGDB ASSIGNED ● high
2606:a980:0:3::24/128 QTS Richmond PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: C how networks compare →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS53907