Typesense incident

Cluster Provisioning and Configuration Change Issues

Minor Resolved View vendor source →

Typesense experienced a minor incident on August 29, 2024, lasting —. The incident has been resolved; the full update timeline is below.

Started
Aug 29, 2024, 09:34 AM UTC
Resolved
Aug 29, 2024, 09:34 AM UTC
Duration
—
Detected by Pingoru
Aug 29, 2024, 09:34 AM UTC

Update timeline

  1. resolved Aug 29, 2024, 09:34 AM UTC

    Type: Incident Duration: 1 hour and 55 minutes Affected Components: Ireland, Osaka, Oregon, Sao Paulo, Canada, Mumbai, Tokyo, London, N Virginia, Ohio, Stockholm, Milan, Singapore, Sydney, N California, Frankfurt, Seoul, Paris, Cape Town Aug 29, 09:34:00 GMT+0 - Investigating - We're investigating reports of issues with cluster provisioning in Typesense Cloud. Aug 29, 10:08:04 GMT+0 - Identified - We've tracked down the issue and have identified the root cause as originating from our upstream infrastructure provider's APIs being down. This is causing any provisioning of new nodes, both during new cluster provisioning and during configuration changes, to be affected. Existing clusters that are already provisioned and running are unaffected. We are closely monitoring the upstream issue and will post updates as a fix is being worked on. Aug 29, 11:29:23 GMT+0 - Resolved - The issue is now resolved. The upstream APIs are now back up and we've verified that new cluster provisioning and configuration changes now work.