UXCam Outage History
4 incidents recorded over the last 365 days, 2 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 UXCam Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 25, 2026 | Scheduled Maintenance - UXCam PlatformThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 16, 2026 | Scheduled Maintenance: EU Database UpgradeThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Mar 2, 2026 | UAE Region Service Disruption (AWS Outage)Following our previous communications, the disruption in the Amazon Web Services (AWS) UAE Region (ME-CENTRAL-1) is expected to take a considerable amount of time to fully recover, and there have been no recent updates… | 243h 8m | Resolved |
| Nov 18, 2025 | Degradation in Processing SessionsRouting traffic away from Cloudflare has fully resolved the issue. While the earlier disruption caused a temporary drop in incoming sessions, all delayed sessions were eventually received. Thank you for your patience… | 30 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 UXCam 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 UXCam 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 UXCam 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 UXCam outage in this window ran 10d 3h, against a mean recovery of 2d 13h. If you depend on UXCam 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.