Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    1. Home
    2. Services
    3. Qovery

    Last checked Oct 26, 11:02 PM UTC

    Qovery status

    DevOps automation platform for self-service cloud infrastructure provisioning.

    Experiencing an issue?

    Qovery logo

    Is Qovery down?

    Degraded performance

    Having issues with Qovery?

    Share your experience to help others stay informed.

    Current statusHealth graphOutage reportsOutage mapSocial signalsStatus historyComponentsIncident historyCommunityReviewsAboutFAQsMonitor serviceSimilar servicesComparison

    Latest activity

    Last 24 hours
    1. Official status checked

      Qovery is experiencing issues

      Official provider status
      Oct 26, 11:02 PM UTC

    Qovery outage reports

    0 individual report entries in the last 24 hours. This list includes legacy imports; external source aggregates are shown in the chart.

    No recent outage reports

    No community outage reports have been submitted for this service in the last 24 hours.

    Get notified about Qovery outages

    Monitor Qovery with Uptimus and get alerts when its status changes.

    Start monitoring for free

    Qovery outage map

    Approved reports from the last 24 hours, grouped by country. Markers show country-level locations, not precise locations or confirmed affected infrastructure.
    View full map

    Qovery outage map

    Loading report locations…

    Qovery status history

    Official status observations, not measured service uptime.

    Qovery components

    Component nameStatus
    Qovery — Emails statusUp
    Qovery Customer infrastructure: AWS — Third Party: Amazon Web Services (AWS) → AWS ec2-us-east-2 statusUp
    Qovery Third Party: Authentication — Third Party: Auth0 → Europe (PROD) → Auth0 User Authentication statusUp
    Qovery Third party: Git Providers — Third Party: BitBucket -> Webhooks statusUp
    Qovery Third Party: Domain and Certificates management — Third Party: Cloudflare → Cloudflare Sites and Services → Authoritative DNS statusUp
    Qovery Customer infrastructure: GCP — Third Party: Google Cloud Platform → Google Compute Engine statusUp
    Qovery Customer infrastructure: Scaleway — Third Party: Scaleway → Elements - AZ → fr-par-2 statusUp
    Qovery — Api statusUp
    Qovery Customer infrastructure: AWS — Third Party: Amazon Web Services (AWS) → AWS ec2-ap-northeast-1 statusUp
    Qovery Third Party: Authentication — Third Party: Auth0 → Europe (PROD) → Auth0 Machine to Machine Authentication statusUp

    Qovery incident history

    Official incidents, early warnings and community reports are identified separately. Early warning history covers only the last 24 hours. Dates use your time zone.

    View more history
    Incident nameDurationStartedUTCAcknowledgedSeverity
    Official status·Resolved1h 45mOct 8, 202610:50 AM UTCYesCritical
    Official status·Resolved32mOct 8, 20269:10 AM UTCYesCritical
    Official status·Resolved18mOct 8, 20268:30 AM UTCYesCritical

    About Qovery monitoring on Uptimus

    Uptimus monitors Qovery through its official status source and normalizes published incidents, maintenance windows and component health into one consistent service status.

    This page currently includes 81 monitored components, 3 indexed incidents, 0 maintenance windows and 42 days of known history.

    Uptimus is an independent monitoring service and is not affiliated with Qovery. A healthy status does not guarantee that every user, device or region is unaffected.

    How Uptimus monitors Qovery

    Get notified when Qovery or one of its monitored components reports a major outage or another critical service disruption. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations. The available history contains 3 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Console unreachable and authentication issues through the CLI”.

    Get notified about degraded performance, partial impact and smaller incidents that do not represent a complete outage. Uptimus currently tracks 81 Qovery components: Emails, Third Party: Amazon Web Services (AWS) → AWS ec2-us-east-2, Third Party: Auth0 → Europe (PROD) → Auth0 User Authentication, Third Party: BitBucket -> Webhooks. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.

    Maintenance notifications
    Receive alerts when Qovery publishes planned, scheduled or active maintenance affecting the service. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
    Recovery notifications
    Know when Qovery or an affected component returns to healthy operation after an issue or outage. The current page contains 42 days of known status history, while resolved events remain available for later review. Alerts can be routed through the notification channels enabled for your workspace, including email, push and configured integrations.
    Status messages
    Uptimus stores the incident headline published by Qovery and presents it with the normalized service status. The available history contains 3 indexed incidents, giving each alert context beyond the current status. A recent indexed incident was “Console unreachable and authentication issues through the CLI”.
    Status details
    Incident and maintenance updates are preserved so you can follow investigations, mitigations and recovery progress. A recent official update preserved by Uptimus reads: “This incident has been resolved.”.
    Component status filtering
    Choose all components or only the Qovery products you use. Official alerts then respect that component selection. Uptimus currently tracks 81 Qovery components: Emails, Third Party: Amazon Web Services (AWS) → AWS ec2-us-east-2, Third Party: Auth0 → Europe (PROD) → Auth0 User Authentication, Third Party: BitBucket -> Webhooks. Filtering changes which official alerts are delivered; it does not remove the provider's events from the public history.

    Fair questions, straight answers.

    Be the first to know when Qovery goes down

    Start monitoring
    Similar services
    Comparison

    Uptimus vs Downdetector for Qovery

    Downdetector public pages are led by user reports. Uptimus combines community activity with official provider incidents, maintenance windows and component health when the source publishes them.

    Uptimus vs Downdetector for Qovery
    Comparison criteriaUptimusDowndetector
    Community outage reports for QoveryIncludedIncluded
    Adaptive baseline that separates isolated reports from wider disruptionIncludedIncluded
    24-hour report activity and regional outage viewIncludedIncluded
    One workspace for websites, provider status pages, Steam games and Android apps and gamesIncludedSeparate product
    Email, push and webhook alerts from the same workspaceIncludedSeparate product
    Official incident updates and status timeline for QoveryIncludedUser-report led
    Component health and maintenance windows kept separateIncludedLimited on public pages
    IncludedUser-report led · Limited on public pagesSeparate product

    The official status page for Qovery reports degraded performance. Components reported as affected: Customer infrastructure: Scaleway. 0 reports were recorded for Qovery in the last 24 hours. Last official check: Oct 26, 11:02 PM UTC.

    Community Discussion

    Share your thoughts about Qovery

    A
    No comments yet

    Be the first to comment!

    Rate this service

    How would you rate Qovery over the last month?

    No reviews yet

    (One review per month limit)

    More services to monitor

    Discover other popular services and their current status

    Browse all services
    Uber EatsBlendProject44ScoutPoll EverywhereRescuetimeSimply Hosting undefined ServersTsysPackback