Vendor-reported status observed by INTERNETMON
Hasura status
Hasura · Atlassian Statuspage
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.
Active incidents
No active incidents were included in this vendor report.
Maintenance
No active or upcoming maintenance was included in this vendor report.
Component health
Reported
50
Retained
50
Affected retained
0
Projection scope: complete · 50 retained of 50 reported components across 8 source groups.
Hasura Cloud Dashboard and APIs
Operational
Self-hosted EE(Hybrid Setup) - Monitoring
Group: Hasura EE (Hybrid Setup)
Operational
GCP: Iowa (us-central1)
Group: GCP: Metrics & Reporting
Operational
AWS: London (eu-west-2)
Group: AWS: Metrics & Reporting
Operational
Azure: Virginia (eastus)
Group: Azure: Metrics & Reporting
Operational
Azure: Virginia (eastus)
Group: Hasura Cloud Azure Regions
Operational
Hasura DDN Control Plane
Group: Hasura DDN
Operational
Hasura Console
Operational
AWS: Tokyo (ap-northeast-1)
Group: Hasura Cloud AWS Regions
Operational
GCP: Los Angeles (us-west2)
Group: Hasura Cloud GCP Regions
Operational
GCP: Frankfurt (europe-west3)
Group: GCP: Metrics & Reporting
Operational
AWS: Sydney (ap-southeast-2)
Group: AWS: Metrics & Reporting
Operational
Azure: Paris (francecentral)
Group: Hasura Cloud Azure Regions
Operational
Azure: Paris (francecentral)
Group: Azure: Metrics & Reporting
Operational
Hasura DDN Data Plane
Group: Hasura DDN
Operational
AWS: N. Virginia (us-east-1)
Group: Hasura Cloud AWS Regions
Operational
GCP: Iowa (us-central1)
Group: Hasura Cloud GCP Regions
Operational
AWS: Tokyo (ap-northeast-1)
Group: AWS: Metrics & Reporting
Operational
GCP: Los Angeles (us-west2)
Group: GCP: Metrics & Reporting
Operational
AWS: London (eu-west-2)
Group: Hasura Cloud AWS Regions
Operational
Showing 20 of 50 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.
Recent observed status changes and checkpoints
These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.
Operational
HTTP 200 · 271.74 ms feed latency
Operational
HTTP 200 · 784.55 ms feed latency
Operational
HTTP 200 · 264.68 ms feed latency
Operational
HTTP 200 · 300.54 ms feed latency
Operational
HTTP 200 · 137.08 ms feed latency
Operational
HTTP 200 · 175.82 ms feed latency
Operational
HTTP 200 · 145.3 ms feed latency
Operational
HTTP 200 · 291.04 ms feed latency
Operational
HTTP 200 · 203.89 ms feed latency
Operational
HTTP 200 · 465.36 ms feed latency
Collection details
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
192.42 ms
JSON source