Skip to main content
Hasura logo

Is Hasura Down?

No — Hasura is up

Reachable from all 8 checked regions

Average response time: 107ms

Last checked · checks run every 6 hours

Official status page: https://hasura-status.com

Hasura uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
137ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 17 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

17-day clean streak
Sep 13: no data
Sep 14: no data
Sep 15: no data
Sep 16: no data
Sep 17: no data
Sep 18: no data
Sep 19: no data
Sep 20: no data
Sep 21: no data
Sep 22: no data
Sep 23: no data
Sep 24: no data
Sep 25: 100.00% uptime, 16 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 35 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: no data
Sep 13 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
55ms
DNS 17ms TCP 2ms TLS 10ms TTFB 55ms
arn
155ms
DNS 131ms TCP 1ms TLS 7ms TTFB 154ms
cdg
220ms
DNS 182ms TCP 1ms TLS 8ms TTFB 220ms
ord
52ms
DNS 23ms TCP 1ms TLS 10ms TTFB 52ms
sin
35ms
DNS 8ms TCP 1ms TLS 6ms TTFB 35ms
sjc
106ms
DNS 78ms TCP 2ms TLS 8ms TTFB 106ms
syd
133ms
DNS 112ms TCP 0ms TLS 8ms TTFB 132ms
yyz
107ms
DNS 54ms TCP 1ms TLS 10ms TTFB 106ms

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
AWS
Cloudflare
Cloudflare
Supabase
Supabase
Neon
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.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Hasura goes down

This page refreshes every 6 hours. 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