Is Scaleway down?

Last checked 1m ago
Current status
Scaleway has degraded performance

9 active incidents: [WEBHOSTING] - PF-13 issue, [Generative APIs] - GLM-5.3 model unavailability · +7 more

Scaleway is reporting degraded performance right now (last checked 1m ago). Services are up but slower or partially failing.

Real-time Scaleway status, recent outages, and incident history: pulled directly from Scaleway's official status page at status.scaleway.com every 5 minutes. Pingoru tracks 74 Scaleway services and has captured 164 incidents in the last 90 days (97.00% uptime). Get email, Slack, Discord, or webhook alerts the moment Scaleway reports a new incident, free for 3 monitors, no credit card.

Users who monitor Scaleway also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 8,000+ providers
Scaleway uptime 97.00% uptime · past 90 days
Mon Wed Fri
JulAugSepOct
Less More

Active incidents 8

  1. Ongoing ● 9h 29m
    Started Oct 28, 2026, 06:39 PM UTC
    Web Hosting
    Timeline · 1 update
    • investigating · Oct 28, 2026, 06:39 PM UTC

      Customers on pf-13 may currently experience database connection issues. As a result, CMS applications like WordPress might be unavailable and display database connection errors. Our team is now investigating.

    Latest: Customers on pf-13 may currently experience database connection issues. As a result, CMS applications like WordPress might be unavailable and display database connection errors. Ou…

  2. Ongoing ● 1d 17h
    Started Oct 27, 2026, 11:03 AM UTC
    Generative API
    Timeline · 1 update
    • investigating · Oct 27, 2026, 11:03 AM UTC

      [10:06] Requests on model had experienced elevated timeouts. [10:15] Model has been unavailable [10:50] Fix has been applied

    Latest: [10:06] Requests on model had experienced elevated timeouts. [10:15] Model has been unavailable [10:50] Fix has been applied

  3. Ongoing ● 2d 10h
    Started Oct 26, 2026, 05:34 PM UTC
    Generative API
    Timeline · 1 update
    • monitoring · Oct 26, 2026, 05:34 PM UTC

      Some requests to the deepseek-v4-flash and deepseek-v4.1-flash models had experienced elevated timeouts. The error rates are improving. We're monitoring the situation.

    Latest: Some requests to the deepseek-v4-flash and deepseek-v4.1-flash models had experienced elevated timeouts. The error rates are improving. We're monitoring the situation.

  4. Ongoing ● 2d 19h
    Started Oct 26, 2026, 08:45 AM UTC
    Excellence
    Timeline · 3 updates
    • investigating · Oct 26, 2026, 08:45 AM UTC

      En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests as quickly as possible. Thank you for your patience and understanding.

    • identified · Oct 26, 2026, 08:54 AM UTC

      En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests as quickly as possible. Thank you for your patience and understanding.

    • identified · Oct 26, 2026, 08:55 AM UTC

      En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afin de rétablir la situation et de traiter les demandes dans les meilleurs délais. Nous vous remercions pour votre patience et votre compréhension. Due to a high volume of requests, the processing of ongoing tickets may take longer than usual. Our teams are fully mobilized to restore normal service and handle requests as quickly as possible. Thank you for your patience and understanding.

    Latest: En raison d’un volume exceptionnellement élevé de demandes, le traitement des tickets en cours peut prendre plus de temps que d’habitude. Nos équipes sont pleinement mobilisées afi…

  5. Ongoing ● 2d 19h
    Started Oct 26, 2026, 08:44 AM UTC
    Excellence
    Timeline · 2 updates
    • investigating · Oct 26, 2026, 08:44 AM UTC

      Due to a high volume of requests, it may be difficult to reach our teams by phone. If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible. Thank you for your understanding. En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone. Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais. Merci de votre compréhension.

    • identified · Oct 26, 2026, 08:56 AM UTC

      Due to a high volume of requests, it may be difficult to reach our teams by phone. If needed, we invite you to contact us directly by submitting a ticket so that your request can be processed as quickly as possible. Thank you for your understanding. En raison d’un nombre élevé de demandes, il peut être difficile de joindre nos équipes par téléphone. Au besoin, nous vous invitons à nous contacter directement par ticket afin que votre demande soit prise en charge dans les meilleurs délais. Merci de votre compréhension.

    Latest: Due to a high volume of requests, it may be difficult to reach our teams by phone. If needed, we invite you to contact us directly by submitting a ticket so that your request can b…

+3 more ongoing incidents: sign up free to track them all.

Recent outages & incidents

Past 90 days
  1. Resolved 57s
    Started Oct 27, 2026, 04:32 PM UTC · Resolved Oct 27, 2026, 04:33 PM UTC
    nl-ams-1nl-ams-2nl-ams-3Databases
    Timeline · 3 updates
    • investigating · Oct 27, 2026, 04:32 PM UTC

      Since 14:51 UTC, new RDB instance can't be provisioning in AMS

    • investigating · Oct 27, 2026, 04:33 PM UTC

      We are continuing to investigate this issue.

    • resolved · Oct 27, 2026, 04:33 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  2. Resolved 3m
    Started Oct 27, 2026, 02:23 PM UTC · Resolved Oct 27, 2026, 02:27 PM UTC
    Serverless Container
    Timeline · 2 updates
    • investigating · Oct 27, 2026, 02:23 PM UTC

      [12:00] Serverless Container creation is currently unavailable in it-mil due to communication issues within the Kubernetes cluster.

    • resolved · Oct 27, 2026, 02:27 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  3. Resolved 2d 4h
    Started Oct 26, 2026, 12:18 PM UTC · Resolved Oct 28, 2026, 05:07 PM UTC
    Kubernetes Kapsule
    Timeline · 2 updates
    • investigating · Oct 26, 2026, 12:18 PM UTC

      2026-10-26 11:40:37 GMT+1: a new image was released for Kapsule nodes, unfortunately the release seems to be only partial and some regions might not have the right image id. This may cause nodes to be unable to spawn.

    • resolved · Oct 28, 2026, 05:07 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  4. Resolved –
    Started Oct 26, 2026, 08:48 AM UTC · Resolved Oct 26, 2026, 08:48 AM UTC
    Generative API
    Timeline · 1 update
    • resolved · Oct 26, 2026, 08:48 AM UTC

      Some requests to the deepseek-v4.1-flash model had experienced elevated timeouts. The situation has been resolved.

    Latest: Some requests to the deepseek-v4.1-flash model had experienced elevated timeouts. The situation has been resolved.

  5. Resolved 3d 20h
    Started Oct 23, 2026, 02:24 PM UTC · Resolved Oct 27, 2026, 10:36 AM UTC
    BookMyName
    Timeline · 2 updates
    • identified · Oct 23, 2026, 02:24 PM UTC

      On 2026-10-21, a critical PHP RCE (CVE-2026-109618/109619, CVSS 9.2) forced an emergency migration of the BookMyName fleet off EOL PHP branches (5.6/7.4/8.1) to PHP 8.2.35. The migration introduced PHP 8 compatibility regressions in legacy code, impacting customers since 2026-10-21.

    • resolved · Oct 27, 2026, 10:36 AM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

See the full Scaleway outage history

130 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Scaleway outage history →

Or sign up free to get alerts when Scaleway breaks · 10 free monitors · No credit card

Incident record

Since April 2026 · Statuspage by Atlassian · 74 components checked every 5 minutes
372incidents recorded
371last 12 months
135last 90 days
3 daystypical duration, 12 months

The longest incident in the last year, [WEBHOSTING] SMTP/51.159.208.135 blacklisted on Microsoft/Outlook from classic webhosting service on November 24, 2025, ran for 200 days. 63 maintenance windows announced in the same period.

Most affected components, last 12 months

  • fr-par-235
  • Generative API32
  • fr-par-132
  • Dedibox28
  • fr-par-326

Latest incidents

Outage history

Past 90 days · 135 incidents View full outage history →