Title: Parse.ly servers and infrastructure
Author: staff
Published: August 1, 2022
Last modified: February 24, 2026

---

 1. [Parse.ly data privacy](https://docs.parse.ly/privacy/)
 2. Parse.ly servers and infrastructure

#  Parse.ly servers and infrastructure

---

Parse.ly is hosted using enterprise-class server infrastructure and cloud services.

Our primary data processing backend is hosted using [Amazon Web Services](http://aws.amazon.com/).
Likewise for our [web crawlers](https://docs.parse.ly/crawler/), [API](https://docs.parse.ly/api/)
servers, and [dashboard](https://docs.parse.ly/dashboard/) web application servers.

**Notice**

As part of our continuous efforts to enhance the security and performance of our
services, we are making an essential change to the CDN service that acts as a cache
layer for the tracker.

### What’s Changing?

We will be switching to a new CDN system, and as part of this upgrade, we will no
longer support TLS v1.0 and v1.1 protocols. This change will be effective immediately.
Our analysis indicates that this change will impact approximately 0.0008% of our
traffic.

### Why is This Important?

The deprecation of TLS 1.0 and TLS 1.1 is crucial in ensuring a more secure and 
efficient web environment.

 * **Enhanced Security:** TLS 1.0 and TLS 1.1 are outdated protocols with known 
   vulnerabilities that attackers can exploit. By discontinuing their support, we
   reduce the risk of security breaches and protect your data more effectively.
 * **Improved Performance:** Modern protocols such as TLS 1.2 and TLS 1.3 offer 
   better performance and reliability. This upgrade will contribute to faster and
   more secure connections for most users.
 * **Compliance with Industry Standards:** Major browsers and industry leaders have
   already phased out support for these older protocols. We ensure compatibility
   and optimal performance across all platforms by aligning with these standards.

### Impact on Your Traffic

The tracker will no longer load for the small percentage (0.0008%) of traffic that
still relies on TLS 1.0 and TLS 1.1. This means no pageviews or heartbeats will 
be recorded from these sources, and this traffic will be lost. The impact of this
change will vary depending on the specific demographics of your site’s visitors.

### Next Steps

We recommend you review your visitor data to assess the potential impact on your
site. While the affected traffic is minimal, understanding how it might influence
your specific metrics can help you better prepare for this transition.

If you have any questions or need further assistance, please do not hesitate to 
contact our support team. We are here to help you ensure a smooth transition and
to provide any additional information you might need.

Thank you for your understanding and cooperation as we work to enhance the security
and performance of our services.

We also use Amazon’s bulk data processing ([Elastic Map/Reduce](http://aws.amazon.com/elasticmapreduce/))
and archival data storage ([S3](http://aws.amazon.com/s3/)).

Our infrastructure will automatically select the nearest edge server to your visitors
based on geographic proximity. We take latency and uptime of our data collection
services very seriously, and publish [public uptime reports](https://status.parsely.com/).

We use [WordPress VIP Platform’s content delivery network (CDN)](https://docs.wpvip.com/infrastructure/edge-cache/)
for all of our data collection and JavaScript code serving. You can see a full list
of our edge locations here: [https://docs.wpvip.com/infrastructure/edge-cache/global-locations/](https://docs.wpvip.com/infrastructure/edge-cache/global-locations/).

Last updated: February 24, 2026