Wakeo Outage History

Wakeo is up right now

Pingoru has recorded 27 incidents for Wakeo: 4 in the last 12 months and 0 in the last 90 days.

Source: status.wakeo.co

27incidents recorded
4last 12 months
0last 90 days
9 hourstypical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking Wakeo in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 2026225 of 720 (4%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 512 (0%)

Incidents, newest first

Notice May 20, 2026 Trusted Routes outage –

Started May 20, 2026, 09:30 AM UTC· resolved May 20, 2026, 09:30 AM UTC

  1. 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.

Read the full incident report →

Notice April 29, 2026 Trusted Routes API and webapp unavailable 12h

Started Apr 29, 2026, 12:30 AM UTC· resolved Apr 29, 2026, 12:30 PM UTC

  1. 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 1d 1h API V2

Started Apr 28, 2026, 02:39 PM UTC· resolved Apr 29, 2026, 04:06 PM UTC

  1. 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.

  2. identified Apr 28, 2026, 02:39 PM UTC

    We are continuing to work on a fix for this issue.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. identified Apr 29, 2026, 12:28 PM UTC

    Minor interruptions have to be expected during the incoming deployment of our fix.

  8. 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.

  9. resolved Apr 29, 2026, 04:06 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 19, 2026 SFTP unreachable for password-based users –

Started Mar 19, 2026, 07:30 PM UTC· resolved Mar 19, 2026, 07:30 PM UTC

  1. 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 →

Minor August 1, 2025 Analytics dashboard data not refreshing 2d 19h Analytics

Started Aug 01, 2025, 12:49 PM UTC· resolved Aug 04, 2025, 08:25 AM UTC

  1. identified Aug 01, 2025, 12:49 PM UTC

    Power BI is facing multiple incidents since a few days, that are impacting the data freshness on our analytics dashboards. We are closely monitoring the evolution of these incidents, and will update you as soon as they are resolved.

  2. resolved Aug 04, 2025, 08:25 AM UTC

    The incident was resolved on Microsoft side this morning, August 4th at 6:40 AM UTC+2. All our analytics dashboards are currently being refreshed, you should expect them to be up-to-date soon enough.

Read the full incident report →

Critical November 7, 2024 Flat File Integration Outage 22h 44m Flat file integration

Started Nov 07, 2024, 06:09 PM UTC· resolved Nov 08, 2024, 04:53 PM UTC

  1. identified Nov 07, 2024, 06:09 PM UTC

    Following today's maintenance of our Flat file integration infrastructure our system is currently down. We are working actively to restore it and we expect to be back online by 08/11 EOD. We are really sorry for the inconvenience this issue is causing and we remain at your disposal.

  2. resolved Nov 08, 2024, 04:53 PM UTC

    This incident has been resolved.

Read the full incident report →