For anyone wanting a quick workaround, try removing all the backend of your load balancer then add them again.
No idea why but it did work for us.
They are currently rolling out a change that should completely fix the issue and somewhere else I read they are rolling back a config change they did recently..
At 15:10 UTC, we duplicated one Kubernetes Service in a new one. Since, we have no alerts.
Coincidence ?