We have rolled out updated Elasticsearch builds that are stable. We are closely monitoring their continued performance.

This issue was resolved.

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 support@bonsai.io for individual assistance.