Booqable Outage History

Booqable is up right now

Booqable had 14 outages in the last 2 years totaling 299h 0m of downtime — averaging 0.6 incidents per month.

There were 14 Booqable outages since June 13, 2024 totaling 299h 0m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.booqable.com

Major November 18, 2025

Partial service outage — underlying infrastructure issue

Detected by Pingoru
Nov 18, 2025, 11:55 AM UTC
Resolved
Nov 18, 2025, 05:56 PM UTC
Duration
6h 1m
Affected: Web application
Timeline · 4 updates
  1. investigating Nov 18, 2025, 11:55 AM UTC

    We’re currently experiencing service disruptions caused by a Cloudflare outage. This may affect access to Booqable for some customers, particularly in certain regions. Our team is monitoring the situation and will update this page as soon as we know more. Your data is safe.

  2. investigating Nov 18, 2025, 11:57 AM UTC

    Cloudflare has acknowledge issues in their global network are investigating them. You can follow the Cloudflare status at: https://www.cloudflarestatus.com/

  3. monitoring Nov 18, 2025, 03:29 PM UTC

    A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal.

  4. resolved Nov 18, 2025, 05:56 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical October 20, 2025

Main Booqable Application Unavailable Due to Heroku Outage

Detected by Pingoru
Oct 20, 2025, 04:17 PM UTC
Resolved
Oct 21, 2025, 02:21 PM UTC
Duration
22h 4m
Affected: Web application
Timeline · 3 updates
  1. identified Oct 20, 2025, 02:59 PM UTC

    The main Booqable application is currently unavailable due to a widespread outage affecting our main hosting provider — Heroku. We’re monitoring Heroku’s status closely and will restore full access as soon as their services are back online.

  2. monitoring Oct 20, 2025, 07:17 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Oct 21, 2025, 02:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Major October 20, 2025

Partial Domain Resolution Disruption Due to AWS Outage

Detected by Pingoru
Oct 20, 2025, 02:03 PM UTC
Resolved
Oct 21, 2025, 02:21 PM UTC
Duration
1d
Affected: DNS
Timeline · 4 updates
  1. identified Oct 20, 2025, 02:03 PM UTC

    We are currently experiencing issues with domain resolution due to an AWS outage. While our application itself continues to operate normally, online stores using custom domains may be temporarily unavailable. We’re monitoring the situation closely and will provide updates as soon as the issue is resolved.

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

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

  3. monitoring Oct 20, 2025, 07:16 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Oct 21, 2025, 02:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor July 14, 2025

Degraded Performance

Detected by Pingoru
Jul 14, 2025, 12:58 PM UTC
Resolved
Jul 14, 2025, 03:14 PM UTC
Duration
2h 16m
Affected: Web application
Timeline · 2 updates
  1. investigating Jul 14, 2025, 12:58 PM UTC

    We are currently investigating degraded performance affecting the web platform.

  2. resolved Jul 14, 2025, 03:14 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 1, 2025

Email delivery disruption

Detected by Pingoru
Jul 01, 2025, 12:16 PM UTC
Resolved
Jul 01, 2025, 04:30 PM UTC
Duration
4h 14m
Affected: Email delivery
Timeline · 2 updates
  1. identified Jul 01, 2025, 12:16 PM UTC

    We are currently experiencing an issue that is preventing emails from being sent from our application. Our team has identified the root cause and is actively working on implementing a fix. We will provide updates as progress is made. Thank you for your patience.

  2. resolved Jul 01, 2025, 04:30 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor April 24, 2025

Performance Degradation

Detected by Pingoru
Apr 24, 2025, 02:55 PM UTC
Resolved
Apr 24, 2025, 03:13 PM UTC
Duration
18m
Affected: Web application
Timeline · 3 updates
  1. investigating Apr 24, 2025, 02:55 PM UTC

    We're currently investigating an issue causing slower than normal performance. Our team is working to identify and resolve the root cause. Thank you for your patience.

  2. monitoring Apr 24, 2025, 03:09 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 24, 2025, 03:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 18, 2025

Document Download Issues

Detected by Pingoru
Apr 18, 2025, 08:08 AM UTC
Resolved
Apr 18, 2025, 11:27 AM UTC
Duration
3h 18m
Affected: Web application
Timeline · 4 updates
  1. investigating Apr 18, 2025, 08:08 AM UTC

    We are currently investigating an issue affecting document downloads on our platform. Some users may experience failures or delays when attempting to download documents. All other core services remain operational. Our engineering team is actively working to identify the root cause and implement a fix as soon as possible. We appreciate your patience and apologize for the inconvenience.

  2. identified Apr 18, 2025, 08:55 AM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 18, 2025, 10:46 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 18, 2025, 11:27 AM UTC

    This incident has been resolved.

Read the full incident report →

Major February 4, 2025

Embeddable components not loading

Detected by Pingoru
Feb 04, 2025, 02:41 PM UTC
Resolved
Feb 05, 2025, 08:57 AM UTC
Duration
18h 16m
Timeline · 3 updates
  1. identified Feb 04, 2025, 02:41 PM UTC

    We are currently experiencing an issue where Booqable embeddable components are not loading properly due to a recent library update. Our team has identified the root cause and is actively working on a fix. We appreciate your patience and will provide further updates as we make progress. Thank you for your understanding.

  2. monitoring Feb 04, 2025, 04:21 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Feb 05, 2025, 08:57 AM UTC

    This incident has been resolved.

Read the full incident report →

Major January 7, 2025

Missing items in Inventory

Detected by Pingoru
Jan 07, 2025, 06:47 PM UTC
Resolved
Jan 07, 2025, 08:59 PM UTC
Duration
2h 11m
Affected: Search engine
Timeline · 4 updates
  1. investigating Jan 07, 2025, 06:47 PM UTC

    We are currently experiencing an issue in our application related to Elasticsearch, which is affecting the ability to search and find items in the inventory.

  2. identified Jan 07, 2025, 06:47 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jan 07, 2025, 07:49 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Jan 07, 2025, 08:59 PM UTC

    This incident has been resolved.

Read the full incident report →

Major December 2, 2024

Missing orders

Detected by Pingoru
Dec 02, 2024, 03:10 PM UTC
Resolved
Dec 02, 2024, 03:26 PM UTC
Duration
15m
Affected: Web application
Timeline · 3 updates
  1. investigating Dec 02, 2024, 03:10 PM UTC

    We are actively investigating an issue causing orders to not display as expected. Please rest assured that our database is fully operational, and no data has been lost. Thank you for your patience as we work to resolve this matter promptly.

  2. monitoring Dec 02, 2024, 03:13 PM UTC

    We identified an issue related to a recent library update. The changes have been rolled back, and we are closely monitoring the situation. Services should return to normal shortly as the servers complete their restart. Thank you for your understanding and patience.

  3. resolved Dec 02, 2024, 03:26 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 29, 2024

Elasticsearch outage

Detected by Pingoru
Nov 29, 2024, 09:11 AM UTC
Resolved
Nov 29, 2024, 12:22 PM UTC
Duration
3h 10m
Affected: Web applicationSearch engine
Timeline · 5 updates
  1. investigating Nov 29, 2024, 09:11 AM UTC

    We are currently experiencing an issue in our application related to Elasticsearch, which is affecting the ability to search and find items in the inventory. Updates will be shared here as we make progress toward resolving the issue.

  2. investigating Nov 29, 2024, 09:17 AM UTC

    We have identified the root cause of the issue and are pleased to confirm that no data has been lost. Our team is currently in the process of reindexing the search database, which we anticipate will fully resolve the problem. Thank you for your patience as we work diligently to restore full functionality.

  3. identified Nov 29, 2024, 09:45 AM UTC

    The issue has been identified and a fix is being implemented.

  4. monitoring Nov 29, 2024, 10:09 AM UTC

    A fix has been implemented and we are monitoring the results.

  5. resolved Nov 29, 2024, 12:22 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 29, 2024

Degraded performance

Detected by Pingoru
Aug 29, 2024, 02:21 PM UTC
Resolved
Aug 29, 2024, 02:57 PM UTC
Duration
36m
Affected: Web application
Timeline · 3 updates
  1. investigating Aug 29, 2024, 02:21 PM UTC

    We're currently experiencing performance issues affecting the platform. Our team is working to resolve the problem as quickly as possible.

  2. monitoring Aug 29, 2024, 02:46 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Aug 29, 2024, 02:57 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 20, 2024

Webshops not resolving (.booqable.store)

Detected by Pingoru
Jun 20, 2024, 08:49 AM UTC
Resolved
Jun 21, 2024, 08:01 AM UTC
Duration
23h 11m
Affected: DNS
Timeline · 5 updates
  1. investigating Jun 20, 2024, 08:49 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.

  2. investigating Jun 20, 2024, 08:55 AM UTC

    We are continuing to investigate this issue.

  3. identified Jun 20, 2024, 10:57 AM UTC

    We're working with the companies that manage our domains to restore service.

  4. monitoring Jun 20, 2024, 11:34 AM UTC

    The booqable.store domain has been restored. Shops should be coming back online now.

  5. resolved Jun 21, 2024, 08:01 AM UTC

    Both `booqable.shop` and `booqable.store` are resolving again. The issue has been resolved.

Read the full incident report →

Major June 13, 2024

Webshops not resolving

Detected by Pingoru
Jun 13, 2024, 11:12 AM UTC
Resolved
Jun 21, 2024, 08:00 AM UTC
Duration
7d 20h
Affected: DNS
Timeline · 7 updates
  1. 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.

  2. identified Jun 13, 2024, 11:13 AM UTC

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

  3. identified Jun 13, 2024, 03:44 PM UTC

    We are implementing a temporary patch to fix embedded stores and stores on root domains.

  4. 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`.

  5. 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.

  6. 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.

  7. resolved Jun 21, 2024, 08:00 AM UTC

    Both `booqable.shop` and `booqable.store` are resolving again. The issue has been resolved.

Read the full incident report →