H2O AI Outage History

H2O AI is up right now

Pingoru has recorded 2 incidents for H2O AI: 0 in the last 12 months and 0 in the last 90 days.

Source: status.cloud.h2o.ai

2incidents recorded
0last 12 months
0last 90 days
–typical duration
Incidents per month
012AprMayJunJulAugSepOct0
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking H2O AI in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 202600 of 720 (0%)
May 202600 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202600 of 744 (0%)
September 202600 of 720 (0%)
October 202600 of 526 (0%)

Incidents, newest first

Major October 20, 2025 Service Disruption Due to AWS us-east-1 Regional Outage –

Started Oct 20, 2025, 09:00 PM UTC· resolved Oct 20, 2025, 09:00 PM UTC

  1. resolved Feb 13, 2026, 10:09 AM UTC

    We are experiencing a service disruption due to an ongoing AWS outage in the us-east-1 region. This issue is affecting components and workloads hosted in that region, resulting in degraded performance and partial unavailability for some users.

Read the full incident report →

Major July 28, 2025 Model scoring endpoints are currently unavailable –

Started Jul 28, 2025, 06:30 PM UTC· resolved Jul 28, 2025, 06:30 PM UTC

  1. resolved Feb 13, 2026, 10:12 AM UTC

    We are currently experiencing a service disruption affecting MLOps model deployments in our Managed Cloud environment, where your model endpoints may be returning errors or appearing unreachable. Model scoring endpoints are currently unavailable across all deployments, but our engineering teams have identified the root cause and are implementing fixes across all customer environments. We are working around the clock to restore full service and applying targeted fixes to restore your model endpoints. Some deployments may already be restored, while others are still being addressed. Please avoid redeploying models during this time, as it may complicate recovery efforts. We will notify you immediately when your specific environment is fully restored. We sincerely apologize for this disruption and understand the critical nature of these services to your operations. Restoring your MLOps capabilities is our highest priority. For urgent inquiries, please contact our support team at [email protected].

Read the full incident report →