Historical record of incidents for Unlayer
Report: "Google Chrome Update - Editor Output Issues"
Last updateGoogle Chrome's latest version 112 has caused some extra margins and spacing issues. We have identified the cause and resolved this.
Report: "Export API"
Last updateThe incident has been resolved.
We have deployed a potential fix. We are now going to be monitoring to see if the issue has been resolved.
We have identified the issue to be memory related with the Chrome version on Lambda. Our engineers are exploring different options to fix the issue.
We have received reports of intermittent failures on our cloud export API. We are currently investigating this issue and trying to identify the root cause.
Report: "Spike in Errors"
Last updateThe issue has been resolved.
We've confirmed that this is an issue with Heroku. You can track that incident here: https://status.heroku.com/incidents/2402
Report: "AWS US-EAST-1"
Last updateThis incident has been resolved and verified. It is working fine for the last three hours.
The editor is working fine with some intermittent issues in the API. We are continuously monitoring AWS US-East 1.
We are continuously monitoring AWS US-East 1. However, our engineering team has resolved the editor on our end, and it is working in offline mode. There is some intermittent outage in the API.
AWS US EAST-1 is down for many companies all over the world. We are closely monitoring it, and we apologize for this inconvenience. As per AWS, they have already identified the root cause and are actively working towards recovery.
Report: "Database Maintenance"
Last updateThis incident has been resolved.
Our database provider is performing maintenance on the database. We are actively working on resolving this issue.
Report: "This is an example incident"
Last updateWhen your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
Empathize with those affected and let them know everything is operating as normal.
As you continue to work through the incident, update your customers frequently.
Let your users know once a fix is in place, and keep communication clear and precise.