Unitag Outage History
7 incidents recorded over the last 365 days, 4 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 Unitag Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 24, 2026 | Planned system upgradeScheduled maintenance is currently in progress. We will provide updates as necessary. | 30 min | Scheduled |
| Aug 19, 2026 | opn.to short links unreachable for Swisscom mobile customers (Switzerland)This incident has been resolved. | 22h 15m | Resolved |
| Jul 30, 2026 | Website unavailableThis incident has been resolved. | 8h 16m | Resolved |
| Jul 15, 2026 | QR codes scans partial outage in North America regionOur CDN infrastructure suffered a partial outage on its cache population operations for the North America region. The issue has now been resolved and we are investigating the root cause of the problem. | 0 min | Resolved |
| Jun 24, 2026 | Elevated error rate on Packaging /pa/ redirectionsThis incident has been resolved. | 5 min | Resolved |
| Jun 21, 2026 | Routine MaintenanceThe scheduled maintenance has been completed. | 10 min | Scheduled |
| Jun 19, 2026 | Dynamic-Pro infrastructure upgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 Unitag 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 Unitag 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 Unitag 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 Unitag outage in this window ran 22h 15m, against a mean recovery of 4h 37m. If you depend on Unitag 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.