Jira outage — 2026-08-27
Major System Outage It began at 2026-08-27 04:27 UTC and recovered at 2026-08-27 05:21 UTC, lasting 54 min. We recorded 18 failing checks during the window.
Check-by-check timeline
- 2026-08-27 04:15 UTCOperational364ms · HTTP 200All Systems Operational
- 2026-08-27 04:18 UTCOperational205ms · HTTP 200All Systems Operational
- 2026-08-27 04:21 UTCOperational155ms · HTTP 200All Systems Operational
- 2026-08-27 04:24 UTCDown253ms · HTTP 200Major System Outage
- 2026-08-27 04:27 UTCDown146ms · HTTP 200Major System Outage
- 2026-08-27 04:30 UTCDown434ms · HTTP 200Major System Outage
- 2026-08-27 04:33 UTCDown535ms · HTTP 200Major System Outage
- 2026-08-27 04:36 UTCDown201ms · HTTP 200Major System Outage
- 2026-08-27 04:39 UTCDown395ms · HTTP 200Major System Outage
- 2026-08-27 04:42 UTCDown525ms · HTTP 200Major System Outage
- 2026-08-27 04:45 UTCDown112ms · HTTP 200Major System Outage
- 2026-08-27 04:48 UTCDown273ms · HTTP 200Major System Outage
- 2026-08-27 04:51 UTCDown218ms · HTTP 200Major System Outage
- 2026-08-27 04:54 UTCDown306ms · HTTP 200Major System Outage
- 2026-08-27 04:57 UTCDown270ms · HTTP 200Major System Outage
- 2026-08-27 05:00 UTCDown897ms · HTTP 200Major System Outage
- 2026-08-27 05:03 UTCDown186ms · HTTP 200Major System Outage
- 2026-08-27 05:06 UTCDown155ms · HTTP 200Major System Outage
- 2026-08-27 05:09 UTCDown331ms · HTTP 200Major System Outage
- 2026-08-27 05:12 UTCDown99ms · HTTP 200Major System Outage
- 2026-08-27 05:15 UTCDown139ms · HTTP 200Major System Outage
- 2026-08-27 05:18 UTCOperational286ms · HTTP 200All Systems Operational
- 2026-08-27 05:21 UTCOperational357ms · HTTP 200All Systems Operational
- 2026-08-27 05:24 UTCOperational294ms · HTTP 200All Systems Operational
- 2026-08-27 05:27 UTCOperational494ms · HTTP 200All Systems Operational
- 2026-08-27 05:30 UTCOperational164ms · HTTP 200All Systems Operational
- 2026-08-27 05:33 UTCOperational174ms · HTTP 200All Systems Operational
Current Jira status and full outage history
How this is measured
Readings are taken every few minutes from outside Jira's network, combining their published status feed with a timed request to the service itself.
An incident opens after two consecutive bad readings and closes after two consecutive good ones, so the recorded duration may be a few minutes wider than the true outage.
Jira's official status page is the authority on causes and affected components.