GraphQL Hive Outage History

GraphQL Hive is up right now

Pingoru has recorded 13 incidents for GraphQL Hive: 9 in the last 12 months and 3 in the last 90 days.

Source: status.graphql-hive.com

13incidents recorded
9last 12 months
3last 90 days
39 minutestypical duration
Incidents per month
012AprMayJunJulAugSepOct1
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct0%
Pingoru began tracking GraphQL Hive 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 202620 of 720 (0%)
May 202610 of 744 (0%)
June 202600 of 720 (0%)
July 202600 of 744 (0%)
August 202625 of 744 (1%)
September 202600 of 720 (0%)
October 202611 of 513 (0%)

Incidents, newest first

Major October 20, 2026 Brief outage possible due to database scaling 33m APIs (GraphQL API (Registry))

Started Oct 20, 2026, 08:35 PM UTC· resolved Oct 20, 2026, 09:09 PM UTC

  1. investigating Oct 20, 2026, 08:35 PM UTC

    We are scaling up our database to accommodate increased load and improve overall performance. During the scaling operation, some services may experience brief interruptions or elevated error rates. We are monitoring the process and will provide an update once the scaling operation is complete.

  2. resolved Oct 20, 2026, 09:09 PM UTC

    The database was scaled successfully.

Read the full incident report →

Minor August 31, 2026 Degraded performance for schema publishes and app deployment publishes 3h 59m APIs (GraphQL API (Registry)), APIs (HA CDN), APIs (GraphQL API (Registry)), APIs (HA CDN)

Started Aug 31, 2026, 08:22 AM UTC· resolved Aug 31, 2026, 12:21 PM UTC

  1. investigating Aug 31, 2026, 08:22 AM UTC

    We are experiencing slow-downs and internal server errors due to our Cloudflare R2 bucket PUT operations being slow. We are in contact with the Cloudflare support team and are looking into solutions on why the bucket endpoint suddenly started degrading.

  2. resolved Aug 31, 2026, 12:21 PM UTC

    The error rates and latency from the affected Cloudflare R2 bucket has decreased and things are operational again. We are still monitoring the situation and are attempting to learn the root cause from the Cloudflare support.

Read the full incident report →

Major August 26, 2026 Usage reporting is down 41m APIs (Usage reporting), APIs (Usage reporting)

Started Aug 26, 2026, 01:38 PM UTC· resolved Aug 26, 2026, 02:19 PM UTC

  1. investigating Aug 26, 2026, 01:38 PM UTC

    Usage reporting went down.

  2. resolved Aug 26, 2026, 02:19 PM UTC

    Usage reporting recovered.

Read the full incident report →

Major May 22, 2026 GraphQL API (Registry) is down 1m APIs (GraphQL API (Registry)), APIs (GraphQL API (Registry))

Started May 22, 2026, 04:37 PM UTC· resolved May 22, 2026, 04:38 PM UTC

  1. investigating May 22, 2026, 04:37 PM UTC

    GraphQL API (Registry) went down.

  2. resolved May 22, 2026, 04:38 PM UTC

    GraphQL API (Registry) recovered.

Read the full incident report →

Major April 15, 2026 Some services are down 22m APIs (GraphQL API (Registry)), APIs (GraphQL API (Registry))

Started Apr 15, 2026, 04:16 PM UTC· resolved Apr 15, 2026, 04:39 PM UTC

  1. investigating Apr 15, 2026, 04:16 PM UTC

    GraphQL API (Registry) went down.

  2. resolved Apr 15, 2026, 04:39 PM UTC

    Root cause has been identified: our database provider performed an unscheduled platform update without prior notice, which temporarily disrupted database connectivity for the GraphQL API (Registry). The incident is now resolved.

Read the full incident report →

Major April 4, 2026 Tokens is down 4m Internal (Tokens)

Started Apr 04, 2026, 05:32 PM UTC· resolved Apr 04, 2026, 05:36 PM UTC

  1. investigating Apr 04, 2026, 05:32 PM UTC

    Tokens went down.

Read the full incident report →

Major January 13, 2026 Webhooks is down 7m Internal (Webhooks), Internal (Webhooks)

Started Jan 13, 2026, 09:31 AM UTC· resolved Jan 13, 2026, 09:38 AM UTC

  1. investigating Jan 13, 2026, 09:31 AM UTC

    Webhooks went down.

  2. resolved Jan 13, 2026, 09:38 AM UTC

    Webhooks recovered.

Read the full incident report →

Major December 19, 2025 Dashboard and GraphQL API (Registry) are down 3m Web (Dashboard), APIs (GraphQL API (Registry)), Web (Dashboard), APIs (GraphQL API (Registry))

Started Dec 19, 2025, 12:08 PM UTC· resolved Dec 19, 2025, 12:11 PM UTC

  1. investigating Dec 19, 2025, 12:08 PM UTC

    Dashboard went down.

  2. resolved Dec 19, 2025, 12:11 PM UTC

    Dashboard and GraphQL API (Registry) recovered.

Read the full incident report →

Minor November 18, 2025 Cloudflare Global Network experiencing issues – Web (Dashboard), APIs (GraphQL API (Registry)), APIs (Usage reporting), APIs (HA CDN) and 4 more

Started Nov 18, 2025, 12:12 PM UTC· resolved Nov 18, 2025, 12:12 PM UTC

  1. resolved Nov 18, 2025, 12:12 PM UTC

    https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

Read the full incident report →

Major September 20, 2025 Dashboard is down 38s Web (Dashboard)

Started Sep 20, 2025, 01:39 PM UTC· resolved Sep 20, 2025, 01:39 PM UTC

  1. investigating Sep 20, 2025, 01:39 PM UTC

    Dashboard went down.

  2. resolved Sep 20, 2025, 01:39 PM UTC

    Dashboard recovered.

Read the full incident report →

Major September 4, 2025 Dashboard, Usage reporting, and 1 other service are down 52m Web (Dashboard), APIs (Usage reporting), Internal (Usage reports processing)

Started Sep 04, 2025, 03:11 PM UTC· resolved Sep 04, 2025, 04:04 PM UTC

  1. investigating Sep 04, 2025, 03:11 PM UTC

    Usage reports processing went down.

  2. resolved Sep 04, 2025, 04:04 PM UTC

    Usage reporting recovered.

Read the full incident report →

Minor September 4, 2025 Intermittent network issues 1h 37m Web (Dashboard), APIs (GraphQL API (Registry)), APIs (Usage reporting), Internal (Usage reports processing)

Started Sep 04, 2025, 03:11 PM UTC· resolved Sep 04, 2025, 04:48 PM UTC

  1. investigating Sep 04, 2025, 03:11 PM UTC

    Investigating network issues in cluster.

  2. resolved Sep 04, 2025, 04:48 PM UTC

    We have identified the root cause and are actively working on improvements to mitigate it in the future.

Read the full incident report →