Booqable experienced a major incident on June 13, 2024 affecting DNS, lasting 7d 20h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jun 13, 2024, 11:12 AM UTC
Our NS records are not resolving which are in control of our domain registrar. We are working with them to resolve the issue as fast as possible.
- identified Jun 13, 2024, 11:13 AM UTC
We are continuing to work on a fix for this issue.
- identified Jun 13, 2024, 03:44 PM UTC
We are implementing a temporary patch to fix embedded stores and stores on root domains.
- monitoring Jun 13, 2024, 05:06 PM UTC
We see most stores coming online now. If you need your store to come online faster and you are using a CNAME record, point it to `custom.booqable.store` instead of `custom.booqable.shop`.
- monitoring Jun 14, 2024, 08:28 AM UTC
All embedded stores and those configured with an A record are now back online. However, stores using a custom domain with a CNAME record remain offline due to issues with the `booqable.shop` domain. After thorough consideration, we have decided to sunset the `booqable.shop` domain and transition all customers with a CNAME record to our `booqable.store` domain. To update your setup, please log in to your domain name provider and change your CNAME record to `custom.booqable.store` instead of `custom.booqable.shop`. Note that it may take some time for it to be fully effective, depending on your provider.
- monitoring Jun 20, 2024, 08:54 AM UTC
The new `booqable.store` domain is now affected by the same problem. We are working with our domain registrar to resolve this as fast as possible.
- resolved Jun 21, 2024, 08:00 AM UTC
Both `booqable.shop` and `booqable.store` are resolving again. The issue has been resolved.