Checkfront Outage History

Checkfront is up right now

Checkfront had 7 outages in the last 2 years totaling 17h 11m of downtime — averaging 0.3 incidents per month.

There were 7 Checkfront outages since February 10, 2026 totaling 17h 11m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://checkfront.statuspage.io

Notice August 25, 2026

NextGen Widgets Not Loading

Detected by Pingoru
Aug 25, 2026, 02:00 PM UTC
Resolved
Aug 25, 2026, 08:00 PM UTC
Duration
5h 59m
Affected: us-west1us-central1us-east1
Timeline · 3 updates
  1. investigating Aug 25, 2026, 02:00 PM UTC

    We are currently investigating an issue where some NextGen booking widgets are not loading as expected. Our team is actively investigating and working to restore service as quickly as possible. We will provide another update as soon as more information is available.

  2. monitoring Aug 25, 2026, 02:44 PM UTC

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

  3. resolved Aug 25, 2026, 08:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice August 13, 2026

Intermittent App Slowness and Access Issues

Detected by Pingoru
Aug 13, 2026, 10:15 PM UTC
Resolved
Aug 13, 2026, 11:18 PM UTC
Duration
1h 2m
Affected: us-central1
Timeline · 2 updates
  1. monitoring Aug 13, 2026, 10:49 PM UTC

    We're aware that some customers may be experiencing intermittent slowness or brief interruptions while accessing the app, related to the scheduled maintenance we performed earlier. Our team is actively working to fully resolve this, and we expect things to stabilize soon. We apologize for the inconvenience and appreciate your patience.

  2. resolved Aug 13, 2026, 11:18 PM UTC

    The issue has been resolved, and app performance has returned to normal. We appreciate your patience while our team worked to address this.

Read the full incident report →

Major June 10, 2026

European customers are unable to login

Detected by Pingoru
Jun 10, 2026, 07:39 AM UTC
Resolved
Jun 10, 2026, 07:53 AM UTC
Duration
13m
Affected: europe-west1
Timeline · 2 updates
  1. identified Jun 10, 2026, 07:39 AM UTC

    We're aware of the issue affecting our European customers trying to login. Team has identified the issue and is working on the resolution.

  2. resolved Jun 10, 2026, 07:53 AM UTC

    Issue is resolved, we apologise for any inconvenience caused.

Read the full incident report →

Notice June 8, 2026

Next-Gen Account Access Issue: 504 Gateway Timeout Errors

Detected by Pingoru
Jun 08, 2026, 07:13 PM UTC
Resolved
Jun 08, 2026, 07:31 PM UTC
Duration
17m
Affected: northamerica-northeast1europe-west1australia-southeast1us-west1us-central1asia-northeast1us-east1
Timeline · 4 updates
  1. investigating Jun 08, 2026, 07:13 PM UTC

    We are aware of an issue affecting Next-Gen account access, resulting in 504 Gateway Timeout errors for some users. Our team is actively investigating and working toward a resolution. We appreciate your patience while we work to restore service.

  2. investigating Jun 08, 2026, 07:14 PM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 08, 2026, 07:24 PM UTC

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

  4. resolved Jun 08, 2026, 07:31 PM UTC

    The issue affecting Next-Gen account access has been resolved, and services are operating normally. During a cluster upgrade, a scaling issue prevented critical cluster components (including DNS) from starting correctly, resulting in 504 Gateway Timeout errors for some users. The issue has now been remediated and service fully restored. We apologize for the disruption.

Read the full incident report →

Notice May 5, 2026

"Account not secure" errors upon access

Detected by Pingoru
May 05, 2026, 12:31 AM UTC
Resolved
May 05, 2026, 12:45 AM UTC
Duration
13m
Timeline · 2 updates
  1. investigating May 05, 2026, 12:31 AM UTC

    We are currently investigating an issue where some users are receiving an "account not secure" warning when attempting to access their Checkfront accounts. Our engineering team is actively looking into the root cause and working to resolve this as quickly as possible. We apologize for the inconvenience and will provide another update shortly.

  2. resolved May 05, 2026, 12:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Major April 15, 2026

NextGen Account Access Outage

Detected by Pingoru
Apr 15, 2026, 03:46 PM UTC
Resolved
Apr 15, 2026, 09:58 PM UTC
Duration
6h 12m
Affected: us-west1us-central1us-east1
Timeline · 5 updates
  1. investigating Apr 15, 2026, 03:46 PM UTC

    We have received reports of users experiencing slow loading times and errors when accessing their booking pages. We are currently investigating the cause.

  2. investigating Apr 15, 2026, 04:02 PM UTC

    We are continuing to investigate this issue.

  3. investigating Apr 15, 2026, 04:03 PM UTC

    We are continuing to investigate this issue.

  4. monitoring Apr 15, 2026, 04:27 PM UTC

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

  5. resolved Apr 15, 2026, 09:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical February 10, 2026

Planned Cluster Update Causing Account Downtime

Detected by Pingoru
Feb 10, 2026, 07:16 PM UTC
Resolved
Feb 10, 2026, 10:29 PM UTC
Duration
3h 12m
Affected: northamerica-northeast1europe-west1australia-southeast1us-west1us-central1asia-northeast1us-east1
Timeline · 6 updates
  1. investigating Feb 10, 2026, 07:16 PM UTC

    We are currently performing a cluster update. During this activity, account-related services are temporarily unavailable. The team is actively working on the update, and services will be restored once the process completes. We’ll share another update as soon as accounts are back online. Thank you for your patience.

  2. investigating Feb 10, 2026, 07:20 PM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 10, 2026, 07:28 PM UTC

    We are continuing to investigate this issue.

  4. identified Feb 10, 2026, 07:57 PM UTC

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

  5. monitoring Feb 10, 2026, 08:02 PM UTC

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

  6. resolved Feb 10, 2026, 10:29 PM UTC

    This incident has been resolved.

Read the full incident report →