Genially had 24 outages in the last 2 years totaling 47h 25m of downtime — averaging 1 incident per month.
There were 24 Genially outages since November 29, 2024 totaling 47h 25m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The Genially viewer is failing to load or display content properly and redirect to error page.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The Genially viewer is failing to load or display content properly on some browsers. Users may experience blank screens, loading issues, or incomplete rendering. Investigation is needed to identify browser compatibility or recent update conflicts.
We have identified the root cause of the issue affecting the Genially viewer on certain browsers. A fix has been implemented and is currently being deployed. We will continue monitoring the situation to ensure full resolution. Thank you for your patience.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We had in issue with our database that provoked this problem
Creates correctly the Genially, but later redirects to a 403 error. Later is possible to enter to edit the new creation
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Due to ongoing issues with OpenAI services, some of the AI-powered features in our editor may not work as expected. We’re closely monitoring the situation and will restore full functionality as soon as the issue is resolved.
This incident has been resolved.
In some creations our users receive a 500 errors entering to view and live sessions
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We detected an issue when users open their creations to edit or share
The issue has been identified and a fix is being implemented.
This incident has been resolved.
At 06:40 UTC we introduced a change in production that provoked the layers order is reversed when users open their Geniallys in the Editor. Due to autosave, these changes were automatically published to the View, affecting all the creations opened during this incident.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Users are unable to import Google Slides into Genially. When attempting to do so, the process either fails to complete or the imported slides do not display correctly.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are experiencing issues when trying to load our viewer in Genially. Users report that the viewer either fails to load completely, takes too long, or displays an error message. This issue is affecting multiple users across different browsers and devices.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently experiencing an issue with the PPTX and PDF import feature in Genially. Users may be unable to upload or convert these file formats at the moment. Our team is investigating the cause and working on a fix. We apologize for the inconvenience and appreciate your patience. Further updates will be provided as soon as possible. Thank you for your understanding.
This incident has been resolved.
We are currently performing updates on some of our services. During this time, you may experience temporary disruptions or degraded performance. Our team is working to complete the updates as quickly as possible. Thank you for your patience and understanding.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
An improvement introduced in the editor provoked the issue
We are currently investigating this issue.
We are investigating the issue it may be related with one of our providers
The generative AI feats related with translations, content improvements, interactive questions and images are failing because a provider problem. We are in communication with the provider to resolve the issue
This incident has been resolved.
The plans pages in the web shows 0 instead the real prices, and in the setting plan page the customer can´t operate
An internal network issue has been identified and fixed
While a network infrastructure maintentance related with application load balancers for our payments service in Europe, we had missconfiguration with an intern traffic policy. That impacted in the purchase process and in the prices of the website. During 26 minutes the whole purchase process was blocked during the incident, and the website was showing incorrect 0€ prices for users from Europe. This incident didn't affected to the recurrent payments of existing customers from any country
Users with guests role received a 403 error when tried to enter to genially editor
This incident was caused because a bug introduced accidentally with an improvement deployed in our product. The incident was resolved after 6 hours and impacted in all the guests that were trying to access to edit geniallys. The editor was showing an error page “_You don’t have permissons to access this genially”_. Most of the time of this incident was caused because our detection time of the incidence. We introduced a fix to avoid this problem and defined different actions to detect more soon this kind of situations and improve our detection time
Auth is now operational and working properly