Last checked: 4 minutes ago
Get notified about any outages, downtime or incidents for Bonsai and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Bonsai.
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 |
---|---|
Bonsai Dashboard | Active |
Bonsai Website | Active |
Private Clusters | Active |
Region Health: Bonsai Frankfurt | Active |
Region Health: Bonsai Ireland | Active |
Region Health: Bonsai North Virginia | Active |
Region Health: Bonsai Oregon | Active |
Region Health: Bonsai Singapore | Active |
Region Health: Bonsai Sydney | Active |
Region Health: Bonsai Tokyo | Active |
Region Health: Bonsai Virginia | Active |
View the latest incidents for Bonsai and check for official updates:
Description: Researchers recently discovered a sophisticated attempt to compromise XZ, a compression library that is widely used in Linux-based services across the world. It is suspected that if the compromise had been successful, state actors or other attackers would be able to remotely access many Linux-based machines on the Internet. Fortunately, the issue was discovered before the compromised version of the library made its way into mainline channels, so the impact is limited to versions 5.6.0 and 5.6.1. [CISA recommends](https://www.cisa.gov/news-events/alerts/2024/03/29/reported-supply-chain-compromise-affecting-xz-utils-data-compression-library-cve-2024-3094) users downgrade to XZ Utils 5.4.6 or earlier. Bonsai's system maintenance policy is to use up to date stable and LTS versions of software, and this policy means that none of our systems are impacted by the compromise. Out of an abundance of caution, we audited every online server in our fleet and verified that none of them is running the compromised versions of XZ Utils. Bonsai remains committed to the security and integrity of our systems and customers' data. Please direct any additional questions or concerns to support@bonsai.io.
Status: Resolved
Impact: None | Started At: April 1, 2024, 2 p.m.
Description: This incident has been resolved. Heroku users will need to resend their provisioning requests. Heroku will also remove failed provisioning requests after 24 hours, so users will have to resend their provisioning requests.
Status: Resolved
Impact: None | Started At: Feb. 24, 2023, 4 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 16, 2022, 8:15 p.m.
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 16, 2022, 4:55 p.m.
Description: At 05:30 UTC on 24 March 2022, Bonsai’s metrics database experienced node loss, which impacted metrics collection for a small percentage of clusters. Normally node loss is tolerable, and nodes are periodically replaced without incident. In this case, the node loss event affected replicated data as well. Affected users may see a gap in their metrics for the duration of the event. This event only affected metrics collection; customers’ Elasticsearch clusters were not impacted and continued to function normally.
Status: Resolved
Impact: None | Started At: March 24, 2022, 4:30 a.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.