DownForAI

Predibase Incident History

5 major incidents detected for Predibase. View live status dashboard →

MajorOngoing

Predibase

On 2026-05-04 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Predibase. The incident is currently being investigated. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 4, 2026, 03:18 UTCDuration: ongoingView service →
MajorResolved

Predibase

On 2026-05-01 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Predibase. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: May 1, 2026, 03:12 UTCResolved: May 4, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Predibase

On 2026-04-28 at 03:18 UTC, DownForAI monitoring detected a significant service issue affecting Predibase. The incident has been resolved after approximately 71h 42m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 28, 2026, 03:18 UTCResolved: May 1, 2026, 03:00 UTCDuration: 71h 42mView service →
MajorResolved

Predibase

On 2026-04-25 at 03:12 UTC, DownForAI monitoring detected a significant service issue affecting Predibase. The incident has been resolved after approximately 71h 48m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 25, 2026, 03:12 UTCResolved: Apr 28, 2026, 03:00 UTCDuration: 71h 48mView service →
MajorResolved

Predibase

On 2026-04-22 at 15:18 UTC, DownForAI monitoring detected a significant service issue affecting Predibase. The incident has been resolved after approximately 59h 42m. This incident was detected by our automated probes running every 2-5 minutes from multiple locations.

Started: Apr 22, 2026, 15:18 UTCResolved: Apr 25, 2026, 03:00 UTCDuration: 59h 42mView service →
← Back to all incidents