Wakeo Outage History

There were 3 Wakeo outages since March 20, 2026 totaling 25h 26m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.wakeo.co

Notice April 29, 2026

Trusted Routes API and webapp unavailable

Detected by Pingoru: Apr 29, 2026, 02:30 PM UTC
Resolved: Apr 29, 2026, 12:30 PM UTC
Duration: —

Timeline · 1 update

resolved Apr 29, 2026, 02:08 PM UTC

Resolved — Service has been fully restored. Total downtime: 1h27. This disruption was a downstream consequence of the ongoing AWS incident in the Paris region (see related incident: API connectivity issues). Identified — The outage was traced back to the broader AWS connectivity issues currently impacting our infrastructure in the Paris region. A targeted mitigation was deployed to restore Trusted Routes API and webapp access. Investigating — We are investigating an outage affecting the Trusted Routes API and webapp. Both interfaces are currently unreachable.

Read the full incident report →

Major April 28, 2026

API connectivity issues

Detected by Pingoru: Apr 28, 2026, 02:39 PM UTC
Resolved: Apr 29, 2026, 04:06 PM UTC
Duration: 1d 1h

Affected: API V2

Timeline · 9 updates

identified Apr 28, 2026, 02:39 PM UTC

An AWS major incident on the Paris region is causing connectivity issues on our APIs since March, 27th. We're currently trying to mitigate the impact by changing the way we handle our API's network.
identified Apr 28, 2026, 02:39 PM UTC

We are continuing to work on a fix for this issue.
identified Apr 28, 2026, 02:52 PM UTC

A temporary fix is in place to bypass the failing resources. ⚠️ Customers using outbound IP whitelisting to our API are not be able to make their calls anymore for now. Calls relying on FQDN whitelist are not impacted.
monitoring Apr 28, 2026, 04:04 PM UTC

API is now considered as stable. ℹ️ We didn't detected any customers being blocked because of IP whitelisting, but are still closely monitoring API calls to detect them, and may adapt our network later depending on these results and customer requirements.
identified Apr 29, 2026, 08:52 AM UTC

Our fix seems to only have stabilized part of the calls. Customers are still raising connectivity issue this morning, we're investigating on a deeper issue.
identified Apr 29, 2026, 12:07 PM UTC

Incident has be escalated on AWS side. The root cause has been identified, one specific network resource has a flaky health status, causing API calls to randomly fail. We are currently working on a fix to bypass this resource and stabilize our APIs.
identified Apr 29, 2026, 12:28 PM UTC

Minor interruptions have to be expected during the incoming deployment of our fix.
monitoring Apr 29, 2026, 02:07 PM UTC

A fix has been deployed to bypass the failing network resource. All APIs should now be stable.
resolved Apr 29, 2026, 04:06 PM UTC

This incident has been resolved.

Read the full incident report →

Notice March 20, 2026

SFTP unreachable for password-based users

Detected by Pingoru: Mar 20, 2026, 08:47 AM UTC
Resolved: Mar 19, 2026, 07:30 PM UTC
Duration: —

Timeline · 1 update

resolved Mar 20, 2026, 08:47 AM UTC

Mistakes where made during the addition of new securities on our SFTP server, which resulted in password-based users not being able to access the server during this timeframe: - Start of the incident: 2026-03-19 19:41 UTC - End of the incident: 2026-03-20 08h40 UTC User connecting with an SSH key were not impacted. We're sorry for the inconvenience.

Read the full incident report →

Looking to track Wakeo downtime and outages?

Pingoru polls Wakeo's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Wakeo reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Wakeo alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Wakeo for free

5 free monitors · No credit card required