Slazzer Outage History
3 incidents recorded over the last 365 days, 2 of them resolved, 1 still open. 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 Slazzer Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Dec 27, 2025 | Slazzer Desktop App 5.0.1 BETA UpdateVersion 5.0.1 includes a smoother user experience along with small bug fixes identified after the previous beta release. | — | Investigating |
| Dec 27, 2025 | Slazzer Desktop App 5.0.0 BETA has been successfully launchedThis version includes performance improvements and updates. Please report any issues or feedback to help us refine the final release. | -18360 min | Resolved |
| Nov 20, 2025 | Editor UI/UX Improvements DeployedWe have updated all editors to make them more user-friendly. The improvements include better UI/UX, smoother interactions, and enhanced usability for all users. The update is now live and functioning as expected. | -2828 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 Slazzer 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 Slazzer 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 Slazzer 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.