Uniqode Outage History
5 incidents recorded over the last 365 days, 5 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 Uniqode Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 15, 2026 | Some QR code scans are failingA fix has been deployed, and QR codes on custom domains that use UTM parameters have been loading normally again since 15:31 UTC. We are monitoring to make sure everything remains stable. | 1h 6m | Resolved |
| Oct 8, 2026 | Intermittent Uniqode Dashboard UnavailabilityOn 8 October 2026, between 15:47 and 18:45 UTC, some customers were intermittently unable to access the Uniqode dashboard. QR Code scans, redirects and scan data collection were not affected, and no customer data was… | -130 min | Resolved |
| Jul 9, 2026 | Gateway Timeout Errors Affecting Enterprise CustomersThis issue has been resolved. It was caused by heavy demand on the servers that power Enterprise Views, which led to slow or failed loading for some users. We increased server capacity to handle the load, and everything… | 1h 5m | Resolved |
| May 21, 2026 | Service degradationA recent backend change has been fully rolled back and dashboard performance has returned to normal. We have confirmed recovery across QR Code list, status, and management endpoints. We're following up with a… | 1h 21m | Resolved |
| Feb 12, 2026 | Service Disruption – QR Code Scans and Dashboard AccessInvestigating (05:38 PST): We are aware of an issue affecting QR code scans and access to the Uniqode dashboard. Our engineering team is actively investigating. Identified (07:02 PST): The issue has been identified as a… | 0 min | 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 Uniqode 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 Uniqode 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 Uniqode 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 Uniqode outage in this window ran 1h 21m, against a mean recovery of 53 min. If you depend on Uniqode 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.