WeVideo Outage History
3 incidents recorded over the last 365 days, 3 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 WeVideo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 21, 2026 | PlayPosit Temporarily Unavailable for Urgent Security MaintenanceThis incident has been resolved. | 2h 17m | Resolved |
| Aug 26, 2026 | Application unresponsive caused by a DB CPU spikeThis incident has been resolved. | 1h 36m | Resolved |
| Jul 27, 2026 | Monitor page not loading for instructorsProduction testing has completed and the Issue is considered resolved. | 10h 56m | 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 WeVideo 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 WeVideo 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 WeVideo 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 WeVideo outage in this window ran 10h 56m, against a mean recovery of 4h 56m. If you depend on WeVideo 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.