Historial de interrupciones de Gotab

1. September 1, 2026 at 9:31 PM UTCinvestigating

   Nuestro equipo está actualmente investigando los informes de errores de timeout al cargar el Catálogo de productos a través del panel Manager.

2. September 1, 2026 at 9:35 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. September 1, 2026 at 10:43 PM UTCidentified

   Nuestro equipo determinó la causa del problema y una solución será liberada inminentemente. El catálogo de productos fue impactado negativamente por los problemas de API directamente desde Quickbooks.

4. September 2, 2026 at 12:20 AM UTCmonitoring

   Nuestro equipo ha implementado una solución sobre temas cargando el Catálogo de Producto. Seguiremos vigilando la situación por el momento.

5. September 2, 2026 at 12:32 AM UTCresolved

   Este incidente ya se ha resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 24, 2026 at 11:21 PM UTCinvestigating

   Actualmente estamos investigando informes de problemas de carga y procesamiento de pagos entre POS y CFD

2. July 24, 2026 at 11:32 PM UTCidentified

   Nuestro equipo ha identificado la fuente del problema y ha implementado una solución para corregir el comportamiento

3. July 24, 2026 at 11:47 PM UTCmonitoring

   Se ha implementado una solución y seguimos monitoreando el comportamiento.

4. July 25, 2026 at 12:34 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 10:16 PM UTCinvestigating

   Estamos investigando informes de resultados degradados que impactan POS y Terminales de Pago

2. July 17, 2026 at 10:42 PM UTCidentified

   Se ha identificado la cuestión de latencia de la aplicación. Nuestro equipo ha implementado más recursos para reforzar el rendimiento.

3. July 17, 2026 at 10:50 PM UTCmonitoring

   Nuestro equipo ha implementado una solución y seguirá monitoreando los resultados.

4. July 18, 2026 at 12:53 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 17, 2026 at 2:12 PM UTCinvestigating

   Nuestro equipo está investigando activamente informes de problemas de carga intermitente de páginas en el panel de gestión GoTab.

2. July 17, 2026 at 2:34 PM UTCresolved

   Nuestro equipo de ingeniería ha identificado y desplegado una solución para el problema que afecta a las cuestiones de carga intermitente de páginas en el panel de administración.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 16, 2026 at 6:17 PM UTCinvestigating

   Estamos investigando informes de errores al actualizar campos (menús, horarios, estaciones, etc) del Administrador Dashboard

2. July 16, 2026 at 6:17 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 16, 2026 at 6:45 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. July 16, 2026 at 6:49 PM UTCmonitoring

   Nuestro equipo ha implementado una solución para el comportamiento reportado. Seguimos vigilando la situación.

5. July 16, 2026 at 7:23 PM UTCresolved

   El problema se ha resuelto y todos los campos dentro del panel de gestión están operativos

Traducido automáticamente desde la actualización oficial del incidente.

1. July 9, 2026 at 6:32 PM UTCinvestigating

   Estamos investigando activamente informes de persistentes banners fuera de línea y mensajes de "actualización" que impactan al POS

2. July 9, 2026 at 7:50 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 9, 2026 at 7:51 PM UTCmonitoring

   Nuestro equipo dev ha implementado recursos para abordar el problema. Estamos viendo estabilizar el comportamiento para los operadores impactados, pero seguirá monitoreando mientras tanto.

4. July 9, 2026 at 7:55 PM UTCresolved

   Nuestro equipo ha confirmado que esta cuestión se ha resuelto desde entonces.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 24, 2026 at 3:43 PM UTCinvestigating

   Nuestro equipo está investigando activamente informes de algunos KDS que no muestran órdenes. Reactivar la pantalla es eficaz para la mayoría de los interinos mientras nuestro equipo investiga.

2. June 24, 2026 at 4:42 PM UTCinvestigating

   Seguimos investigando a algunos KDS que no reciben órdenes.

3. June 24, 2026 at 5:40 PM UTCinvestigating

   Nuestro equipo continúa investigando. Mientras tanto, hay dos posibles soluciones. 1. Si usted tiene un KDS que recibe órdenes, rebosa en todas las estaciones y opera singularmente desde el KDS que está recibiendo órdenes. 2. En un portátil o tableta donde se registró en el panel de administración GoTab. Abra una nueva pestaña y vaya a gotab.io/kds y vea todas las estaciones y utilice eso como sus órdenes de KDS temporales si están populando.

4. June 24, 2026 at 6:30 PM UTCmonitoring

   Nuestro equipo ha implementado una solución para algunos KDS que no muestran pedidos y siguen monitoreando mientras vemos un retorno a la actividad normal.

5. June 24, 2026 at 9:02 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. June 12, 2026 at 1:06 AM UTCinvestigating

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

2. June 12, 2026 at 1:18 AM UTCinvestigating

   We are continuing to investigate this issue.

3. June 12, 2026 at 1:19 AM UTCmonitoring

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

4. June 12, 2026 at 1:24 AM UTCresolved

   Fix was successful. Payments behavior has returned to normal .

1. May 9, 2026 at 12:27 AM UTCinvestigating

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

2. May 9, 2026 at 12:31 AM UTCmonitoring

   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. May 9, 2026 at 1:11 AM UTCmonitoring

   We are continuing to monitor for any further issues.

4. May 9, 2026 at 1:13 AM UTCresolved

   This incident has been resolved.

1. April 18, 2026 at 8:55 PM UTCinvestigating

   Our team is still actively investigating platform latency issues affecting orders not immediately updating in the KDS, slow POS response and CFDs having difficulty connecting to the POS.

2. April 19, 2026 at 12:32 AM UTCresolved

   Our engineering team has resolved the incident and verified that normal operations have been restored.

1. March 6, 2026 at 6:39 PM UTCinvestigating

   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. March 7, 2026 at 4:34 PM UTCinvestigating

   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. March 11, 2026 at 5:07 PM UTCresolved

   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.

1. February 26, 2026 at 6:33 PM UTCinvestigating

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

2. February 26, 2026 at 7:31 PM UTCinvestigating

   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. February 26, 2026 at 7:55 PM UTCmonitoring

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

4. February 26, 2026 at 8:56 PM UTCresolved

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

1. February 18, 2026 at 2:02 AM UTCinvestigating

   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. February 18, 2026 at 2:39 AM UTCidentified

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

3. February 18, 2026 at 3:01 AM UTCresolved

   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.

1. December 4, 2025 at 3:41 PM UTCidentified

   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. December 4, 2025 at 3:46 PM UTCmonitoring

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

3. December 4, 2025 at 4:01 PM UTCresolved

   QR and kiosk ordering has been restored

1. November 18, 2025 at 12:12 PM UTCinvestigating

   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. November 18, 2025 at 12:28 PM UTCinvestigating

   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. November 18, 2025 at 1:02 PM UTCinvestigating

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

4. November 18, 2025 at 2:05 PM UTCinvestigating

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

5. November 18, 2025 at 2:45 PM UTCmonitoring

   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. November 18, 2025 at 3:13 PM UTCresolved

   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.

1. September 26, 2025 at 11:42 PM UTCinvestigating

   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. September 27, 2025 at 12:28 AM UTCresolved

   This incident has been resolved.

1. August 28, 2025 at 7:35 PM UTCinvestigating

   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. August 28, 2025 at 7:40 PM UTCinvestigating

   We are continuing to investigate this issue.

3. August 28, 2025 at 8:18 PM UTCidentified

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

4. August 28, 2025 at 8:50 PM UTCresolved

   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.

1. June 26, 2025 at 1:31 PM UTCresolved

   We detected a spike in errors experienced by guests adding credits cards to their accounts during QR ordering. We investigated and found our payment gateway introduced an unknown change to data formatting returned from their API that caused errors within our integration. No payment data was lost during this time and we are in communication with our payment gateway to determine why the change occurred and establish improved lines of communication of changes to reduce these type of service interruptions.

1. June 12, 2025 at 6:52 PM UTCinvestigating

   We are aware of and monitoring an intermittent issue with Cloudflare, our third-party cloud connectivity provider. Customers using the 1.1.1.1 app on Android devices may experience slow or interrupted network connectivity. Integrators using api.gotab.io may also experience interruptions in connectivity. We will update further as we receive additional details. The upstream provider's real-time status can be found at https://www.cloudflarestatus.com/

2. June 12, 2025 at 7:20 PM UTCidentified

   Cloudflare is reporting that the source of the issue has been identified and recovery is underway.

3. June 12, 2025 at 7:43 PM UTCidentified

   Our phone provider is also experiencing related issues which affects our inbound and outbound support phone capabilities. https://status.openphone.co/ If you experience any issues calling in for support, please utilize our chat support from the manager app, manager dashboard or KDS in the interim.

4. June 12, 2025 at 8:04 PM UTCidentified

   Cloudflare reports engineering work continues to be underway to restore all services as quickly as possible. Additional updates will be published as information becomes available.

5. June 12, 2025 at 8:47 PM UTCmonitoring

   Cloudflare reports that the core affected services are restored and are being monitored for recovery.

6. June 12, 2025 at 9:33 PM UTCresolved

   This incident has been resolved.

1. June 10, 2025 at 6:01 PM UTCinvestigating

   Our team is currently investigating a delay in sales page information updating. This will also affect the PMIX and Sales information within the GoTab Manager app.

2. June 10, 2025 at 6:05 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 10, 2025 at 6:27 PM UTCidentified

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

4. June 10, 2025 at 7:44 PM UTCresolved

   This incident has been resolved.