Is there an Chameleon outage?
Chameleon status: Systems Active
Last checked: 10 minutes ago
Get notified about any outages, downtime or incidents for Chameleon and 1800+ other cloud vendors. Monitor 10 companies, for free.
Last checked: 10 minutes ago
Get notified about any outages, downtime or incidents for Chameleon and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Chameleon.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Chameleon Builder | Active |
| Data API | Active |
| HelpBar Search API | Active |
| Heroku | Active |
| JavaScript CDN | Active |
| Privacy notifications | Active |
| Sidebar API | Active |
| Transactional emails | Active |
| User profile API | Active |
View the latest incidents for Chameleon and check for official updates:
Description: Heroku security incident information (https://status.heroku.com/incidents/2413). Chameleon uses Heroku for the hosting of our application servers. At this time we have performed the checks and recommended steps as outlined by Heroku, GitHub and our own internal policies. As a precaution we revoked tokens where appropriate and have no indication that any of our private repositories were accessed. Our ongoing operations are not impacted by this.
Status: Resolved
Impact: None | Started At: April 15, 2022, 10 p.m.
Description: Our postmortem is [here](https://drive.google.com/file/d/1Jwq-xbo-UGRoj33PSOXIoDcPIRkUTPls/view?usp=sharing) please reach out to us with any questions or comments.
Status: Postmortem
Impact: None | Started At: March 16, 2022, 8 p.m.
Description: Our postmortem is [here](https://drive.google.com/file/d/1Jwq-xbo-UGRoj33PSOXIoDcPIRkUTPls/view?usp=sharing) please reach out to us with any questions or comments.
Status: Postmortem
Impact: None | Started At: March 16, 2022, 8 p.m.
Description: A missing asset correctly fell back to a previous version of the asset, however the previous version became unavailable during this time. Once the issue was discovered we republished the original and will investigate why the failover script was not available.
Status: Resolved
Impact: None | Started At: Feb. 8, 2022, 6:30 a.m.
Description: This is a retrospective about an incident we discovered at 9:50am PT and immediately recovered from (the incident had started at 7:57am PT). A small subset of Tours with a specific legacy configuration [1] were displayed on pages that did not match the URL Rules. This resulted in Tours being erroneously displayed to users who would not have otherwise have seen the Tour. All other rules were correctly applied including Segmentation, Element matching etc. Upon learning of this issue we immediately rolled back the change and invalidated all relevant caches. We are following up with our customers directly to provide details about how this incident impacted their Tours and Users. Please feel free to reach out for more information. [1] We added support for multiple URL matching conditions (~11 months ago) and continued to support the legacy configuration of having only one URL match, when we deployed an update to how URL matching was handled the legacy configuration was omitted from the new code (and should not have been). Upon learning of this issue we immediately rolled back the change and invalidated all relevant caches.
Status: Resolved
Impact: Minor | Started At: Feb. 2, 2022, 3:30 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.
