OneSchema Outage History

OneSchema is up right now

OneSchema had 4 outages in the last 2 years totaling 2h 18m of downtime — averaging 0.2 incidents per month.

There were 4 OneSchema outages since July 15, 2025 totaling 2h 18m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.oneschema.co

Notice February 10, 2026

Partial Outage on US Server

Detected by Pingoru
Feb 10, 2026, 06:49 PM UTC
Resolved
Feb 10, 2026, 05:40 PM UTC
Duration
Timeline · 1 update
  1. resolved Feb 10, 2026, 06:49 PM UTC

    We had a temporary outage of our web services that lasted about 5 minutes, starting at 9:40 am PT. All services are back online now and we're monitoring the situation.

Read the full incident report →

Minor January 12, 2026

Partial service degradation of the US servers

Detected by Pingoru
Jan 12, 2026, 08:05 PM UTC
Resolved
Jan 12, 2026, 08:23 PM UTC
Duration
17m
Affected: DashboardEmbeddable productsAPI
Timeline · 3 updates
  1. investigating Jan 12, 2026, 08:05 PM UTC

    We are currently experiencing instability and intermittent downtime on the US server.

  2. monitoring Jan 12, 2026, 08:09 PM UTC

    A fix has been implemented, and we are monitoring.

  3. resolved Jan 12, 2026, 08:23 PM UTC

    Service is stable, incident is resolved.

Read the full incident report →

Major July 15, 2025

Partial outage on US server

Detected by Pingoru
Jul 15, 2025, 04:28 PM UTC
Resolved
Jul 15, 2025, 06:29 PM UTC
Duration
2h
Affected: DashboardEmbeddable productsAPI
Timeline · 4 updates
  1. investigating Jul 15, 2025, 04:28 PM UTC

    We are currently investigating this issue.

  2. identified Jul 15, 2025, 04:54 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Jul 15, 2025, 05:43 PM UTC

    OneSchema has experienced an intermittent partial outage on the US server. Total downtime was 15 minutes spread over 4 hours from 6:30 am PT to 10:30 am PT. A fix has been implemented and we are monitoring the results.

  4. resolved Jul 15, 2025, 06:29 PM UTC

    This incident has been resolved.

Read the full incident report →