Chameleon Outage History

Chameleon is up right now

Chameleon had 9 outages in the last 2 years totaling 26h 54m of downtime — averaging 0.4 incidents per month.

There were 9 Chameleon outages since June 25, 2025 totaling 26h 54m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.trychameleon.com

Notice March 17, 2026

OAuth authentication issues

Detected by Pingoru
Mar 17, 2026, 12:47 PM UTC
Resolved
Mar 17, 2026, 12:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Mar 17, 2026, 12:47 PM UTC

    OAuth authentication was not working for approximately 3pm est Sunday 2026-03-14 to 8:30 am est Tuesday 2026-03-16

Read the full incident report →

Notice March 16, 2026

Login issues

Detected by Pingoru
Mar 16, 2026, 03:29 PM UTC
Resolved
Mar 16, 2026, 06:38 PM UTC
Duration
3h 9m
Affected: Dashboard
Timeline · 3 updates
  1. investigating Mar 16, 2026, 03:29 PM UTC

    We're looking into an issue where new magic links / OAuth / SSO are not working as expected

  2. identified Mar 16, 2026, 03:53 PM UTC

    The issue has been identified and a fix is being implemented. **Note: If you're already logged in, you will continue to stay logged in and we will likely resolve this before you are automatically logged out**

  3. resolved Mar 16, 2026, 06:38 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice December 29, 2025

Chameleon not vulnerable to MongoBleed - CVE-2025-14847

Detected by Pingoru
Dec 29, 2025, 01:00 PM UTC
Resolved
Dec 29, 2025, 01:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Dec 29, 2025, 02:04 PM UTC

    Chameleon is not and was not not affected by the recently disclosed MongoDB vulnerability CVE-2025-14847 (aka. MongoBleed). It allows attackers to read arbitrary data from the database's heap memory. Chameleon's MongoDB instances are not publicly accessible and are also hosted with MongoDB Atlas which means they were patched before disclosure. We will, however, keep up to date on any developments from this incident

Read the full incident report →

Notice November 28, 2025

Chameleon not included in Mixpanel security incident

Detected by Pingoru
Nov 28, 2025, 12:30 AM UTC
Resolved
Nov 27, 2025, 05:00 PM UTC
Duration
Timeline · 1 update
  1. resolved Nov 28, 2025, 12:30 AM UTC

    Chameleon **was not part of** the security incident reported by Mixpanel today (https://mixpanel.com/blog/sms-security-incident/). We will, however, keep up to date on any developments from this incident

Read the full incident report →

Minor November 20, 2025

Elevated error rates when editing Chameleon experiences

Detected by Pingoru
Nov 20, 2025, 11:36 AM UTC
Resolved
Nov 20, 2025, 12:09 PM UTC
Duration
33m
Affected: Sidebar APIData API
Timeline · 3 updates
  1. identified Nov 20, 2025, 11:36 AM UTC

    We're seeing higher than normal error rates when editing within Chameleon. Our engineers have identified the cause and are working on a fix

  2. monitoring Nov 20, 2025, 11:51 AM UTC

    Error rates are back down to normal levels

  3. resolved Nov 20, 2025, 12:09 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice November 18, 2025

Update regarding active Cloudflare incident

Detected by Pingoru
Nov 18, 2025, 02:25 PM UTC
Resolved
Nov 18, 2025, 10:41 PM UTC
Duration
8h 16m
Affected: Dashboard
Timeline · 2 updates
  1. monitoring Nov 18, 2025, 02:25 PM UTC

    As of approximately 6:45 AM ET, Cloudflare reported an incident affecting many sites and vendors across the internet (Check https://www.cloudflarestatus.com/ for any direct updates). While Chameleon does not directly rely on Cloudflare, some services we depend on do. Consequently, you may experience the following: Copilot: OpenAI powers this feature and is currently impacted. Integrations: Data from integrations (Mixpanel, Amplitude, HubSpot, etc.) may be delayed until the incident is resolved. Recommendation: If your own product is experiencing downstream issues, we encourage you to use Chameleon to publish a downtime banner to alert your users. Please reach out if you need assistance setting this up.

  2. resolved Nov 18, 2025, 10:41 PM UTC

    According Cloudflare and others, this incident is resolved

Read the full incident report →

Major October 20, 2025

AWS outage information + Segments + Background jobs backlog

Detected by Pingoru
Oct 20, 2025, 01:48 PM UTC
Resolved
Oct 21, 2025, 02:13 AM UTC
Duration
12h 25m
Affected: Heroku
Timeline · 6 updates
  1. monitoring Oct 20, 2025, 01:48 PM UTC

    During the AWS outage, Chameleon remained online and was not directly affected by the ongoing issues. All Chameleon Experiences were published on schedule, and new experiences went live as expected. Many customers also used Chameleon to notify *their customers* via in-product banners linking to their own status pages. During this period, we ingested and queued a large volume of data — typical for EU and US Eastern morning hours. However, today our auto-scaling was unable to bring additional resources online due to the AWS and Heroku issues. As a result, we are currently processing a backlog of data and background jobs. The current processing delay is approximately 30 minutes (Experience metrics are delayed by this amount, but microsurvey responses are not). This backlog will decrease quickly once auto-scaling resumes normal operation.

  2. monitoring Oct 20, 2025, 01:48 PM UTC

    Updating to have a "Minor" impact

  3. monitoring Oct 20, 2025, 04:21 PM UTC

    Our current application / background servers are running as-is but our ability to scale our cluster is impacted. We will need additional resources provisioned within the next few hours to bring the backlog back into a manageable length. We will continue to monitor and implement any fixes that we can along the way and will plan to send another update within the next 2-3 hours

  4. monitoring Oct 20, 2025, 05:03 PM UTC

    Currently the Segment page (https://app.chameleon.io/segments) is only loading for a small percentage of requests due to upstream impact at Clickhouse => https://status.clickhouse.com

  5. monitoring Oct 20, 2025, 10:12 PM UTC

    According to AWS "AWS services which rely on EC2 instance launches such as [Heroku] are working through their backlog of EC2 instance launches successfully and we anticipate full recovery of the backlog over the next two hours" <= for Chameleon this means out data backlog should start processing more quickly automatically over the same time frame

  6. resolved Oct 21, 2025, 02:13 AM UTC

    The backlog of events has been processed and any new data coming in will be processed in near real time. TL;DR; Aside from the data backlog (peaked at 2 hours delay), and a ~10% error rate for loading Segments of users (in the Chameleon dashboard; no impact for your end-users), it was a relatively normal day at Chameleon in terms of the "rate of experiences delivered" for the baseline. Chameleon delivered approx. 200k downtime notices I hope today was not too stressful for you / your business and as always feel free to reach out with questions

Read the full incident report →

Notice July 28, 2025

Subprocessors notice

Detected by Pingoru
Jul 28, 2025, 08:41 PM UTC
Resolved
Jul 28, 2025, 08:41 PM UTC
Duration
Affected: Privacy notifications
Timeline · 1 update
  1. resolved Jul 28, 2025, 08:41 PM UTC

    Privacy update (not an incident) We’ve recently added a small number of trusted vendors to support key workflows across our platform, including: - Anthropic – AI functionality for workflow automations - Fathom – Call recording and transcription - Linear – Product issue and roadmap management - Synder – Financial system integrations - Mutiny – Website content personalization - Chili Piper – Meeting scheduling - Unify GTM – Go-to-market orchestration We’ve also streamlined our list by removing subprocessors no longer in use. These changes reflect our commitment to using modern, secure, and effective tools that help us improve our processes and deliver the best product and service to our customers. You can view the full, current list of subprocessors at our new subprocessors page: 👉 https://www.chameleon.io/security/subprocessors If you have any questions, feel free to reach out to us at [email protected]. Thanks, The Chameleon Team

Read the full incident report →

Minor June 25, 2025

Internal API instability

Detected by Pingoru
Jun 25, 2025, 06:59 PM UTC
Resolved
Jun 25, 2025, 09:29 PM UTC
Duration
2h 30m
Affected: Data API
Timeline · 2 updates
  1. identified Jun 25, 2025, 06:59 PM UTC

    We've identified instability in one of our internal APIs, which is causing intermittent 500 errors when editing and displaying Experiences. We've identified the root cause, and our team is actively working on stabilizing our services.

  2. resolved Jun 25, 2025, 09:29 PM UTC

    Solved: We've fixed the instability issues by scaling our service capacity.

Read the full incident report →