Uberall Outage History
12 incidents recorded over the last 365 days, 11 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Uberall Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Nov 3, 2026 | Sandbox ResetMaintenance has started | 1h 8m | Resolved |
| Oct 20, 2026 | Sandbox ResetMaintenance has started | 1h 19m | Resolved |
| Oct 6, 2026 | Sandbox ResetSandbox is back up. | 1h 1m | Scheduled |
| Sep 22, 2026 | Sandbox ResetMaintenance has started | 1h 12m | Resolved |
| Sep 21, 2026 | Store Locator outageWe are investigating an issue affecting not set. | 5 min | Resolved |
| Sep 21, 2026 | Store Locator OutageThe issue has been fully resolved. | 13 min | Resolved |
| Sep 8, 2026 | Sandbox ResetMaintenance has started | 1h 0m | Resolved |
| Aug 25, 2026 | Sandbox ResetMaintenance has started | 41 min | Resolved |
| Aug 11, 2026 | Sandbox ResetMaintenance has started | 1h 49m | Resolved |
| Jul 14, 2026 | Sandbox ResetSandbox is back up. | 1005h 46m | Resolved |
| Jun 22, 2026 | production-webapp synthetic check success percent at 0% below 50% thresholdThis incident has been resolved. | 0 min | Resolved |
| Jan 27, 2026 | API performance degradationThe issue was fully resolved at 13:30 CET. | 5h 44m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Uberall incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Uberall Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Uberall acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Uberall outage in this window ran 41d 21h, against a mean recovery of 3d 12h. If you depend on Uberall in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.