Genially Outage History
5 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 Genially Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Jul 29, 2026 | Timeout on genially viewerThis incident has been resolved. | 2h 10m | Resolved |
| Apr 13, 2026 | Genially viewer redirect to error pageThis incident has been resolved. | 23 min | Resolved |
| Feb 19, 2026 | Genially Viewer Not Working on Certain BrowsersThis incident has been resolved. | 1h 5m | Resolved |
| Feb 10, 2026 | Real-time collaboration system upgradeThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Nov 19, 2025 | Production cluster upgradeThe scheduled maintenance has been completed. | 4h 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 Genially 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 Genially 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 Genially 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 Genially outage in this window ran 4h, against a mean recovery of 2h 20m. If you depend on Genially 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.