Chameleon Outage History
8 incidents recorded over the last 365 days, 8 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Chameleon Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | Chameleon response to PHP CVE-2026-109618 and CVE-2026-109619Chameleon does not use PHP in our stack that supports Chameleon customers and end-users. Chameleon does use PHP in conjunction with Statamic CMS for our marketing site and we have upgraded to the patched PHP version… | -1172 min | Resolved |
| Sep 9, 2026 | Builder and Experience loading issuesWe identified a backed-up queue that caused some requests to our backend to be rejected (with a 500/503 error code) -- the impact was that during the time period from 6:10 eastern to 10am eastern only approximately 92%… | -135 min | Resolved |
| Mar 17, 2026 | OAuth authentication issuesOAuth authentication was not working for approximately 3pm est Sunday 2026-03-14 to 8:30 am est Tuesday 2026-03-16 | -47 min | Resolved |
| Mar 16, 2026 | Login issuesThis incident has been resolved. | 3h 9m | Resolved |
| Dec 29, 2025 | Chameleon not vulnerable to MongoBleed - CVE-2025-14847Chameleon 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… | 0 min | Resolved |
| Nov 28, 2025 | Chameleon not included in Mixpanel security incidentChameleon **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 | -450 min | Resolved |
| Nov 20, 2025 | Elevated error rates when editing Chameleon experiencesThis incident has been resolved. | 33 min | Resolved |
| Nov 18, 2025 | Update regarding active Cloudflare incidentAccording Cloudflare and others, this incident is resolved | 8h 16m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Chameleon incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Chameleon Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Chameleon acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Chameleon outage in this window ran 8h 16m, against a mean recovery of 2h 60m. If you depend on Chameleon in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.