Is MotherDuck down?
Last checked 13m agoNo incidents right now.
MotherDuck is operational right now. Last checked 13m ago; the most recent incident resolved 37d ago.
Real-time MotherDuck status, recent outages, and incident history: pulled directly from MotherDuck's official status page at status.motherduck.com every 5 minutes. Pingoru tracks 4 MotherDuck services and has captured 3 incidents in the last 90 days (98.89% uptime). Get email, Slack, Discord, or webhook alerts the moment MotherDuck reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- MotherDuck App
Timeline · 3 updates
- investigating · Sep 24, 2026, 11:29 AM UTC
Our team has observed elevated error rates since September 24, 0920 UTC. We are actively investigating and will provide an update shortly.
- investigating · Sep 24, 2026, 11:54 AM UTC
We've released a fix and are now seeing a recovery in the errors coming from the us-east-1 region. We're actively monitoring the situation and will provide more updates.
- resolved · Sep 24, 2026, 12:25 PM UTC
The services in us-east-1 have recovered and resumed normal operation.
Latest: The services in us-east-1 have recovered and resumed normal operation.
-
- 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.
-
- 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…
-
Incident record
Since April 2026 · PagerDuty · 4 components checked every 5 minutesThe longest incident in the last year, Degraded experience using Dives on May 1, 2026, ran for 17 hours. 1 maintenance window announced in the same period.
Most affected components, last 12 months
- MotherDuck App21
Latest incidents
- Elevated errors in the us-east-1 region
<p>Our team has observed elevated error rates since September 24, 0920 UTC. </p> <p>We are actively investigating and will provide an update shortly.</p>
- Partial outage of MotherDuck's UI
<p>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.</p>
- Degraded Database Attach Times in eu-central-1
<p>We are investigating degraded database and share attach times in eu-central-1 region. Our team is investigating the issue with high priority! </p>
- Started Sep 24, 2026, 11:29 AM UTC · Resolved Sep 24, 2026, 12:25 PM UTC · 55m
- Partial outage of MotherDuck's UI ResolvedStarted Aug 27, 2026, 10:37 AM UTC · Resolved Aug 27, 2026, 11:35 AM UTC · 58m
- Started Aug 26, 2026, 08:02 AM UTC · Resolved Aug 26, 2026, 12:53 PM UTC · 4h 51m