OAuth authentication issues
Timeline · 1 update
- 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
Chameleon Outage History
Chameleon is up right nowChameleon had 16 outages in the last 2 years totaling 87h 48m of downtime — averaging 0.7 incidents per month.
There were 16 Chameleon outages since June 19, 2024 totaling 87h 48m of downtime. Each is summarised below — incident details, duration, and resolution information.
Login issues
Affected: Dashboard
Timeline · 3 updates
- 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
- 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**
- resolved Mar 16, 2026, 06:38 PM UTC
This incident has been resolved.
Chameleon not vulnerable to MongoBleed - CVE-2025-14847
Timeline · 1 update
- 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
Chameleon not included in Mixpanel security incident
Timeline · 1 update
- 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
Elevated error rates when editing Chameleon experiences
Affected: Sidebar APIData API
Timeline · 3 updates
- 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
- monitoring Nov 20, 2025, 11:51 AM UTC
Error rates are back down to normal levels
- resolved Nov 20, 2025, 12:09 PM UTC
This incident has been resolved.
Update regarding active Cloudflare incident
Affected: Dashboard
Timeline · 2 updates
- 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.
- resolved Nov 18, 2025, 10:41 PM UTC
According Cloudflare and others, this incident is resolved
AWS outage information + Segments + Background jobs backlog
Affected: Heroku
Timeline · 6 updates
- 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.
- monitoring Oct 20, 2025, 01:48 PM UTC
Updating to have a "Minor" impact
- 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
- 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
- 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
- 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
Subprocessors notice
Affected: Privacy notifications
Timeline · 1 update
- 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
Internal API instability
Affected: Data API
Timeline · 2 updates
- 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.
- resolved Jun 25, 2025, 09:29 PM UTC
Solved: We've fixed the instability issues by scaling our service capacity.
Chameleon availability
Affected: User profile APISidebar APIData APIHerokuHelpBar Search APIChameleon Builder
Timeline · 4 updates
- identified Jun 10, 2025, 12:57 PM UTC
We've identified an issue stemming from this Heroku incident https://status.heroku.com/incidents/2822 (upstream of Chameleon) which is causing us to have limited access to the heroku platform. We use Heroku for auto-scaling, console access, and deployment. This incident is currently affecting the availability of the Chameleon Dashboard, Builder, and our ability to run End-user Experiences (Tours, Launchers, Microsurveys).
- identified Jun 10, 2025, 01:44 PM UTC
The issue stems directly back to the Heroku outage (https://status.heroku.com/incidents/2822). Our current deployment of servers is running and handling the traffic to an acceptable level but we're unable to make any changes to the deployment, the number of servers (via autoscaling). We're seeing more total percentage of successful requests to Chameleon and that is also trending in the right direction. Will update again when we have new information
- identified Jun 10, 2025, 02:58 PM UTC
We continue to track the Heroku outage but continue to see intermittent issues with loading Chameleon Dashboard and generally connecting to Chameleon backend applications
- resolved Jun 11, 2025, 04:10 AM UTC
We've now seen consistent performance and response times from our Heroku instances for the past 3 hours and are making the incident as resolved. We will monitor the system as a whole now that everything is catching back up and the jobs/work to be done in the background queues. Thank you for your patience
Launcher Segmentation rules bypass
Timeline · 1 update
- resolved Apr 17, 2025, 03:21 PM UTC
At Apr 16, 2025 12:01pm UTC, Chameleon deployed a code update that caused some Launchers to be shown to users not Segmented to them. Chameleon added an event listener to check for changes to the URL rules, but in case of a new match, this listener accounted only for URL rules, and didn't check Segmentation. The change was rolled back when discovered, at Apr 16, 2025 7:07pm UTC.
Chameleon application errors / performance
Affected: User profile APIJavaScript CDNSidebar APIData APIChameleon Builder
Timeline · 5 updates
- identified Feb 27, 2025, 01:48 PM UTC
Chameleon continues to experience extremely high load and is taking steps to increase capacity above normal limits to address this. The current impact is that some requests to Chameleon are queued for a long time and/or timing out. In the UI this looks like page not loading, auto-saving not working, and for end-users experiences may not display. This currently appears to be happening for a < 10% of traffic but we'll continue to monitor as we work to resolve the issue
- monitoring Feb 27, 2025, 06:41 PM UTC
Our new capacity has been online for several hours now and is performing as expected. We will keep this incident open for another 24 hours in case of any new developments or issues. Thanks for out patience
- investigating Feb 28, 2025, 03:39 PM UTC
We are currently investigating slow downs and 503 errors on profile requests.
- monitoring Feb 28, 2025, 05:52 PM UTC
We are continuing to monitor system performance as response times and error rates have improved over the past hour. No new end-user-facing timeouts have been observed recently, but we are still actively investigating to ensure stability.
- resolved Feb 28, 2025, 07:55 PM UTC
This incident has been resolved, and all systems are operating as expected.
Profile Write Latency and Errors
Affected: User profile API
Timeline · 4 updates
- investigating Feb 21, 2025, 09:44 PM UTC
We are currently investigating the cause of intermittent slowness and timeouts resulting in occasional Application errors
- investigating Feb 21, 2025, 09:47 PM UTC
We are continuing to investigate this issue.
- monitoring Feb 21, 2025, 11:00 PM UTC
We have identified the following issues: 1) Experiences sometimes not being delivered to end-users. 2) Experiences sometimes not being able to be opened/edited in Chameleon Builder. We're actively monitoring and investigating the root cause.
- resolved Feb 22, 2025, 02:27 AM UTC
This incident has been resolved and systems are back to normal.
Data collection and log in issues
Affected: User profile API
Timeline · 3 updates
- investigating Aug 01, 2024, 06:49 PM UTC
We are currently investigating issues with data collection and log in.
- monitoring Aug 01, 2024, 07:57 PM UTC
We've addressed the data collection and log in issues customers were experiencing. We are still monitoring this issue while we understand the root cause.
- resolved Aug 02, 2024, 03:27 AM UTC
This incident is resolved (as of 4:30pm pacific). The main impact was that certain API actions were resulting in errors. These errors were most obvious for calls to track events where the result of the API call was a 500 error. In addition, some data was delayed in reaching the intended user because of delays in processing the incoming data. An incident like this will have an investigation followed by implementing the recommended updates. As always, you may reach out to us for further information, if needed.
Data ingestion delays
Affected: Data API
Timeline · 2 updates
- identified Jul 19, 2024, 03:15 PM UTC
Some data ingestion is experiencing higher than normal latency in being added to Chameleon's analytics charts and aggregate totals. The queues are on track to catch back up soon
- resolved Jul 19, 2024, 04:30 PM UTC
This incident has been resolved.
Chameleon dashboard slowness
Affected: User profile APIData API
Timeline · 3 updates
- investigating Jun 19, 2024, 07:59 PM UTC
We're investigating a slowdown of the Chameleon dashboard @ https://app.chameleon.io
- identified Jun 19, 2024, 08:36 PM UTC
We are still working on this issue. At this time we're seeing some upstream slowness that is impacting our latency to the database and are working on a resolution
- resolved Jun 19, 2024, 08:58 PM UTC
We're back to full speed and consider this incident closed. We will post more updates if we see any further dip in our metrics