Wire Cloud Outage History

14 incidents recorded over the last 365 days, 14 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.

Live Wire Cloud status100.00% uptime history

Every Recorded Wire Cloud Incident

Wire Cloud incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Nov 3, 2026Calling cluster is under maintenanceMaintenance has started1h 54mResolved
Sep 17, 2026Database maintenanceMaintenance has started112h 11mResolved
Sep 14, 2026Unable to have long calls with large (~40) peopleWe have confirmed that the issue only affects an internal team and is not affecting other customers. All system are operational. We will continue the investigation for the internal team but we will close the incident as…1h 20mResolved
Sep 8, 2026Group calling version upgradeMaintenance has started1h 13mResolved
Aug 17, 2026Wire Cloud Production cluster version upgradeMaintenance is in progress. No service impact expected.386h 23mResolved
Aug 17, 2026Wire cloud calling cluster version upgradeMaintenance has started192h 5mResolved
May 20, 2026Delayed message deliveryThis incident has been resolved.14 minResolved
Apr 23, 2026Federated group calls may not connectThis incident has been resolved.24h 46mResolved
Apr 20, 2026Brig throws 5xx errors after release of wire-server 5.29.0This incident has been resolved.6 minResolved
Apr 20, 2026Increased error rate on Wire APIThe issue is fully resolved. All systems operational.9 minResolved
Apr 9, 2026Conference calls not establishedThe issue is fully resolved. All systems operational.7h 6mResolved
Mar 10, 2026"No internet" banner on Wire WebAppThe issue is fully resolved. All systems operational.7 minResolved
Mar 4, 2026Wire for Web and Desktop not availableThe issue is fully resolved. All systems operational.-40196 minResolved
Mar 3, 2026Partial Outage of WebSocket connectionsService availability for **[app.wire.com](http://app.wire.com/)** and the Wire Desktop App has been restored. Please reload your browser or restart your desktop client to ensure you are running the latest version…-48675 minResolved

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 Wire Cloud 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 Wire Cloud 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 Wire Cloud 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 Wire Cloud outage in this window ran 16d 2h, against a mean recovery of 2d 12h. If you depend on Wire Cloud 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.