Mar <var data-var='date'>17</var>, <var data-var='time'>08:00</var> EDT Resolved - OAuth authentication was not working for approximately 3pm est Sunday 2026-03-14 to 8:30 am est Tuesday 2026-03-16

OAuth authentication issues

Mar <var data-var='date'>16</var>, <var data-var='time'>14:38</var> EDT Resolved - This incident has been resolved.Mar <var data-var='date'>16</var>, <var data-var='time'>11:53</var> EDT Identified - 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**Mar <var data-var='date'>16</var>, <var data-var='time'>11:29</var> EDT Investigating - We're looking into an issue where new magic links / OAuth / SSO are not working as expected

Login issues

Dec <var data-var='date'>29</var>, <var data-var='time'>08:00</var> EST Resolved - 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 vulnerable to MongoBleed - CVE-2025-14847

Nov <var data-var='date'>27</var>, <var data-var='time'>12:00</var> EST Resolved - 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

Chameleon not included in Mixpanel security incident

Nov <var data-var='date'>20</var>, <var data-var='time'>07:09</var> EST Resolved - This incident has been resolved.Nov <var data-var='date'>20</var>, <var data-var='time'>06:51</var> EST Monitoring - Error rates are back down to normal levelsNov <var data-var='date'>20</var>, <var data-var='time'>06:36</var> EST Identified - We're seeing higher than normal error rates when editing within Chameleon. Our engineers have identified the cause and are working on a fix

Elevated error rates when editing Chameleon experiences

Nov <var data-var='date'>18</var>, <var data-var='time'>17:41</var> EST Resolved - According Cloudflare and others, this incident is resolvedNov <var data-var='date'>18</var>, <var data-var='time'>09:25</var> EST Monitoring - 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.

Update regarding active Cloudflare incident

Oct <var data-var='date'>20</var>, <var data-var='time'>22:13</var> EDT Resolved - 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 questionsOct <var data-var='date'>20</var>, <var data-var='time'>18:12</var> EDT Update - 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 frameOct <var data-var='date'>20</var>, <var data-var='time'>13:03</var> EDT Update - 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.comOct <var data-var='date'>20</var>, <var data-var='time'>12:21</var> EDT Update - 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 hoursOct <var data-var='date'>20</var>, <var data-var='time'>09:48</var> EDT Update - Updating to have a "Minor" impactOct <var data-var='date'>20</var>, <var data-var='time'>09:48</var> EDT Monitoring - 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.

AWS outage information + Segments + Background jobs backlog

Jul <var data-var='date'>28</var>, <var data-var='time'>16:41</var> EDT Resolved - 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 security@chameleon.io. Thanks, The Chameleon Team

Subprocessors notice

Jun <var data-var='date'>25</var>, <var data-var='time'>17:29</var> EDT Resolved - Solved: We've fixed the instability issues by scaling our service capacity.Jun <var data-var='date'>25</var>, <var data-var='time'>14:59</var> EDT Identified - 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.

Internal API instability

Jun <var data-var='date'>11</var>, <var data-var='time'>00:10</var> EDT Resolved - 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 patienceJun <var data-var='date'>10</var>, <var data-var='time'>10:58</var> EDT Update - We continue to track the Heroku outage but continue to see intermittent issues with loading Chameleon Dashboard and generally connecting to Chameleon backend applicationsJun <var data-var='date'>10</var>, <var data-var='time'>09:44</var> EDT Update - 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 informationJun <var data-var='date'>10</var>, <var data-var='time'>08:57</var> EDT Identified - 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).

Chameleon availability

Apr <var data-var='date'>17</var>, <var data-var='time'>11:21</var> EDT Resolved - 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.

Launcher Segmentation rules bypass

Feb <var data-var='date'>28</var>, <var data-var='time'>14:55</var> EST Resolved - This incident has been resolved, and all systems are operating as expected.Feb <var data-var='date'>28</var>, <var data-var='time'>12:52</var> EST Monitoring - 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.Feb <var data-var='date'>28</var>, <var data-var='time'>10:39</var> EST Investigating - We are currently investigating slow downs and 503 errors on profile requests.Feb <var data-var='date'>27</var>, <var data-var='time'>13:41</var> EST Monitoring - 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 patienceFeb <var data-var='date'>27</var>, <var data-var='time'>08:48</var> EST Identified - 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

Chameleon application errors / performance

Feb <var data-var='date'>21</var>, <var data-var='time'>21:27</var> EST Resolved - This incident has been resolved and systems are back to normal.Feb <var data-var='date'>21</var>, <var data-var='time'>18:00</var> EST Monitoring - 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.Feb <var data-var='date'>21</var>, <var data-var='time'>16:47</var> EST Update - We are continuing to investigate this issue.Feb <var data-var='date'>21</var>, <var data-var='time'>16:44</var> EST Investigating - We are currently investigating the cause of intermittent slowness and timeouts resulting in occasional Application errors

Profile Write Latency and Errors

Feb <var data-var='date'>10</var>, <var data-var='time'>19:00</var> EST Resolved - This incident was kept open for monitoring and has been resolved.Feb <var data-var='date'>10</var>, <var data-var='time'>17:00</var> EST Investigating - We are currently investigating the cause of intermittent slowness and timeouts resulting in occasional Application errors

Feb <var data-var='date'> 3</var>, <var data-var='time'>09:44</var> EST Resolved - This incident has been resolved.Feb <var data-var='date'> 3</var>, <var data-var='time'>06:57</var> EST Monitoring - Response times and error rates are returning to normal and will continue to monitor. At this time, we know that a large increase in latency when writing to the database caused the latency of essentially all other operations to increase. We will leave this incident open until we're sure that the changes have a chance to full stabilize, the background jobs have processed, and the workload returns to normal levels/latencies.Feb <var data-var='date'> 3</var>, <var data-var='time'>06:13</var> EST Identified - We are seeing elevated error rates, and various systems being slow or not loading. At the moment this includes the Chameleon dashboard, identifying users, and sending data to Chameleon. We know this is related to the performance of our primary database and will have an update again shortly.

Jan <var data-var='date'>31</var>, <var data-var='time'>20:13</var> EST Resolved - This incident is over but will remain open while the final data is processedJan <var data-var='date'>31</var>, <var data-var='time'>17:41</var> EST Update - This incident is has now been partially resolved, some data ingestion delay will be processed over the next few hours as more capacity is brought online to assist in working through a backlog of events and updates from integrationsJan <var data-var='date'>31</var>, <var data-var='time'>17:01</var> EST Update - We're still actively monitoring this incident and will report any new information we haveJan <var data-var='date'>31</var>, <var data-var='time'>13:34</var> EST Monitoring - This incident is still ongoing, we will have more updates within the hour. The main impact is that requests that typically take 30-50ms are varying from 30ms to 3s, with some timing out and never completing, this is causing some Chameleon experiences to not start when they otherwise wouldJan <var data-var='date'>31</var>, <var data-var='time'>09:28</var> EST Investigating - Intermittent slowness and timeouts resulting in occasional Application errors

Jan <var data-var='date'>30</var>, <var data-var='time'>22:11</var> EST Resolved - This incident is resolvedJan <var data-var='date'>30</var>, <var data-var='time'>16:36</var> EST Investigating - We are currently investigating the cause of intermittent slowness and timeouts resulting in occasional Application errors

Aug <var data-var='date'> 1</var>, <var data-var='time'>23:27</var> EDT Resolved - 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.Aug <var data-var='date'> 1</var>, <var data-var='time'>15:57</var> EDT Monitoring - 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.Aug <var data-var='date'> 1</var>, <var data-var='time'>14:49</var> EDT Investigating - We are currently investigating issues with data collection and log in.

Data collection and log in issues

Jul <var data-var='date'>19</var>, <var data-var='time'>12:30</var> EDT Resolved - This incident has been resolved.Jul <var data-var='date'>19</var>, <var data-var='time'>11:15</var> EDT Identified - 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

Data ingestion delays

Jul <var data-var='date'>15</var>, <var data-var='time'>15:40</var> EDT Resolved - Chameleon's iFrame-support Beta has now completed its testing and release onto Chameleon's production version. This version now provides support for Chameleon Tours, Surveys, Tooltips, HelpBar experiences. If you have any questions about Chameleon's iframe support, please reach out to our Support team.Feb <var data-var='date'>13</var>, <var data-var='time'>10:38</var> EST Monitoring - There is now a beta version of Chameleon iFrame support available. This beta allows for Chameleon Tours and experiences to appear across iframes with different domains (both subdomains and primary domains). Please message Chameleon Support to request to be included in this beta.Oct <var data-var='date'>18</var>, <var data-var='time'>13:36</var> EDT Identified - Impact: If your use of Chameleon depends on selecting page elements that reside within iframes, those specific Chameleon Experiences may not not be running correctly. Working: Main page is app.acme.com and the iframe is app.acme.com Not working: Main page is app.acme.com and the iframe is content.acme.com Further context is that prior to Chrome 115, iframes on the same origin (e.g. app.acme.com and content.acme.com) allowed their content is be accessible to the parent page. Chameleon uses this same-origin access pattern to find and attach Chameleon Experiences to the element found within an iframe. However, starting in Chrome 115, Google removed support for modifying a property called `document.domain` which permits this behavior. Now, because Google has disabled this feature, Chameleon cannot currently directly access content of iframes with subdomains that differ from the parent page. The Chameleon team is working quickly to restore full support for same-origin iframes. We plan to ship an early version of this to impacted customers in the coming days. If you are using iframes in the way described above, please reach out to your account manager or hello@chameleon.io let us know. Also indicate if you want to be added to the iframe feature preview when it's ready. Workaround: In the meantime, the workaround is to match the domain of the content inside an iframe with the content outside of the iframe (referenced as "Working:" above). Some teams we're in contact with have had success in simply proxying their iframed content through the same domain as their main page (let us know if you want more information on how to do this).

Chameleon support for iframes using a different subdomain than parent page

Jun <var data-var='date'>19</var>, <var data-var='time'>16:58</var> EDT Resolved - We're back to full speed and consider this incident closed. We will post more updates if we see any further dip in our metricsJun <var data-var='date'>19</var>, <var data-var='time'>16:36</var> EDT Identified - 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 resolutionJun <var data-var='date'>19</var>, <var data-var='time'>15:59</var> EDT Investigating - We're investigating a slowdown of the Chameleon dashboard @ https://app.chameleon.io

Chameleon dashboard slowness

Mar <var data-var='date'> 7</var>, <var data-var='time'>14:00</var> EST Resolved - Some Microsurvey summaries from the previous 7 days were delayed and but will be re-run and delivered over the next few hours

Microsurvey summaries delayed

Feb <var data-var='date'> 9</var>, <var data-var='time'>15:00</var> EST Resolved - On Feb 9th, Chameleon determined that a small percentage of some customers' end-user were not able to dismiss a specific type of Chameleon Experience (a Tour or a Microsurvey) due to an issue the application of the Experiences' Snooze settings from a Snooze that first happened prior to Jan 30th. We quickly fixed the issue and migrated the relevant data to bring your users back to the expected state. If your users were impacted by this, you will receive an email from our customer success team with more details.

Snooze settings incident

Feb <var data-var='date'> 7</var>, <var data-var='time'>13:39</var> EST Resolved - We're going to close this incident as Chameleon has now been operating at full capacity for the last 12 hours. If you have any questions about this or anything else Chameleon-related please reach out to Chameleon support.Feb <var data-var='date'> 6</var>, <var data-var='time'>20:28</var> EST Monitoring - We have increased the network capacity of our Redis cluster and we're in contact with the Heroku Redis team about the latency issues we're still intermittently experiencing. At this time, we're going to consider this incident closed but will continue to monitor until more time has passed without latency issuesFeb <var data-var='date'> 6</var>, <var data-var='time'>13:21</var> EST Investigating - This is a repeat of the previous incident (https://status.chameleon.io/incidents/x12r73srmcg2). Please check back for updates as we will update when we have more information on when all of Chameleon's services are back up and running. Customers may experience issues opening Chameleon's Builder in their applications, exporting reports, or loading certain Chameleon Dashboard pages.

Redis instance connection timeouts (2)

Feb <var data-var='date'> 6</var>, <var data-var='time'>12:32</var> EST Resolved - This incident has been resolved. The analytics data received for the time between Feb 6th, 15:31 UTC and Feb 6th, 16:28 UTC were not processed in real time. Our team in the process of re-running any data received during this time frame including experience analytics. Additionally many background jobs during this will also be re-run including data exports. If you do not receive your data export by the end of the day today please re-export the data or reach out to supportFeb <var data-var='date'> 6</var>, <var data-var='time'>11:07</var> EST Monitoring - Our main redis instance had a failover to its secondary and is catching back up with traffic. This redis instance handles background processing and will take some time to catch back up with realtime. Customers may experience issues opening Chameleon's Builder in their applications, exporting reports, or loading certain Chameleon Dashboard pages.Feb <var data-var='date'> 6</var>, <var data-var='time'>10:43</var> EST Investigating - We are currently investigating this issue.

Is Chameleon down?

Chameleon status is UP

Lastest published events

OAuth authentication issues

Login issues

Chameleon not vulnerable to MongoBleed - CVE-2025-14847

Chameleon Services, Components and Regions

Recent Chameleon events

OAuth authentication issues

Login issues

Chameleon not vulnerable to MongoBleed - CVE-2025-14847

Chameleon not included in Mixpanel security incident

Elevated error rates when editing Chameleon experiences

Update regarding active Cloudflare incident

Get your FREE account now,
5 monitors included!

Is Chameleon down?

Chameleon status is UP

Lastest published events

OAuth authentication issues

Login issues

Chameleon not vulnerable to MongoBleed - CVE-2025-14847

Chameleon Services, Components and Regions

Recent Chameleon events

OAuth authentication issues

Login issues

Chameleon not vulnerable to MongoBleed - CVE-2025-14847

Chameleon not included in Mixpanel security incident

Elevated error rates when editing Chameleon experiences

Update regarding active Cloudflare incident

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!