GoTab Outage History
GoTab is up right nowPingoru has recorded 43 incidents for GoTab: 16 in the last 12 months and 2 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 4 of 720 (1%) |
| May 2026 | 1 | 1 of 744 (0%) |
| June 2026 | 2 | 6 of 720 (1%) |
| July 2026 | 5 | 7 of 744 (1%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 2 | 4 of 720 (1%) |
| October 2026 | 0 | 0 of 579 (0%) |
Incidents, newest first
Notice April 6, 2025 Slow POS login –
Started Apr 06, 2025, 01:30 PM UTC· resolved Apr 06, 2025, 01:30 PM UTC
- resolved Apr 12, 2025, 11:11 AM UTC
On 4/6/25, a number of customers reported experiencing intermittent slow login to the POS after PIN entry, followed by a prolonged loading screen. In some cases, a subset of customers also reported seeing a blank screen after logging into the POS. The issue was traced to latency in receiving responses from our Redis caching database. An investigation revealed a significant number of blocking calls that caused some requests to be paused while previous requests were being serviced. Our engineers increased resource allocation to the database as an immediate measure of relief and subsequently optimized the usage of Redis within our applications to reduce the number of calls and to also reduce the size of stored payloads. This optimization took place incrementally between 4/7/25 and 4/10/25, during which time we observed performance improvements on the order of several magnitudes.
Notice April 5, 2025 System Outage 40m
Started Apr 05, 2025, 06:30 AM UTC· resolved Apr 05, 2025, 07:10 AM UTC
- resolved Apr 12, 2025, 11:00 AM UTC
On 4/5/25, between 2:30 am EDT and 3:10 am EDT, GoTab experienced an outage similar to the prior day's incident. The root cause was the same. The investigation from the prior incident had inaccurately identified a failed database backup process on Amazon Web Services and a high priority ticket had been opened with AWS support. The investigation had been ongoing at the time this second incident occurred. As a result of additional data gathered in this secondary incident from 4/5/25, we were able to accurately diagnose and identify the true root cause of the issue. A newly-introduced bulk payment data processing job had inadvertently caused a spike in the number of real-time notifications that were being initiated from the database to Redis listeners to propagate outward to other consuming services. With this new understanding of the nature of the underlying issue, our engineers immediately deactivated the scheduled task and revised the processing strategy to avoid future similar incidents.
Critical November 14, 2024 Payments gateway service disruption 1h Card-Present Payment System
Started Nov 14, 2024, 03:04 PM UTC· resolved Nov 14, 2024, 04:05 PM UTC
- investigating Nov 14, 2024, 03:04 PM UTC
We are aware of an ongoing incident with Adyen payments that is causing delays and timeouts. Adyen's engineering team is currently investigating. The latest status updates are posted on https://status.adyen.com/
- identified Nov 14, 2024, 03:15 PM UTC
Adyen reports they have identified the root cause of the issue and are actively working on a resolution.
- monitoring Nov 14, 2024, 03:28 PM UTC
We are seeing a restoration of Adyen services and are monitoring updates from their engineering team.
- resolved Nov 14, 2024, 04:05 PM UTC
Adyen is reporting the incident has been resolved.