Is Hasura down?
Last checked just nowNo incidents right now.
Hasura is operational right now. Last checked just now; the most recent incident resolved 2d ago.
Real-time Hasura status, recent outages, and incident history — pulled directly from Hasura's official status page at https://hasura-status.com every 5 minutes. Pingoru tracks 66 Hasura services and has captured 2 incidents in the last 90 days (99.95% uptime). Get email, Slack, Discord, or webhook alerts the moment Hasura reports a new incident — free for 5 monitors, no credit card.
Recent outages & incidents
Past 90 days- PromptQL APIPromptQL Playground
Timeline · 4 updates
- investigating · Sep 12, 2026, 02:48 PM UTC
Status: Investigating We're investigating elevated latency on PromptQL. You might see the app taking longer than usual to load or failures in sending messages. Dedicated data planes are not affected. Affected components PromptQL API (Degraded performance) PromptQL Playground (Degraded performance)
- identified · Sep 12, 2026, 03:18 PM UTC
Status: Identified We've identified the root cause and are working on mitigation. Affected components PromptQL Playground (Degraded performance) PromptQL API (Degraded performance)
- monitoring · Sep 12, 2026, 03:37 PM UTC
Status: Monitoring Applied a fix. Affected components PromptQL API (Degraded performance) PromptQL Playground (Degraded performance)
- resolved · Sep 12, 2026, 03:44 PM UTC
Status: Resolved Resolved. Affected components PromptQL API (Operational) PromptQL Playground (Operational)
Latest: Status: Resolved Resolved. Affected components PromptQL API (Operational) PromptQL Playground (Operational)
-
-
Timeline · 4 updates
- investigating · Sep 10, 2026, 04:03 PM UTC
Status: Investigating We are investigating an issue where DDN connector builds are not completing. Our team is working to identify the cause and restore normal build processing.
- investigating · Sep 10, 2026, 05:23 PM UTC
Status: Investigating We've identified the root cause: an authentication change in a recent control-plane upgrade caused new connector deployments to stall in a pending state. The fix has been merged and is being rolled out now. Once deployed, we'll re-run your pending connector builds and confirm your development environment is unblocked; no changes are needed on your side.
- monitoring · Sep 10, 2026, 06:00 PM UTC
Status: Monitoring We identified the root cause: an authentication change in the service that initializes connector deployments, introduced by an internal upgrade and deployed a fix at approximately 17:30 UTC. New builds started after this time are processing normally. Action required: builds started during the impacted window will not complete on their own. Please re-run any affected builds (ddn connector build create / ddn supergraph build create). No other action is needed. We are continuing to monitor and will post a final update once we have confirmed full recovery.
- resolved · Sep 10, 2026, 06:10 PM UTC
Status: Resolved Connector deployments have been processing normally since the fix was deployed. Builds started during the impacted window still need to be re-run.
Latest: Status: Resolved Connector deployments have been processing normally since the fix was deployed. Builds started during the impacted window still need to be re-run.
-
- Increased latency on PromptQL ResolvedStarted Sep 12, 2026, 03:44 PM UTC · Resolved Sep 12, 2026, 03:44 PM UTC · —
- Started Sep 10, 2026, 06:10 PM UTC · Resolved Sep 10, 2026, 06:10 PM UTC · —