Vendor Status Watch

← all vendors

Hygraph status history

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

0incidents, last 30 days
2incidents, last 90 days
4incidents on record
Incidents per week, last 12 weeks:
Get Hygraph alerts in your Slack — free templateRSS for Hygraph

How long do Hygraph incidents last?

112 minmedian incident duration4 measured
3.7 h90th percentile1 in 10 ran longer
54 minmedian, major/critical only3 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Operational issue - Multiple services (N. Virginia) — 3.7 h (2025-10-20 07:59 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 (4)

StartedIncidentStatusImpactDuration
2026-08-07 11:38 UTCSign-ups temporarily unavailableresolvedmajor35 min
2026-06-26 07:25 UTCLogin Failuresresolvedmajor54 min
2025-11-18 11:57 UTCAPI endpoints effected by Cloudflare outageresolvedminor2 h 50 min
2025-10-20 07:59 UTCOperational issue - Multiple services (N. Virginia)resolvedcritical3 h 44 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 Hygraph with the template

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

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