Last checked: 56 seconds 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: The latest Chameleon update has been deployed successfully, and this has resolved the errors that some Chameleon customers were seeing while creating a new Tour. We're monitoring the deployment and our team will be reviewing our deployment process to pinpoint the fault of this failed deployment. Thank you for your patience as we worked to resolve this issue.
Status: Resolved
Impact: None | Started At: Oct. 12, 2020, 11:33 a.m.
Description: The root cause of this incident was a database failover into a node that was performing a background index build -- the index on the previous master had completed in 'off hours' with not noticeable impact to query performance however when the index build had to keep up with peak load it could not quite cover the load. The result was a throttling effect on each connection causing requests that typically take 35ms to take around 5s-12s with some more intensive requests taking longer. After identifying the issue our engineers were able to shed load into a properly throttled background queue to drop the overall load. End-users may have seen console errors relating to failed network requests or simply a slowdown in network activity to Chameleon.
Status: Resolved
Impact: None | Started At: Oct. 6, 2020, 8:28 p.m.
Description: The root cause of this incident was a database failover into a node that was performing a background index build -- the index on the previous master had completed in 'off hours' with not noticeable impact to query performance however when the index build had to keep up with peak load it could not quite cover the load. The result was a throttling effect on each connection causing requests that typically take 35ms to take around 5s-12s with some more intensive requests taking longer. After identifying the issue our engineers were able to shed load into a properly throttled background queue to drop the overall load. End-users may have seen console errors relating to failed network requests or simply a slowdown in network activity to Chameleon.
Status: Resolved
Impact: None | Started At: Oct. 6, 2020, 8:28 p.m.
Description: The performance of the pages referenced here has been restored
Status: Resolved
Impact: None | Started At: Aug. 24, 2020, 9:29 p.m.
Description: The performance of the pages referenced here has been restored
Status: Resolved
Impact: None | Started At: Aug. 24, 2020, 9:29 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.