Gynzy Outage History
11 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 Gynzy Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Oct 23, 2026 | Degraded performance | Het kan iets langer duren om Gynzy te laden.Het probleem is opgelost | The problem has been resolved | 5 min | Resolved |
| Sep 11, 2026 | Gepland onderhoud / Scheduled maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 6, 2026 | Gebruikers zonder gekoppelde school kunnen niet inloggen / Users without linked school cannot log inHet probleem is opgelost. / This incident has been resolved. | 37 min | Resolved |
| Jun 27, 2026 | Gepland onderhoud / Planned maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jun 6, 2026 | Gepland onderhoud / Planned maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 30, 2026 | Gepland onderhoud / Planned maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| May 23, 2026 | Gepland onderhoud / Planned maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Jan 30, 2026 | Problemen met laden / Loading issuesWe have identified the incident with loading Gynzy and released a fix. Everything should work after reloading the Gynzy website. | 9 min | Resolved |
| Jan 13, 2026 | Gepland onderhoud / Planned maintenanceThe scheduled maintenance has been completed. | 30 min | Scheduled |
| Jan 10, 2026 | Gepland onderhoud / Planned maintenanceThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Nov 29, 2025 | Gepland onderhoud / Planned maintenanceThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
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 Gynzy 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 Gynzy 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 Gynzy 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 Gynzy outage in this window ran 2h, against a mean recovery of 57 min. If you depend on Gynzy 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.