Partial outage of MotherDuck's UI
We addressed the issue and the UI is back to authenticating users correctly.
The latest update from MotherDuck.
State
Resolved
Started
66 d ago
2026-08-27 10:37 UTC
Lasted
58 min
until 2026-08-27 11:35 UTC
Worst impact
Partial outage
Timeline
3 updatesDetected
30 min 51%
Investigating
28 min 49%
Updates
Times in UTCAs posted by MotherDuck
We addressed the issue and the UI is back to authenticating users correctly.
The issue has been mitigated and the UI seems to be authenticating users correctly now. We are actively monitoring the situation.
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.
Affected components
1MotherDuck in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
3
Median duration
58 min
This incident
About the median
Other MotherDuck incidents
All incidents
MotherDuck·Elevated errors in the us-east-1 region
The services in us-east-1 have recovered and resumed normal operation.
MotherDuck·Degraded Database Attach Times in eu-central-1
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...
Follow MotherDuck
Your coding agent knows when MotherDuck is down, and tells you when a failure is theirs, not yours. You can also get MotherDuck incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "motherduck" and tell me if MotherDuck has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=motherduck/feed subscribe https://outages.cc/feed.xml?providers=motherduckFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane