Unlayer Outage History

Unlayer is up right now

Unlayer had 1 outage in the last 2 years totaling 11h 28m of downtime — averaging 0 incidents per month.

There was 1 Unlayer outage since October 20, 2025 totaling 11h 28m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.unlayer.com

Notice October 20, 2025

AWS Service Disruption Affecting Unlayer Services

Detected by Pingoru
Oct 20, 2025, 11:55 AM UTC
Resolved
Oct 20, 2025, 11:24 PM UTC
Duration
11h 28m
Timeline · 3 updates
  1. monitoring Oct 20, 2025, 11:55 AM UTC

    Earlier today, a global outage in Amazon Web Services (AWS) impacted multiple Unlayer systems, including our Backend API, Account services (login and signup), and Export API. As of now: Editor and Builders: Fully operational. Export API: Functionality has been restored and is performing normally. Account (Login / Signup): Working as expected. Backend API: Previously degraded, but now stable. We continue to monitor for residual impact. Like many other online platforms, Unlayer experienced intermittent disruptions as AWS worked to restore global stability. Our engineering team actively monitored all systems and confirmed full recovery across affected components. We are continuing to observe our systems to ensure everything remains fully functional. You can follow AWS’s own recovery updates here: https://health.aws.amazon.com/health/status Thank you for your patience and understanding during this AWS-related incident.

  2. monitoring Oct 20, 2025, 08:46 PM UTC

    We’re continuing to monitor our systems following the earlier AWS service disruption. At this time, all Unlayer services are fully operational and performing normally. We’ll continue to keep a close eye on performance as AWS fully stabilizes their infrastructure. For updates from AWS, visit: https://health.aws.amazon.com/health/status Thank you for your patience while we ensured everything was back to normal.

  3. resolved Oct 20, 2025, 11:24 PM UTC

    This incident has been resolved.

Read the full incident report →