Last checked: 3 minutes ago
Get notified about any outages, downtime or incidents for Jira and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Jira.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Administration | Active |
Authentication and User Management | Active |
Automation for Jira | Active |
Create and edit | Active |
Marketplace | Active |
Mobile | Active |
Notifications | Active |
Purchasing & Licensing | Active |
Search | Active |
Signup | Active |
Viewing content | Active |
View the latest incidents for Jira and check for official updates:
Description: Between 02:00 AM UTC to 04:13 AM UTC, we experienced email address handling failures, for email fields and smart values, which resulted in rule executions failing for some customers using Automation for Jira - JSW, JSM, JWM, JPD. The issue has been resolved and the service is operating normally.
Status: Resolved
Impact: None | Started At: Feb. 2, 2024, 8:53 a.m.
Description: At around 4am UTC, about 40 percent of Forge app invocations experienced high latency, with a portion of the requests failing, during a 15 minute time window. The scaling of the instances was misconfigured following a new deployment of the service, which needed manual intervention which took a few minutes to resolve the issue. Timeline: - 2024-01-31 04:00 UTC: impact started - 2024-01-31 04:03 UTC: incident detected - 2024-01-31 04:15 UTC: the incident was resolved and the impact ended This issue is now resolved and Forge is fully operational. We apologize for any inconveniences this may have caused to our customers, partners, and our developer community.
Status: Resolved
Impact: None | Started At: Jan. 31, 2024, 6:03 a.m.
Description: At around 4am UTC, about 40 percent of Forge app invocations experienced high latency, with a portion of the requests failing, during a 15 minute time window. The scaling of the instances was misconfigured following a new deployment of the service, which needed manual intervention which took a few minutes to resolve the issue. Timeline: - 2024-01-31 04:00 UTC: impact started - 2024-01-31 04:03 UTC: incident detected - 2024-01-31 04:15 UTC: the incident was resolved and the impact ended This issue is now resolved and Forge is fully operational. We apologize for any inconveniences this may have caused to our customers, partners, and our developer community.
Status: Resolved
Impact: None | Started At: Jan. 31, 2024, 6:03 a.m.
Description: All sandbox sites that were affected by this incident have been restored and are now accessible.
Status: Resolved
Impact: Major | Started At: Jan. 23, 2024, 2:24 p.m.
Description: All sandbox sites that were affected by this incident have been restored and are now accessible.
Status: Resolved
Impact: Major | Started At: Jan. 23, 2024, 2:24 p.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.