Previous incidents

Our provider is blocking outgoing E-Mails towards Microsoft domains.

https://status.scaleway.com/incidents/vyc7z0zdp42y

dal1-1.edge.pbs-host.de recovered.

ham1-ingress.pbs-host.de - Instance 1, ham1-ingress.pbs-host.de - Instance 2, ham1-1.pbs-host.de, and 1 other resource recovered.

internet routes divered and are all synced now

remote-backups.com recovered.

We are resolving this incident for now. A post-incident report will be posted on the blog later today.

We see that the queue is draining slowly but the underlying issue seems to be resolved. We will think about how we can avoid issues like this in the future and act faster to not impact customer logins. Thanks for understanding.

fra1-4.pbs-host.de recovered.

API recovered.

All services are back up and recovered.

bhs1-1.edge.pbs-host.de recovered.

sao1-1.edge.pbs-host.de recovered.

remote-backups.com recovered.

Services are healthy again and we are monitoring recovery

sao1-1.edge.pbs-host.de recovered.

fra1-1.pbs-host.de recovered.

sao1-1.edge.pbs-host.de recovered.

rtr1 is fully back up and running.

hil1-1.edge.pbs-host.de recovered.

remote-backups.com, Dashboard, and API recovered.

syd1-1.edge.pbs-host.de recovered.

dus1-2.pbs-host.de recovered.

Server is up again. Incident closed.

Service are backup and recovered.

Routes changed, incident resolved

dus1-1.pbs-host.de recovered.

mum1-1.edge.pbs-host.de recovered.

mum1-1.edge.pbs-host.de recovered.

dus1-2.pbs-host.de recovered.

The issue was resolved. It was a 500 Million Packets per Second DDoS attack clogging the uplink streams on our providers network.

Server is up again, the issue was memory error which caused the server to hang.

The timing with the on-site technicial is a unlucky coincidence. He pulled our remote management port which made us unable to hard-reset the server at the time. We have communicated that this is not acceptable.

Thanks for your patience.

Confirmed resolved. A BGP routing issue not with our provider but further upstream.