Histórico de interrupções do Gotab

1. 14 Gwengolo 2026 da 17:09 UTCinvestigating

   Nossa equipe está investigando ativamente um problema que afeta atualmente logins no POS.

2. 14 Gwengolo 2026 da 17:31 UTCidentified

   Nossa equipe identificou o problema e está trabalhando para implementar uma correção.

3. 14 Gwengolo 2026 da 17:41 UTCinvestigating

   Estamos actualmente a investigar esta questão.

4. 14 Gwengolo 2026 da 17:59 UTCinvestigating

   Continuamos a investigar esta questão.

5. 14 Gwengolo 2026 da 17:59 UTCidentified

   A questão foi identificada e uma correção foi implementada para corrigir o comportamento.

6. 14 Gwengolo 2026 da 18:14 UTCmonitoring

   Nossa equipe implementou uma correção e continua monitorando a situação.

7. 14 Gwengolo 2026 da 18:34 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 1 Gwengolo 2026 da 21:31 UTCinvestigating

   Nossa equipe está atualmente investigando relatórios de erros de timeout ao carregar o Catálogo de Produtos através do Painel de Gestão.

2. 1 Gwengolo 2026 da 21:35 UTCinvestigating

   Continuamos a investigar esta questão.

3. 1 Gwengolo 2026 da 22:43 UTCidentified

   A nossa equipa determinou a causa do problema e uma solução será libertada. O Catálogo de Produtos foi negativamente impactado por problemas de API diretamente de Quickbooks.

4. 2 Gwengolo 2026 da 00:20 UTCmonitoring

   Nossa equipe implementou uma correção em relação aos problemas que carregam o Catálogo de Produtos. Continuaremos a acompanhar a situação por enquanto.

5. 2 Gwengolo 2026 da 00:32 UTCresolved

   Este incidente já foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Gouere 2026 da 23:21 UTCinvestigating

   Atualmente estamos investigando relatórios de problemas de carregamento e processamento de pagamentos entre POS e CFD

2. 24 Gouere 2026 da 23:32 UTCidentified

   Nossa equipe identificou a fonte do problema e implementou uma correção para corrigir o comportamento

3. 24 Gouere 2026 da 23:47 UTCmonitoring

   Uma correção foi implementada e continuamos a monitorar o comportamento.

4. 25 Gouere 2026 da 00:34 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 22:16 UTCinvestigating

   Estamos investigando relatórios de desempenho degradado impactando POS e Terminais de Pagamento

2. 17 Gouere 2026 da 22:42 UTCidentified

   O problema de latência do aplicativo foi identificado. Nossa equipe implementou mais recursos para reforçar o desempenho.

3. 17 Gouere 2026 da 22:50 UTCmonitoring

   Nossa equipe implementou uma correção e continuará monitorando os resultados.

4. 18 Gouere 2026 da 00:53 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 17 Gouere 2026 da 14:12 UTCinvestigating

   Nossa equipe está ativamente investigando relatórios de problemas intermitentes de carregamento de páginas no Painel do Gerente GoTab.

2. 17 Gouere 2026 da 14:34 UTCresolved

   Nossa equipe de engenharia identificou e implantou uma correção para o problema que afeta problemas intermitentes de carregamento de páginas no painel do gerente.

Traduzido automaticamente da atualização oficial do incidente.

1. 16 Gouere 2026 da 18:17 UTCinvestigating

   Estamos investigando relatórios de erros ao atualizar campos(menus, horários, estações, etc) do Painel de Gestão

2. 16 Gouere 2026 da 18:17 UTCinvestigating

   Continuamos a investigar esta questão.

3. 16 Gouere 2026 da 18:45 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

4. 16 Gouere 2026 da 18:49 UTCmonitoring

   Nossa equipe implementou uma correção para o comportamento relatado. Continuamos a acompanhar a situação.

5. 16 Gouere 2026 da 19:23 UTCresolved

   O problema foi resolvido e todos os campos dentro do Painel de Gestão estão operacionais

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Gouere 2026 da 18:32 UTCinvestigating

   Estamos ativamente investigando relatórios de banners off-line persistentes e mensagens "atualizando" impactando o POS

2. 9 Gouere 2026 da 19:50 UTCinvestigating

   Continuamos a investigar esta questão.

3. 9 Gouere 2026 da 19:51 UTCmonitoring

   Nossa equipe de desenvolvimento implementou recursos para resolver o problema. Estamos vendo o comportamento estabilizar para os operadores impactados, mas continuará monitorando entretanto.

4. 9 Gouere 2026 da 19:55 UTCresolved

   A nossa equipa confirmou que esta questão já foi resolvida.

Traduzido automaticamente da atualização oficial do incidente.

1. 24 Mezheven 2026 da 15:43 UTCinvestigating

   A nossa equipa está a investigar ativamente relatórios de alguns KDS que não mostram ordens. Reactivar o ecrã é eficaz para a maioria enquanto a nossa equipa investiga.

2. 24 Mezheven 2026 da 16:42 UTCinvestigating

   Continuamos a investigar alguns KDS que não recebem ordens.

3. 24 Mezheven 2026 da 17:40 UTCinvestigating

   A nossa equipa continua a investigar. Entretanto, existem duas soluções potenciais. 1. Se você tem um KDS recebendo ordens, alternar em todas as estações e operar de forma singular a partir do KDS que está recebendo ordens. 2. Em um laptop ou tablet onde logou no painel de gerenciamento GoTab. Abra uma nova aba e vá para gotab.io/kds e veja todas as estações e utilize isso como suas ordens temporárias do KDS se estiverem povoando.

4. 24 Mezheven 2026 da 18:30 UTCmonitoring

   Nossa equipe implementou uma correção para alguns KDS não exibindo ordens e continua a monitorar conforme vemos um retorno à atividade normal.

5. 24 Mezheven 2026 da 21:02 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 12 Mezheven 2026 da 01:06 UTCinvestigating

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

2. 12 Mezheven 2026 da 01:18 UTCinvestigating

   We are continuing to investigate this issue.

3. 12 Mezheven 2026 da 01:19 UTCmonitoring

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

4. 12 Mezheven 2026 da 01:24 UTCresolved

   Fix was successful. Payments behavior has returned to normal .

1. 9 Mae 2026 da 00:27 UTCinvestigating

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

2. 9 Mae 2026 da 00:31 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. 9 Mae 2026 da 01:11 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 9 Mae 2026 da 01:13 UTCresolved

   This incident has been resolved.

1. 18 Ebrel 2026 da 20:55 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. 19 Ebrel 2026 da 00:32 UTCresolved

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

1. 6 Meurzh 2026 da 18:39 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. 7 Meurzh 2026 da 16:34 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. 11 Meurzh 2026 da 17:07 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. 26 Cʼhwevrer 2026 da 18:33 UTCinvestigating

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

2. 26 Cʼhwevrer 2026 da 19:31 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. 26 Cʼhwevrer 2026 da 19:55 UTCmonitoring

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

4. 26 Cʼhwevrer 2026 da 20:56 UTCresolved

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

1. 18 Cʼhwevrer 2026 da 02:02 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. 18 Cʼhwevrer 2026 da 02:39 UTCidentified

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

3. 18 Cʼhwevrer 2026 da 03:01 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. 4 Kerzu 2025 da 15:41 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. 4 Kerzu 2025 da 15:46 UTCmonitoring

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

3. 4 Kerzu 2025 da 16:01 UTCresolved

   QR and kiosk ordering has been restored

1. 18 Du 2025 da 12:12 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. 18 Du 2025 da 12:28 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. 18 Du 2025 da 13:02 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. 18 Du 2025 da 14:05 UTCinvestigating

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

5. 18 Du 2025 da 14:45 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. 18 Du 2025 da 15:13 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. 26 Gwengolo 2025 da 23:42 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. 27 Gwengolo 2025 da 00:28 UTCresolved

   This incident has been resolved.

1. 28 Eost 2025 da 19:35 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. 28 Eost 2025 da 19:40 UTCinvestigating

   We are continuing to investigate this issue.

3. 28 Eost 2025 da 20:18 UTCidentified

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

4. 28 Eost 2025 da 20:50 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. 26 Mezheven 2025 da 13:31 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. 12 Mezheven 2025 da 18:52 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. 12 Mezheven 2025 da 19:20 UTCidentified

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

3. 12 Mezheven 2025 da 19:43 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. 12 Mezheven 2025 da 20:04 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. 12 Mezheven 2025 da 20:47 UTCmonitoring

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

6. 12 Mezheven 2025 da 21:33 UTCresolved

   This incident has been resolved.