Vendor Status Watch

← all vendors

OneSchema status history

Current state: operational — “All Systems Operational” per https://status.oneschema.co (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
2incidents, last 90 days
6incidents on record
Incidents per week, last 12 weeks:

How long do OneSchema incidents last?

20 minmedian incident duration6 measured
69 min90th percentile1 in 10 ran longer
23 minmedian, major/critical only3 incidents

From 6 incidents with a vendor-posted start and resolve time. Longest on record: Partial service degradation of the US servers — 10.6 h (2025-09-29 16:04 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (6)

StartedIncidentStatusImpactDuration
2026-07-28 19:21 UTCPartial outage in US Serversresolvednone1 h 09 min
2026-07-17 21:05 UTCFile storage service outage in USresolvedmajor23 min
2026-05-05 00:30 UTCImports failing to submit in US Productionresolvedmajor0 min
2026-02-10 17:40 UTCPartial Outage on US Serverresolvednone0 min
2026-01-12 20:05 UTCPartial service degradation of the US serversresolvedminor17 min
2025-09-29 16:04 UTCPartial service degradation of the US serversresolvedmajor10 h 35 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch OneSchema with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "oneschema"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}