Booqable Outage History

Booqable is up right now

Booqable had 5 outages in the last 2 years totaling 58h 54m of downtime — averaging 0.2 incidents per month.

There were 5 Booqable outages since July 1, 2025 totaling 58h 54m 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 →