Bonsai Elasticsearch Outage History

Bonsai Elasticsearch is up right now

Pingoru has recorded 7 incidents for Bonsai Elasticsearch: 6 in the last 12 months and 1 in the last 90 days.

Source: status.bonsai.io

7incidents recorded
6last 12 months
1last 90 days
8 hourstypical duration
Incidents per month
024AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct4%
Pingoru began tracking Bonsai Elasticsearch in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 2026327 of 720 (4%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 2026120 of 576 (4%)

Incidents, newest first

Minor October 21, 2026 eMudhra Intermediate CA Compromise 20h 13m One More Cloud service

Started Oct 21, 2026, 01:12 AM UTC· resolved Oct 21, 2026, 09:25 PM UTC

  1. investigating Oct 21, 2026, 01:13 AM UTC

    We are aware of the recently published findings of compromised intermediate CA certificates and we are working to evaluate any impact to Bonsai services. We will post updates here as we clear all of our hosted and managed services.

  2. investigating Oct 21, 2026, 01:51 AM UTC

    We have uncovered no critical customer impact as of this time and our investigation continues.

  3. investigating Oct 21, 2026, 02:21 AM UTC

    We have uncovered no critical customer impact as of this time and our investigation continues.

  4. monitoring Oct 21, 2026, 02:58 AM UTC

    After discovering no customer impact or direct route to exploit this situation, we are starting a series of remediations off the critical path for security hygiene. We are shifting this incident to monitoring and will update with any further findings.

  5. resolved Oct 21, 2026, 09:25 PM UTC

    We consider this issue closed. Please see our blog post for more details: https://bonsai.io/blog/emudhra-ca-compromise-customer-notice/

  6. resolved Oct 21, 2026, 09:25 PM UTC

    We consider this issue closed. Please see our blog post for more details: https://bonsai.io/blog/emudhra-ca-compromise-customer-notice/

Read the full incident report →

Minor June 29, 2026 Isolated Cluster Availability Issues 23h 55m One More Cloud service

Started Jun 29, 2026, 11:04 PM UTC· resolved Jun 30, 2026, 11:00 PM UTC

  1. resolved Jun 30, 2026, 11:00 PM UTC

    This issue was resolved on June 30 and left open in error. Impacted: Hosted Search Clusters: AWS

  2. resolved Jul 30, 2026, 07:08 PM UTC

    This issue was resolved on June 30 and left open in error. Impacted: Hosted Search Clusters: AWS

Read the full incident report →

Minor June 24, 2026 Bonsai app experiencing timeouts and slow responses 22m One More Cloud service

Started Jun 24, 2026, 10:58 PM UTC· resolved Jun 24, 2026, 11:21 PM UTC

  1. resolved Jun 24, 2026, 11:21 PM UTC

    This issue was resolved.

  2. resolved Jun 25, 2026, 11:21 PM UTC

    This issue was resolved.

Read the full incident report →

Major June 23, 2026 Search connection outage 2h 33m One More Cloud service

Started Jun 23, 2026, 06:35 PM UTC· resolved Jun 23, 2026, 09:08 PM UTC

  1. resolved Jun 23, 2026, 09:08 PM UTC

    The underlying incident has been resolved. Some small number of clusters still experiencing 502 errors due to cached or otherwise incorrect DNS resolution, and should either refresh their DNS caches or replace "bonsaisearch.net" in their cluster URL with the fallback of "bonsai.io". For example, "oak-123.us-east-1.bonsaisearch.net" becomes "oak-123.us-east-1.bonsai.io". Anyone experiencing lingering errors is encourage to reach out to [email protected] for individual assistance.

  2. resolved Jun 24, 2026, 07:37 PM UTC

    The underlying incident has been resolved. Some small number of clusters still experiencing 502 errors due to cached or otherwise incorrect DNS resolution, and should either refresh their DNS caches or replace "bonsaisearch.net" in their cluster URL with the fallback of "bonsai.io". For example, "oak-123.us-east-1.bonsaisearch.net" becomes "oak-123.us-east-1.bonsai.io". Anyone experiencing lingering errors is encourage to reach out to [email protected] for individual assistance.

Read the full incident report →

Minor March 24, 2026 Bonsai Dashboard Temporarily Unavailable –

Started Mar 24, 2026, 05:29 PM UTC· resolved Mar 24, 2026, 05:29 PM UTC

  1. resolved Mar 24, 2026, 05:43 PM UTC

    We had a temporary outage affecting our dashboard application. No search clusters or services were affected.

Read the full incident report →

Minor February 4, 2026 Interruption in New Business & Enterprise Cluster Provisioning 1h 37m

Started Feb 04, 2026, 04:48 PM UTC· resolved Feb 04, 2026, 06:25 PM UTC

  1. resolved Feb 04, 2026, 05:41 PM UTC

    New Business & Enterprise-tier cluster provisioning were briefly interrupted during an API outage that affected all regions for about 32 minutes.

Read the full incident report →

Notice October 20, 2025 AWS us-east-1 issues 7h 26m Bonsai Dashboard

Started Oct 20, 2025, 02:39 PM UTC· resolved Oct 20, 2025, 10:06 PM UTC

  1. identified Oct 20, 2025, 02:39 PM UTC

    AWS us-east-1 is having EC2, network & control plane issues that have affected the Bonsai Dashboard. As far as we are able to evaluate, all Bonsai search services are still operating without interruption given our multi-AZ redundancy.

  2. identified Oct 20, 2025, 02:39 PM UTC

    We are continuing to work on a fix for this issue.

  3. identified Oct 20, 2025, 02:40 PM UTC

    We are continuing to work on a fix for this issue.

  4. monitoring Oct 20, 2025, 02:46 PM UTC

    We have mitigated the availability of the Bonsai Dashboard and will continue monitoring the situation.

  5. monitoring Oct 20, 2025, 05:05 PM UTC

    We are experiencing delays in single-tenant cluster provisioning & deprovisioning while AWS is having issues today. We expect this to resolve within a few hours.

  6. monitoring Oct 20, 2025, 05:58 PM UTC

    Immediate impacts to Bonsai’s service have been mitigated and all services are functioning normally. We will continue to monitor the progress of the upstream outage at AWS which may affect newly provisioned clusters in the us-east-1 region.

  7. resolved Oct 20, 2025, 10:06 PM UTC

    We are considering this incident resolved. Please write [email protected] if you see any lingering issues.

Read the full incident report →