Is Hasura Down?

No — Hasura is up

Hasura's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 116 ms

Right now

The verdict is the worse of these two. How we decide

Hasura's status page

hasura-status.com · read 3 minutes ago · checked every 3 minutes

Operational

Hasura's components, as its status page reports them
Component	Status
PromptQL Control Plane	Operational
PromptQL Playground	Operational
PromptQL API	Operational
Observability & Monitoring	Operational
Hasura DDN Control Plane	Operational
Hasura DDN Data Plane	Operational
Hasura Cloud Dashboard and APIs	Operational

16 locations All operational

Open their status page

FlareWarden checks

hasura.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 116 ms
Checked: 39 minutes ago

By region

Amsterdam reachable, 77 ms
Chicago reachable, 90 ms
San Jose reachable, 102 ms
Singapore reachable, 142 ms
Stockholm reachable, 83 ms
Sydney reachable, 216 ms
Tokyo reachable, 99 ms
Toronto reachable, 125 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	12 ms	2 ms	7 ms	76 ms
Chicago	65 ms	2 ms	7 ms	89 ms
San Jose	76 ms	1 ms	11 ms	102 ms
Singapore	76 ms	1 ms	8 ms	141 ms
Stockholm	59 ms	1 ms	6 ms	82 ms
Sydney	197 ms	1 ms	7 ms	215 ms
Tokyo	74 ms	1 ms	8 ms	99 ms
Toronto	54 ms	1 ms	7 ms	125 ms

We check that hasura.io loads, not every feature behind it. Test it yourself

History

Incidents Hasura reported

Since Oct 22, 3 days · from hasura-status.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Hasura website availability

Measured by FlareWarden · hasura.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 143ms

Last 30 days

30-day clean streak

Sep 25 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of hasura.io from multiple regions every 6 hours. Hasura's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 30 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Hasura does

Hasura makes the open-source Hasura GraphQL Engine, which puts a GraphQL API over your databases, REST endpoints and other APIs. Teams self-host it or use Hasura Cloud, where each project gets a hasura.app domain in one AWS, GCP or Azure region. Its newer Hasura DDN builds federated data APIs from connectors, and PromptQL is its AI product. The status page covers these hosted services, not engines you run yourself.

What an outage looks like

Requests to your project's hasura.app endpoint time out or return errors, so apps built on it show empty screens or failed queries. The Cloud console may not load. On Hasura DDN, a control plane incident looks different: the API keeps answering, but new builds and connector deployments stall, new data planes cannot be provisioned and traces stop appearing in the console.

What to do about it

Find your project's region in the General tab of its project details, then check that region's row on status.hasura.io, grouped by AWS, GCP and Azure; the default is AWS us-east-2 (Ohio). On DDN, check the Control Plane and Data Plane rows separately. After a build incident is resolved, re-run builds started during it; in the September 2026 incident they did not recover by themselves.

Is it down for everyone, or just you?

If this page says Hasura is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

AWS

Cloudflare

Supabase

Neon

Hasura outage FAQ

Does a Hasura DDN control plane outage take my API down?

Usually not. Hasura's docs describe the control plane as the place for builds, the console and observability, while the data plane hosts your GraphQL API, and for Private DDN they state the control plane is not on the critical path for serving requests. In the June 2025 Google Cloud and Cloudflare incident, GraphQL and PromptQL APIs kept answering while DDN builds, provisioning and console traces failed.

Why is my Hasura Cloud project unreachable when the status page is green?

It may be hibernated. Hasura hibernates free-tier projects that have had no API requests for three months, after emailing the owner at 60 and 75 days. Metadata is kept, but API calls to the endpoint stop working until the owner clicks Reactivate in the project's section. Also confirm the project's region, since incidents on status.hasura.io are listed per region.

Do I need to re-run builds after a Hasura incident?

Sometimes, yes. On September 10, 2026, an authentication change in a control plane upgrade stalled new DDN connector deployments for about two hours. Hasura deployed a fix, but its resolution note said builds started during the impacted window still needed to be re-run. Read the final update on the incident before assuming your pending builds finished.

Which region is my Hasura Cloud project in?

The Region field in the project's General tab shows it. New projects default to AWS us-east-2 (Ohio), and owners can move a project, with a short downtime during the move. The status page lists 14 AWS, 13 GCP and 7 Azure regions separately, so an incident in one region does not mean your project is affected unless it runs there.

Does a Hasura outage affect self-hosted GraphQL Engine?

No, not a self-hosted Community Edition instance. That runs from Hasura's Docker image on your own infrastructure, so it depends on your servers and databases rather than Hasura Cloud. The status page covers Hasura Cloud regions, Hasura DDN, PromptQL and the monitoring used by Hasura Enterprise hybrid setups, which appears as its own row.

How we measure this

We request Hasura's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Hasura publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Hasura itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Hasura goes down

We check Hasura every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required