MotherDuck Outage History

MotherDuck experienced elevated attach failures that prevented users from connecting to their database instances. The issue was identified and service was restored by restarting the affected database processes (ducklings), with full resolution achieved within 1 hour.

MotherDuck experienced degraded database load times in their EU region for 4.1 hours. The team deployed a fix that improved performance and continued monitoring the situation. The incident was classified as major, indicating significant impact on EU region users' database operations.

MotherDuck experienced a degraded experience with their Dives feature for 16.4 hours. The incident was classified as minor with no additional details provided about the specific nature of the degradation or affected functionality. The service has since been restored to normal operation.

MotherDuck databases in the us-east-1 region became unavailable due to a service incident. The outage affected database access and operations for users in that region. The root cause was identified and a fix was implemented, resolving the issue after 36 minutes.