Is Scaleway Down? Live status & outage reports

Service info and troubleshooting

Instance fails to boot after restart

Check the console logs through the web interface to identify boot errors. Most often, this happens due to incorrect fstab entries or filesystem corruption. Boot into rescue mode from the instance settings, mount your root partition, and verify the /etc/fstab file. Remove or comment out any problematic mount points. Run fsck to check filesystem integrity before rebooting.

API returns 429 rate limit errors

Scaleway enforces strict API rate limits per project and token. If your scripts or automation tools hit these limits, implement exponential backoff in your requests. Space out API calls by adding delays between operations. For high-volume workflows, consider requesting a rate limit increase through support or splitting tasks across multiple projects.

Object Storage bucket access denied

• Verify your API key has the correct permissions for Object Storage operations
• Check bucket policies and ACL settings in the console
• Ensure the bucket region matches your API endpoint
• Confirm your IP isn't blocked by any bucket restrictions
• Regenerate credentials if they were recently rotated

SSH connection timeout to instances

Security groups might be blocking port 22. Go to instance settings and verify the default security group allows inbound TCP traffic on port 22 from your IP. If you're connecting from a dynamic IP, you may need to update the rules. Also check that the instance isn't overloaded - high CPU usage can delay SSH responses.

Database backup restore failing

Timeout errors during restore usually mean the backup file is too large for the current instance specs. Upgrade to a higher-tier database instance temporarily, perform the restore, then downgrade if needed. Alternatively, use the CLI tools for restore operations as they handle large datasets better than the web console.

Load balancer health checks failing

Your backend servers must respond correctly to health check requests. Review the health check path and expected status codes in load balancer settings. Enable detailed health check logs to see exact response codes from backends. Ensure your application returns responses within the configured timeout period, typically 5 seconds.