Bonsai outages and incidents
Outage and incident data over the last 30 days for Bonsai.
There have been 0 outages or incidents for Bonsai in the last 30 days.
Severity Breakdown:
Tired of searching for status updates?
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 NowComponents and Services Monitored for Bonsai
Outlogger 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 |
Latest Bonsai outages and incidents.
View the latest incidents for Bonsai and check for official updates:
Bonsai Unaffected By XZ Compromise
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 [email protected].
Status: Resolved
Impact: None | Started At: April 1, 2024, 2 p.m.
Updates:
-
Time: April 3, 2024, 6:41 p.m.Status: ResolvedUpdate: 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 [email protected].
Heroku Bonsai Elasticsearch add-on users experiencing provisioning failures
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.
Updates:
-
Time: Feb. 24, 2023, 6:35 p.m.Status: ResolvedUpdate: 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.
-
Time: Feb. 24, 2023, 6:16 p.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: Feb. 24, 2023, 6:15 p.m.Status: IdentifiedUpdate: The issue has been identified and a fix is being implemented.
-
Time: Feb. 24, 2023, 6:14 p.m.Status: InvestigatingUpdate: We are currently investigating this issue.
Interruption to Metrics service
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 16, 2022, 8:15 p.m.
Updates:
-
Time: June 17, 2022, 3:38 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: June 17, 2022, 1:34 a.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: June 16, 2022, 8:36 p.m.Status: IdentifiedUpdate: The issue has been identified and a fix is being implemented.
-
Time: June 16, 2022, 8:22 p.m.Status: InvestigatingUpdate: We are investigating interruptions to the Metrics service. This does not affect Elasticsearch, but may temporarily impact metrics collection for users.
Interruption in Grafana reporting
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: June 16, 2022, 4:55 p.m.
Updates:
-
Time: June 17, 2022, 3:35 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: June 17, 2022, 1:40 a.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: June 16, 2022, 5:30 p.m.Status: IdentifiedUpdate: The issue has been identified and our team is working to restore the Grafana dashboards.
-
Time: June 16, 2022, 5:28 p.m.Status: InvestigatingUpdate: The metrics database used by Grafana is currently experiencing an interruption. Elasticsearch clusters are operating normally. View an alternate source of metrics data on the "Metrics" tab in your Bonsai dashboard: https://docs.bonsai.io/article/328-metrics.
Missing Cluster Metrics
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.
Updates:
-
Time: March 28, 2022, 9:51 p.m.Status: ResolvedUpdate: 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.
