GoTab Outage History

GoTab is up right now

GoTab had 10 outages in the last 2 years totaling 133h 33m of downtime — averaging 0.4 incidents per month.

There were 10 GoTab outages since August 28, 2025 totaling 133h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.gotab.io

Minor June 24, 2026

Orders Not Displayed on KDS

Detected by Pingoru
Jun 24, 2026, 03:43 PM UTC
Resolved
Jun 24, 2026, 09:02 PM UTC
Duration
5h 18m
Affected: Kitchen Display System (KDS)
Timeline · 5 updates
  1. investigating Jun 24, 2026, 03:43 PM UTC

    Our team is actively investigating reports of some KDS failing to display orders. Reactivating the display is effective for most in the interim while our team investigates.

  2. investigating Jun 24, 2026, 04:42 PM UTC

    We are continuing to investigate some KDS not receiving orders.

  3. investigating Jun 24, 2026, 05:40 PM UTC

    Our team is continuing to investigate. In the meantime, there are two potential solutions. 1. If you have a KDS receiving orders, toggle on all stations and operate singularly from the KDS that is receiving orders. 2. On a laptop or tablet where logged into the GoTab manager dashboard. Open a new tab and go to gotab.io/kds and view all stations and utilize that as your temporary KDS orders are populating.

  4. monitoring Jun 24, 2026, 06:30 PM UTC

    Our team has implemented a fix for some KDS not displaying orders and continue to monitor as we see a return to normal activity.

  5. resolved Jun 24, 2026, 09:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 12, 2026

Payment Failures Impacting Card Readers

Detected by Pingoru
Jun 12, 2026, 01:06 AM UTC
Resolved
Jun 12, 2026, 01:24 AM UTC
Duration
17m
Affected: Point of Sale (POS)Customer Facing Display (CFD)
Timeline · 4 updates
  1. investigating Jun 12, 2026, 01:06 AM UTC

    We are currently investigating reports of payment failures regarding credit/debit card transactions at the POS

  2. investigating Jun 12, 2026, 01:18 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jun 12, 2026, 01:19 AM UTC

    A fix has been implemented and we are continuing to monitor the situation.

  4. resolved Jun 12, 2026, 01:24 AM UTC

    Fix was successful. Payments behavior has returned to normal .

Read the full incident report →

Major May 9, 2026

Platform Latency

Detected by Pingoru
May 09, 2026, 12:27 AM UTC
Resolved
May 09, 2026, 01:13 AM UTC
Duration
45m
Affected: Point of Sale (POS)Card-Present Payment SystemKitchen Display System (KDS)
Timeline · 4 updates
  1. investigating May 09, 2026, 12:27 AM UTC

    We are currently investigating reported latency issues impacting POS and KDS displays.

  2. monitoring May 09, 2026, 12:31 AM UTC

    We've implemented mitigation for recent issues where some customers were experiencing delays with POS and KDS performance. We're seeing improvements and are closely monitoring the situation. For real-time updates, please visit status.gotab.io.

  3. monitoring May 09, 2026, 01:11 AM UTC

    We are continuing to monitor for any further issues.

  4. resolved May 09, 2026, 01:13 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 6, 2026

Tap to Pay Payment Failures

Detected by Pingoru
Mar 06, 2026, 06:39 PM UTC
Resolved
Mar 11, 2026, 05:07 PM UTC
Duration
4d 22h
Affected: Point of Sale (POS)Card-Present Payment System
Timeline · 3 updates
  1. investigating Mar 06, 2026, 06:39 PM UTC

    Our team is actively working with our payment processor to investigate failures to initialize payments when using Tap to Pay directly to a Samsung A14-17 device. This is not impacting tapping on any other payment devices such as AMS1 or S1F2.

  2. investigating Mar 07, 2026, 04:34 PM UTC

    Our team continues to investigate an outage for tap to pay directly to mobile phones. All other devices, including phones paired to an NYC1, remain unaffected.

  3. resolved Mar 11, 2026, 05:07 PM UTC

    Our team worked with our payment processor Adyen to update the Adyen SDK to fix any tap to pay issues. Most device should update the GoTab app automatically but to be sure, navigate to the Play Store and also check for a GoTab app update to version 4.1.0 version 77, which resolves any outstanding tap to pay issues.

Read the full incident report →

Minor February 26, 2026

System Latency

Detected by Pingoru
Feb 26, 2026, 06:33 PM UTC
Resolved
Feb 26, 2026, 08:56 PM UTC
Duration
2h 23m
Affected: Point of Sale (POS)KioskManager Dashboard
Timeline · 4 updates
  1. investigating Feb 26, 2026, 06:33 PM UTC

    We are currently investigating an issue with system latency that can affect POS loading, Kiosk Ordering and Manager Dashboard page loading.

  2. investigating Feb 26, 2026, 07:31 PM UTC

    We have mitigated the immediate issues while our engineers continue investigating the root cause of the ongoing incident. Further updates will be published as details become available.

  3. monitoring Feb 26, 2026, 07:55 PM UTC

    We are observing a return to normal request latency levels after implementing mitigations.

  4. resolved Feb 26, 2026, 08:56 PM UTC

    All system monitors are continuing to report health metrics within expected ranges.

Read the full incident report →

Critical February 18, 2026

Support chat unavailable

Detected by Pingoru
Feb 18, 2026, 02:02 AM UTC
Resolved
Feb 18, 2026, 03:01 AM UTC
Duration
59m
Affected: Chat Support
Timeline · 3 updates
  1. investigating Feb 18, 2026, 02:02 AM UTC

    GoTab's online support chat is currently experiencing an outage due to a hosting platform issue upstream. We are working with the service provider to restore service as quickly as possible. In the meantime, for support requests, please call or text our support hotline at +1-703-552-4690.

  2. identified Feb 18, 2026, 02:39 AM UTC

    We are beginning to see a gradual restoration of service from our upstream partner. GoChat is re-enabled on the Manager Dashboard.

  3. resolved Feb 18, 2026, 03:01 AM UTC

    Our service provider has restored connectivity and GoChat is operational. We apologize for the unexpected interruption. If you experience any lingering issues, please reach out to our support hotline at +1-703-552-4690.

Read the full incident report →

Critical December 4, 2025

QR and Kiosk ordering incident

Detected by Pingoru
Dec 04, 2025, 03:41 PM UTC
Resolved
Dec 04, 2025, 04:01 PM UTC
Duration
19m
Affected: QR OrderingKiosk
Timeline · 3 updates
  1. identified Dec 04, 2025, 03:41 PM UTC

    We are aware of and have identified an issue affecting guest ordering via QR and kiosk platforms. A fix is being implemented and will be released shortly.

  2. monitoring Dec 04, 2025, 03:46 PM UTC

    QR and kiosk ordering has been re-enabled and a permanent fix is underway.

  3. resolved Dec 04, 2025, 04:01 PM UTC

    QR and kiosk ordering has been restored

Read the full incident report →

Critical November 18, 2025

System outage

Detected by Pingoru
Nov 18, 2025, 12:12 PM UTC
Resolved
Nov 18, 2025, 03:13 PM UTC
Duration
3h
Affected: Uptime
Timeline · 6 updates
  1. investigating Nov 18, 2025, 12:12 PM UTC

    GoTab is currently experiencing a systemwide outage caused by an upstream global service provider. We are monitoring the status provided by Cloudflare and are investigating mitigation possibilities. The provider's status can be viewed here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  2. investigating Nov 18, 2025, 12:28 PM UTC

    We are observing improvements in connectivity but some customers are still continuing to experience intermittent Cloudflare error screens when using POS, KDS, Manager Dashboard and QR ordering.

  3. investigating Nov 18, 2025, 01:02 PM UTC

    Our service provider is continuing to investigate the issue. We are still observing periods of intermittent errors followed by periods of restored service.

  4. investigating Nov 18, 2025, 02:05 PM UTC

    We are continuing to work with our service provider to restore service. Further updates will be provided as they become available.

  5. monitoring Nov 18, 2025, 02:45 PM UTC

    We are observing connectivity being restored at our cloud provider. Concurrently, we also have a backup solution prepared in case of continuing issues as we monitor ongoing performance today.

  6. resolved Nov 18, 2025, 03:13 PM UTC

    Our cloud service provider has marked the incident as resolved and we are observing consistent service performance. We will continue to monitor and adjust accordingly.

Read the full incident report →

Minor September 26, 2025

Chat Platform Outage

Detected by Pingoru
Sep 26, 2025, 11:42 PM UTC
Resolved
Sep 27, 2025, 12:28 AM UTC
Duration
46m
Affected: Chat Support
Timeline · 2 updates
  1. investigating Sep 26, 2025, 11:42 PM UTC

    We are currently aware of an outage with our chat support platform. Please call or text our Support line at (703) 552-4690 if in need of immediate assistance.

  2. resolved Sep 27, 2025, 12:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor August 28, 2025

Text Notifications

Detected by Pingoru
Aug 28, 2025, 07:35 PM UTC
Resolved
Aug 28, 2025, 08:50 PM UTC
Duration
1h 14m
Affected: SMS
Timeline · 5 updates
  1. investigating Aug 28, 2025, 07:35 PM UTC

    A third-party text provider is currently experiencing text fulfillment delay and outages. We are in contact with their team as they work on the issue. Order confirmation and fulfillment texts are currently affected.

  2. investigating Aug 28, 2025, 07:39 PM UTC

    We are continuing to investigate this issue.

  3. investigating Aug 28, 2025, 07:40 PM UTC

    We are continuing to investigate this issue.

  4. identified Aug 28, 2025, 08:18 PM UTC

    We are seeing a return to normal activity from our text provider but are continuing to monitor.

  5. resolved Aug 28, 2025, 08:50 PM UTC

    Our messaging provider is reporting that services have been restored, although queued messages will take some time to process through the system. New messages sent will be delivered as normal.

Read the full incident report →