Resolved -
This incident has been resolved.
Jul 24, 20:30 CEST
Update -
We are operational but will keep monitoring our services throughout the evening.
Jul 24, 16:12 CEST
Monitoring -
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
Jul 24, 15:39 CEST
Investigating -
Follow-up issues created by the initial authentication backend issues is still causing partial outage for many of our systems. We are investigating.
Jul 24, 15:14 CEST
Update -
We are continuing to monitor for any further issues.
Jul 24, 14:51 CEST
Update -
We are continuing to monitor for any further issues.
Jul 24, 14:37 CEST
Monitoring -
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.
Jul 24, 14:22 CEST
Update -
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.
Jul 24, 09:38 CEST
Identified -
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
Jul 24, 08:23 CEST
Investigating -
We are experiencing issues with our authentication backend and are currently investigating the issue.
Jul 24, 07:36 CEST