Is MotherDuck down?

Last checked 1m ago
Current status
MotherDuck is up

No incidents right now.

Official status page: https://status.motherduck.com/posts/dashboard · Polled every 5 minutes · 4 components tracked

MotherDuck is operational right now. Last checked 1m ago; the most recent incident resolved 19d ago.

Real-time MotherDuck status, recent outages, and incident history — pulled directly from MotherDuck's official status page at https://status.motherduck.com/posts/dashboard every 5 minutes. Pingoru tracks 4 MotherDuck services and has captured 5 incidents in the last 90 days (98.06% uptime). Get email, Slack, Discord, or webhook alerts the moment MotherDuck reports a new incident — free for 5 monitors, no credit card.

Users who monitor MotherDuck also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
MotherDuck uptime 98.06% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved 58m
    Started Aug 27, 2026, 10:37 AM UTC · Resolved Aug 27, 2026, 11:35 AM UTC
    MotherDuck App
    Timeline · 3 updates
    • identified · Aug 27, 2026, 10:37 AM UTC

      We are investigating reports that the MotherDuck UI is failing to authorize some customers. Other clients, like the DuckDB CLI or SDKs are not affected.

    • investigating · Aug 27, 2026, 11:06 AM UTC

      The issue has been mitigated and the UI seems to be authenticating users correctly now. We are actively monitoring the situation.

    • resolved · Aug 27, 2026, 11:35 AM UTC

      We addressed the issue and the UI is back to authenticating users correctly.

    Latest: We addressed the issue and the UI is back to authenticating users correctly.

  2. Resolved 4h 51m
    Started Aug 26, 2026, 08:02 AM UTC · Resolved Aug 26, 2026, 12:53 PM UTC
    MotherDuck App
    Timeline · 7 updates
    • investigating · Aug 26, 2026, 08:02 AM UTC

      We are investigating degraded database and share attach times in eu-central-1 region. Our team is investigating the issue with high priority!

    • investigating · Aug 26, 2026, 08:37 AM UTC

      We are continuing to investigate the degraded attach times in the eu-central-1 region. Our team has identified that some background jobs are putting unreasonable load on the system. These jobs have been paused and we are exploring potential fixes. Apologies for the impact!

    • investigating · Aug 26, 2026, 09:13 AM UTC

      We are continuing to investigate the degraded attach times in the eu-central-1 region. Our team has identified that some background jobs are putting unreasonable load on the system and these jobs have been paused. We are continuing to investigate the full impact of the issue and explore fixes....

    • investigating · Aug 26, 2026, 09:48 AM UTC

      Our team has identified the issue and are attempting potential fixes. Thank you for your patience as we continue to investigate and work towards a resolution!

    • investigating · Aug 26, 2026, 11:33 AM UTC

      Our team are continuing to work on implementing a work around and to reduce the load on our internal database, which causes the performance issues with attaches (both for MD databases and shares). We will post update here once the issue is resolved!

    • investigating · Aug 26, 2026, 12:14 PM UTC

      We have applied a fix and database and share attach times in eu-central-1 have returned to normal levels as of approximately 11:50 UTC. New connections should now establish normally, and any request that failed during the incident can be retried. We are monitoring closely before...

    • resolved · Aug 26, 2026, 12:53 PM UTC

      This incident is resolved. The fix was applied at approximately 11:50 UTC and database and share attach times in eu-central-1 have returned to normal levels. The degradation came from excessive load on an internal metadata service in the region, which slowed the step that opens a...

    Latest: This incident is resolved. The fix was applied at approximately 11:50 UTC and database and share attach times in eu-central-1 have returned to normal levels. The degradation came f…

  3. Resolved
    Started Jul 06, 2026, 01:00 PM UTC · Resolved Jul 06, 2026, 01:00 PM UTC
    MotherDuck App
    Timeline · 1 update
    • resolved · Jul 06, 2026, 01:00 PM UTC

      An AWS EC2 issue in us-east-1 during early morning of July 6 (PDT) impacted our ability to provision new compute. Some MotherDuck customers may have seen errors obtaining a duckling.  More information about the AWS EC2 issue is available at: https://health.aws.amazon.com/health/...

    Latest: An AWS EC2 issue in us-east-1 during early morning of July 6 (PDT) impacted our ability to provision new compute. Some MotherDuck customers may have seen errors obtaining a ducklin…

  4. Resolved 1h 25m
    Started Jun 25, 2026, 11:00 AM UTC · Resolved Jun 25, 2026, 12:25 PM UTC
    MotherDuck App
    Timeline · 5 updates
    • identified · Jun 24, 2026, 10:00 PM UTC

      At ~10:30 UTC, MotherDuck observed partial platform disruption via elevated error rates across all regions for Ducklings. We are actively investigating and will provide an update shortly.

    • identified · Jun 25, 2026, 11:00 AM UTC

      At ~10:30 UTC, MotherDuck observed partial platform disruption via elevated error rates across all regions for Ducklings. We are actively investigating and will provide an update shortly.

    • investigating · Jun 25, 2026, 11:51 AM UTC

      We are continuing to investigate the issue with the highest priority!

    • investigating · Jun 25, 2026, 12:20 PM UTC

      Our team has identified the root cause and are working on an implementation of the solution. More updates will follow shortly, we apologize for the disruption this is causing.

    • resolved · Jun 25, 2026, 12:25 PM UTC

      Our team has identified the root cause of the elevated error rates and has released a fix. We are currently in the process of rolling out this update. We are observing reduced error rates, and our systems are steadily returning to normal operation. We are monitoring the situation closely and will...

    Latest: Our team has identified the root cause of the elevated error rates and has released a fix. We are currently in the process of rolling out this update. We are observing reduced erro…

  5. Resolved
    Started Jun 24, 2026, 08:15 PM UTC · Resolved Jun 24, 2026, 08:15 PM UTC
    MotherDuck App
    Timeline · 2 updates
    • investigating · Jun 24, 2026, 07:25 PM UTC

      Flights in us-east-1 are not currently running due to a DNS issue. We're investigating a fix now.

    • resolved · Jun 24, 2026, 08:15 PM UTC

      The issue is resolved and all Flights in us-east-1 should be operational again.

    Latest: The issue is resolved and all Flights in us-east-1 should be operational again.

Outage history

Past 90 days · 5 incidents View full outage history →