From 2b4f23a8111b5e271d95e0aae2d8e4e889534c17 Mon Sep 17 00:00:00 2001
From: Donna <6880495+Tofufu@users.noreply.github.com>
Date: Thu, 26 Feb 2026 13:28:41 -0800
Subject: [PATCH 1/2] Update changelog for TLS 1.0/1.1 deprecation
Fixing the headers
---
pages/changelogs/2026-02-26-tls1011-deprecation.mdx | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/pages/changelogs/2026-02-26-tls1011-deprecation.mdx b/pages/changelogs/2026-02-26-tls1011-deprecation.mdx
index 66ec5ec726..52549a79f4 100644
--- a/pages/changelogs/2026-02-26-tls1011-deprecation.mdx
+++ b/pages/changelogs/2026-02-26-tls1011-deprecation.mdx
@@ -49,7 +49,7 @@ Mixpanel will also mirror the commonly accepted standards for TLS 1.2 and TLS 1.
| | TLS_AES256_GCM_SHA384 |
| | TLS_CHACHA20_POLY1305_SHA256 |
-# What’s the impact of this change?
+# What’s the impact of this change?
Any data sent to Mixpanel’s Ingestion API endpoints after **April 1, 2026** via TLS 1.0 and 1.1 will not be accepted, meaning you will not receive analytics information from users who engage with your applications using the 1.0 and 1.1 versions of TLS.
@@ -78,7 +78,7 @@ Please Note: While we’ve listed some common versions above, compatibility can
For a comprehensive list of environments that may still use TLS 1.0/1.1, we recommend visiting the Browser/OS Official Documentation or referring to the [TLS Support Version History](https://en.wikipedia.org/wiki/Version_history_for_TLS/SSL_support_in_web_browsers) (External Resource).
-# How to identify affected users
+# How to identify affected users
More than 99% of Mixpanel Web and API Traffic use TLS 1.2+; however, to assess how many users are potentially affected by this change in your projects:
1. In an Insights report, select `All Events` as the primary metric
@@ -91,13 +91,13 @@ For example, the following Custom Property can help check against Chrome and Fir
-# Recommended Actions
+# Recommended Actions
- **Client-Side Tracking:** Where possible, we recommend encouraging users to update their browsers or OS to a version that communicates using TLS 1.2+.
- **Server-Side Tracking:** Verify your server environments are configured to use TLS 1.2+.
- **Protocol Migration:** If your application currently utilizes legacy TLS versions, we recommend deprecating them in favor of TLS 1.2+ to ensure long-term security and compatibility.
- **Proxying:** We understand that some devices have hardware/software limitations that may not be able to use TLS 1.2+. In these cases, if you would like to maintain tracking for these devices, you could consider implementing a proxy server that accepts TLS 1.0/1.1 from end users and forwards the tracking data to Mixpanel Ingestion APIs via TLS 1.2+.
-# Support & Inquiries
+# Support & Inquiries
We have notified users whose projects were detected receiving legacy TLS 1.0/1.1 Ingestion traffic.
If you have questions about your project’s compatibility or need general assistance, please reach out to [Mixpanel Support](/docs/response-times#contacting-mixpanel-support).
From 6f9baa0adc13354f41dff01c8db67450e9a821f1 Mon Sep 17 00:00:00 2001
From: Donna <6880495+Tofufu@users.noreply.github.com>
Date: Thu, 26 Feb 2026 17:23:12 -0800
Subject: [PATCH 2/2] Update changelog for TLS 1.0/1.1 deprecation
---
pages/changelogs/2026-02-26-tls1011-deprecation.mdx | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/pages/changelogs/2026-02-26-tls1011-deprecation.mdx b/pages/changelogs/2026-02-26-tls1011-deprecation.mdx
index 52549a79f4..14efb0858e 100644
--- a/pages/changelogs/2026-02-26-tls1011-deprecation.mdx
+++ b/pages/changelogs/2026-02-26-tls1011-deprecation.mdx
@@ -49,7 +49,7 @@ Mixpanel will also mirror the commonly accepted standards for TLS 1.2 and TLS 1.
| | TLS_AES256_GCM_SHA384 |
| | TLS_CHACHA20_POLY1305_SHA256 |
-# What’s the impact of this change?
+## What’s the impact of this change?
Any data sent to Mixpanel’s Ingestion API endpoints after **April 1, 2026** via TLS 1.0 and 1.1 will not be accepted, meaning you will not receive analytics information from users who engage with your applications using the 1.0 and 1.1 versions of TLS.
@@ -78,7 +78,7 @@ Please Note: While we’ve listed some common versions above, compatibility can
For a comprehensive list of environments that may still use TLS 1.0/1.1, we recommend visiting the Browser/OS Official Documentation or referring to the [TLS Support Version History](https://en.wikipedia.org/wiki/Version_history_for_TLS/SSL_support_in_web_browsers) (External Resource).
-# How to identify affected users
+## How to identify affected users
More than 99% of Mixpanel Web and API Traffic use TLS 1.2+; however, to assess how many users are potentially affected by this change in your projects:
1. In an Insights report, select `All Events` as the primary metric
@@ -91,13 +91,13 @@ For example, the following Custom Property can help check against Chrome and Fir
-# Recommended Actions
+## Recommended Actions
- **Client-Side Tracking:** Where possible, we recommend encouraging users to update their browsers or OS to a version that communicates using TLS 1.2+.
- **Server-Side Tracking:** Verify your server environments are configured to use TLS 1.2+.
- **Protocol Migration:** If your application currently utilizes legacy TLS versions, we recommend deprecating them in favor of TLS 1.2+ to ensure long-term security and compatibility.
- **Proxying:** We understand that some devices have hardware/software limitations that may not be able to use TLS 1.2+. In these cases, if you would like to maintain tracking for these devices, you could consider implementing a proxy server that accepts TLS 1.0/1.1 from end users and forwards the tracking data to Mixpanel Ingestion APIs via TLS 1.2+.
-# Support & Inquiries
+## Support & Inquiries
We have notified users whose projects were detected receiving legacy TLS 1.0/1.1 Ingestion traffic.
If you have questions about your project’s compatibility or need general assistance, please reach out to [Mixpanel Support](/docs/response-times#contacting-mixpanel-support).