Uscreen Outage History
14 incidents recorded over the last 365 days, 13 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 Uscreen Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 28, 2026 | Degraded live streaming and video playbackOur 3rd party provider has fixed their outage. Live streams and videos are working normally. Thank you for your patience during this time. | 57 min | Resolved |
| Oct 18, 2026 | Degraded performance — Admin and StorefrontsBetween approximately 19:35 and 19:39 UTC on October 18, the platform experienced a brief period of degraded performance affecting admin dashboards and storefronts. Services auto-recovered and remained fully… | -52 min | Resolved |
| Oct 15, 2026 | Intermittent errors — Admin and StorefrontsOn October 14, from 23:35 to 23:46 UTC (7:35 PM to 7:46 PM EDT), some users saw intermittent “Rate exceeded” errors and slower-than-usual load times on admin dashboards and storefronts. The cause was a service… | -54 min | Resolved |
| Sep 13, 2026 | Service unavailable due to a network error.**Incident:** Storefront errors and degraded performance **Date:** September 13, 2026 **Duration:** 12:09–12:47 UTC and 13:18–13:26 UTC, approximately 45 minutes of customer impact ## Summary Some customers and… | 2h 8m | Resolved |
| Jul 14, 2026 | Errors In Video PlaybackThis incident has been resolved. Our CDN partner confirmed the fix, and video playback has returned to normal. We appreciate your patience while this was being resolved. | 2h 23m | Resolved |
| Jul 8, 2026 | Partial CDN issue affecting page stylingWe've applied a change that has resolved the immediate issue — visitors on affected customer websites should no longer see pages loading without proper styling. The underlying cause appears to be related to how DNS… | 1h 46m | Resolved |
| May 4, 2026 | Degraded Performance# Incident Post-Mortem: May 4, 2026 Database Upgrade ## A note from our team On Monday, May 4, 2026, Uscreen experienced a significant performance incident following a planned PostgreSQL database upgrade. Storefronts… | 5h 8m | Resolved |
| May 4, 2026 | Degraded PerformanceThis incident has been resolved. | 1h 32m | Resolved |
| May 4, 2026 | Scheduled Maintenance: Server MaintenanceThe scheduled maintenance has been completed. | 15 min | Scheduled |
| May 3, 2026 | Degraded performance — Admin and StorefrontsThis incident has been resolved. Services across admin dashboards and storefronts are fully restored and operating normally. Thank you for your patience while our engineering team worked through this. | 22 min | Resolved |
| Apr 12, 2026 | Partial Service Degradation - ResolvedWe experienced a brief service disruption lasting approximately 2 minutes. The issue has been fully resolved and all systems are operating normally. We apologize for any inconvenience caused. | 0 min | Resolved |
| Feb 23, 2026 | Video Upload FailuresThe third-party provider has confirmed that the earlier issue has been resolved. Video uploads are now being processed normally. | 2h 8m | Resolved |
| Feb 10, 2026 | Slow loading or errors on Uscreen subdomain storefrontsOur third-party partner has resolved the issue, and our team continues to monitor for any changes. All storefronts are operational. | 2h 53m | Resolved |
| Jan 15, 2026 | Brief Performance Degradation Due to DDoS AttackWe experienced a brief performance degradation due to a DDoS attack that impacted platform performance for approximately 4 minutes. Our team responded quickly, mitigated the attack, and deployed additional protections… | -17 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 Uscreen 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 Uscreen 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 Uscreen 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 Uscreen outage in this window ran 5h 8m, against a mean recovery of 1h 47m. If you depend on Uscreen 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.