Qovery - Notice history

All systems operational

99.99% uptime

Console - Operational

100.0% uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Api - Operational

100.0% uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Environment deployment - Operational

100.0% uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Infrastructure deployment - Operational

100.0% uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Emails - Operational

100.0% uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Customer infratructure - Operational

99.96% uptime
Aug 2024 · 99.89%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024

Terraform provider - Operational

100.0% uptime
Aug 2024 · 100.0%Sep · 100.0%Oct · 100.0%

Previous page

Next page

Aug 2024
Sep 2024
Oct 2024
100.0% uptime

Third Party: Scaleway → Elements - Products → Elastic Metal - Degraded performance

Third Party: Scaleway → Elements - Products → Kapsule - Operational

Third Party: Scaleway → Elements - Products → LBaaS - Operational

Third Party: Scaleway → Elements - Products → Object Storage - Operational

Third Party: Scaleway → Elements - Products → Container Registry - Operational

Third Party: Scaleway → Elements - Products → Block Storage - Operational

Third Party: Scaleway → Elements - AZ → fr-par-1 - Operational

Third Party: Scaleway → Elements - AZ → fr-par-2 - Operational

Third Party: Scaleway → Elements - AZ → fr-par-3 - Operational

Third Party: Scaleway → Elements - AZ → nl-ams-1 - Operational

Third Party: Scaleway → Elements - AZ → nl-ams-2 - Operational

Third Party: Scaleway → Elements - AZ → pl-waw-1 - Operational

Notice history

View current status

Oct 2024

Deployment Timeout
ResolvedPartial outage
  • ResolvedUTC

    Most deployment failed with timeout.

    This incident has been resolved.

Sep 2024

SEP16
Standard Non-production cluster Update
CompletedMaintenance4 hours
  • CompletedSeptember 16, 2024 at 12:00 PMUTC
    Maintenance has completed successfully
  • UpdateSeptember 16, 2024 at 8:00 AMUTC

    Update - September 12, 2024

    The scheduled update for non-production clusters did not take place today due to issues with our ARM image. To avoid any potential risks, we have decided to postpone the update. The issue has since been resolved, and we have rescheduled the maintenance to September 16, 2024 at 8:00 AM UTC.

    The update will be applied to your production clusters on September 19, 2024, at 8:00 AM UTC. However, if you choose to manually update your production cluster in Qovery before this date, the update will be automatically applied.

  • PlannedSeptember 16, 2024 at 8:00 AMUTC

    Cluster Updates on September 16, 2024, at 8:00 AM UTC
    Please be aware that updates will be applied to your non-production clusters, and actions may be required in the future.

    Key changes:

    • Cert-manager update: Read more

    • NGINX Ingress name update: Read more

    • ALB controller flag will be enabled for non-production clusters only: Read more

    The update will be applied to your production clusters on September 19, 2024, at 8:00 AM UTC. However, if you choose to manually update your production cluster in Qovery before this date, the update will be automatically applied.

Aug 2024

403 received Nginx customer side
ResolvedPartial outage2 hours 40 minutes
  • UpdateUTC

    Following a global cluster update triggered by our team, some configuration of the Nginx Ingress controller was wrongly modified on a subset of these clusters.

    Our team identified the root cause of the problem and deployed a fix on all clusters.

    The websites hosted on impacted clusters were unreachable during the outage.

    You can find more information on this forum thread

    We apologize for any inconvenience caused.

  • ResolvedUTC

    Our team has identified the root cause of this issue; however, further investigation is required, as the bug appears to have impacted configurations that should have remained unaffected. We are actively working to fully understand the scope and prevent any recurrence.

    We apologize for any inconvenience caused and appreciate your patience as we work to investigate this matter promptly.

  • IdentifiedUTC

    We want to inform you of a recent incident involving customers' Nginx configuration that affected some customers. Specifically, a conflicting setting was released that impacted customers with IP whitelists configured on their services, resulting in their requests being denied with an HTTP 403 error.

    Investigation is in progress

Previous

Aug 2024 to Oct 2024

Next