Easee experienced a critical incident on July 24, 2025 affecting Easee Cloud & API and Easee App and 1 more component, lasting 12h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 24, 2025, 05:36 AM UTC
We are experiencing issues with our authentication backend and are currently investigating the issue.
- identified Jul 24, 2025, 06:23 AM UTC
We have identified some cache issues with our authentication backend and are trying to clear a cache that was filled up and restarting all the backend nodes to see if the improves the situation. We have applied a firewall block for the login endpoints and have now let the Easee Mobile apps and the Easee Portal bypass this block to verify the fix. Also verified partners should also be able to authenticate
- identified Jul 24, 2025, 07:38 AM UTC
We are investigating surge in traffic home automation systems originating from certain countries and are gradually allowing / disallowing traffic to try to narrow down specific clients that we have to permanently block.
- monitoring Jul 24, 2025, 12:22 PM UTC
We have detected a surge of API traffic originating from Switzerland using the user-agent "got (https://github.com/sindresorhus/got)". This client was using methods to bypass our API endpoint protections causing a surge in traffic on our login endpoints which in turn led to downtime / partial outage on our authentication backend. We have decided to block clients using the user-agent "got (https://github.com/sindresorhus/got)" until further notice. Easee reserves the right to protect its API endpoints from unwanted traffic.
- monitoring Jul 24, 2025, 12:37 PM UTC
We are continuing to monitor for any further issues.
- monitoring Jul 24, 2025, 12:51 PM UTC
We are continuing to monitor for any further issues.
- investigating Jul 24, 2025, 01:14 PM UTC
Follow-up issues created by the initial authentication backend issues is still causing partial outage for many of our systems. We are investigating.
- monitoring Jul 24, 2025, 01:39 PM UTC
We have identified issue with a service that experienced problems after the authentication backend was down. A fix has been implemented and we are monitoring the situation
- monitoring Jul 24, 2025, 02:12 PM UTC
We are operational but will keep monitoring our services throughout the evening.
- resolved Jul 24, 2025, 06:30 PM UTC
This incident has been resolved.