Resolved after 2 hours 33 minutes, affecting One More Cloud service, on June 23, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
Your product runs on more than Bonsai Elasticsearch
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services