🦊StackFox

Jira

Operational— checked just now

Productivity

Official Status

Components

Viewing content
Operational
Create and edit
Operational
Authentication and User Management
Operational
Search
Operational
Notifications
Operational
Administration
Operational
Marketplace
Operational
Mobile
Operational
Purchasing & Licensing
Operational
Signup
Operational
Automation for Jira
Operational

90-Day Uptime History

90 days agoToday
Issue-Free Days78 of 90d monitored
OperationalDegradedPartialOutageUnknown

Event Log

Status changed to OperationalOperational

5h ago

Status changed to OperationalOperational

11h ago

Status changed to OperationalOperational

17h ago

Resolved: Forge custom fields are not getting createdRESOLVED

23h ago

Status changed to OperationalOperational

23h ago

Status changed to DegradedDegraded

May 20, 9:19 AM

Forge custom fields are not getting createdMINOR

Our teams have identified the root cause and are in process of deploying a fix. We will share further updates in next 3 hours, or sooner if we have any meaningful developments to report. The impact is limited to new deployments with Forge custom fields on Jira work items, however existing deployments with custom fields are running without any issues.

May 20, 9:17 AM

Status changed to OperationalOperational

May 20, 6:50 AM

Status changed to OperationalOperational

May 20, 12:50 AM

Status changed to OperationalOperational

May 19, 6:50 PM

Status changed to OperationalOperational

May 19, 12:49 PM

Status changed to OperationalOperational

May 19, 6:49 AM

Status changed to OperationalOperational

May 19, 12:49 AM

Status changed to OperationalOperational

May 18, 6:48 PM

Status changed to OperationalOperational

May 18, 12:48 PM

Status changed to OperationalOperational

May 18, 6:48 AM

Status changed to OperationalOperational

May 18, 12:47 AM

Status changed to OperationalOperational

May 17, 6:47 PM

Status changed to OperationalOperational

May 17, 12:46 PM

Status changed to OperationalOperational

May 17, 6:45 AM

Status changed to OperationalOperational

May 17, 12:44 AM

Status changed to OperationalOperational

May 16, 6:44 PM

Status changed to OperationalOperational

May 16, 12:44 PM

Status changed to OperationalOperational

May 16, 6:44 AM

Status changed to OperationalOperational

May 16, 12:43 AM

Status changed to OperationalOperational

May 15, 6:43 PM

Status changed to OperationalOperational

May 15, 12:43 PM

Status changed to OperationalOperational

May 15, 6:42 AM

Status changed to OperationalOperational

May 15, 12:42 AM

Status changed to OperationalOperational

May 14, 6:41 PM

Status changed to OperationalOperational

May 14, 12:40 PM

Resolved: Users experiencing issues accessing multiple Atlassian productsRESOLVED

May 14, 6:48 AM

Status changed to OperationalOperational

May 14, 6:40 AM

Status changed to Partial OutagePartial Outage

May 14, 5:43 AM

Status changed to Major OutageMajor Outage

May 14, 4:55 AM

Users experiencing issues accessing multiple Atlassian productsCRITICAL

We are now able to see recovery for all impacted products, and users should be able to access their products as expected. Our team is continuing to monitor all products and services to ensure there is no further impact, and we will provide further update when this has been validated and the incident is closed.

May 14, 4:54 AM

Status changed to OperationalOperational

May 14, 3:59 AM

Status changed to OperationalOperational

May 13, 9:59 PM

Status changed to OperationalOperational

May 13, 3:59 PM

Resolved: Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some usersRESOLVED

May 13, 9:59 AM

Status changed to OperationalOperational

May 13, 9:59 AM

Status changed to Partial OutagePartial Outage

May 13, 7:37 AM

Status changed to Partial OutagePartial Outage

May 13, 1:37 AM

Automations within Jira, Jira Service Management and JSM Assist experiencing delays for some usersMAJOR

Our teams are actively processing events that were delayed during this incident. We will provide a further update once all delayed events have been processed.

May 13, 1:37 AM

Status changed to OperationalOperational

May 12, 11:18 PM

Status changed to OperationalOperational

May 12, 5:18 PM

Status changed to OperationalOperational

May 12, 11:18 AM

Status changed to OperationalOperational

May 12, 5:17 AM

Status changed to OperationalOperational

May 11, 11:17 PM

Status changed to OperationalOperational

May 11, 5:17 PM

Status data polled every 60 seconds. History retained for 90 days. Snapshots stored on status changes.