Is Wakeo down?
Last checked 6m agoNo incidents right now.
Wakeo is operational right now. Last checked 6m ago; the most recent incident resolved 4d ago.
Real-time Wakeo status, recent outages, and incident history — pulled directly from Wakeo's official status page at https://status.wakeo.co every 5 minutes. Pingoru tracks 14 Wakeo services and has captured 5 incidents in the last 90 days (99.76% uptime). Get email, Slack, Discord, or webhook alerts the moment Wakeo reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- resolved · May 20, 2026, 04:06 PM UTC
Resolved — Service has been fully restored. Total downtime: 2h10. Following the mitigation steps, the Trusted Routes API and webapp are fully stable and operating normally. We are continuing to monitor performance closely. Identified — The outage was traced back to an isolated, unprecedented surge in API request volume that exceeded our API Gateway's standard rate limits. To resolve the issue and restore full access, our engineering team successfully optimized and increased our gateway throughput capacity. Investigating — We are investigating an outage affecting the Trusted Routes API and webapp. Both interfaces are currently unreachable.
Latest: Resolved — Service has been fully restored. Total downtime: 2h10. Following the mitigation steps, the Trusted Routes API and webapp are fully stable and operating normally. We are …
-
-
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.
Latest: 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 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.
Latest: This incident has been resolved.
-
-
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.
Latest: 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: - St…
-
- Trusted Routes outage ResolvedStarted May 20, 2026, 04:06 PM UTC · Resolved May 20, 2026, 09:30 AM UTC · —
- Started Apr 29, 2026, 02:30 PM UTC · Resolved Apr 29, 2026, 12:30 PM UTC · —
- API connectivity issues ResolvedStarted Apr 28, 2026, 02:39 PM UTC · Resolved Apr 29, 2026, 04:06 PM UTC · 1d 1h
- Started Mar 20, 2026, 08:47 AM UTC · Resolved Mar 19, 2026, 07:30 PM UTC · —