Drata · Operational
Observed by INTERNETMON
INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Drata status

Drata · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

0 retained of 0 reported
No active incidents were included in this vendor report.

Maintenance

1 retained of 1 reported

System is undergoing a scheduled maintenance

Some customers may be experiencing gaps in automated monitoring for resources in the AWS me-central-1 (UAE) and me-south-1 (Bahrain) regions. Due to ongoing service disruptions in these regions, we have temporarily disabled Drata's automated monitoring (data syncs and tests) for both regions. This change prevents test errors and instability for customers with infrastructure there. We are unsure when the situation will resolve but will continue to monitor for new changes.

Status scheduled Starts Ends Updated

Component health

Complete source scope
Reported
19
Retained
19
Affected retained
0
Projection scope: complete · 19 retained of 19 reported components across 3 source groups.
API US Group: US Operational
API EU Group: EU Operational
API APAC Group: APAC Operational
Agent API US Group: US Operational
Agent API EU Group: EU Operational
AGENT API APAC Group: APAC Operational
Public API US Group: US Operational
Public API EU Group: EU Operational
Public API APAC Group: APAC Operational
Auditor API US Group: US Operational
Auditor API EU Group: EU Operational
Auditor API APAC Group: APAC Operational
Web Application Operational
Incoming Webhooks US Group: US Operational
Incoming Webhooks EU Group: EU Operational
Incoming Webhooks APAC Group: APAC Operational
Trust Center Pages Operational
Trust Center Admin Page Operational
AIQA Operational

Recent observed status changes and checkpoints

Up to 30 days retained

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Operational
HTTP 200 · 368.51 ms feed latency
Operational
HTTP 200 · 382.03 ms feed latency
Operational
HTTP 200 · 442.17 ms feed latency
Operational
HTTP 200 · 345.0 ms feed latency
Operational
HTTP 200 · 455.05 ms feed latency
Operational
HTTP 200 · 395.0 ms feed latency
Operational
HTTP 200 · 460.72 ms feed latency
Operational
HTTP 200 · 472.94 ms feed latency
Operational
HTTP 200 · 600.39 ms feed latency
Operational
HTTP 200 · 351.17 ms feed latency

Collection details

Sanitized public metadata
Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
388.98 ms
JSON source
Sanitized detail projection