All Systems Operational

Uptime over the past 90 days. View historical uptime.
JXL for Jira Cloud Operational
90 days ago
100.0 % uptime
Today
JXL application Operational
90 days ago
100.0 % uptime
Today
Atlassian Jira app installation Operational
Atlassian Jira APIs Operational
Atlassian Jira (other) Operational
Netlify CDN Operational
AWS Route 53 Operational
🇦🇺 Sydney AWS Lambda Operational
🇦🇺 Sydney AWS DynamoDB Operational
🇯🇵 Tokyo AWS Lambda Operational
🇯🇵 Tokyo AWS DynamoDB Operational
🇰🇷 Seoul AWS Lambda Operational
🇰🇷 Seoul AWS DynamoDB Operational
🇸🇬 Singapore AWS Lambda Operational
🇸🇬 Singapore AWS DynamoDB Operational
🇮🇳 Mumbai AWS Lambda Operational
🇮🇳 Mumbai AWS DynamoDB Operational
🇪🇺 Frankfurt AWS Lambda Operational
🇪🇺 Frankfurt AWS DynamoDB Operational
🇨🇭 Zürich AWS Lambda Operational
🇨🇭 Zürich AWS DynamoDB Operational
🇬🇧 London AWS Lambda Operational
🇬🇧 London AWS DynamoDB Operational
🇧🇷 São Paulo AWS Lambda Operational
🇧🇷 São Paulo AWS DynamoDB Operational
🇨🇦 Montreal AWS Lambda Operational
🇨🇦 Montreal AWS DynamoDB Operational
🇺🇸 Northern Virginia AWS Lambda Operational
🇺🇸 Northern Virginia AWS DynamoDB Operational
JXL for Jira Data Center Operational
JXL application Operational
Atlassian Jira app installation Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Mar 13, 2026

No incidents reported today.

Mar 12, 2026

No incidents reported.

Mar 11, 2026

No incidents reported.

Mar 10, 2026

No incidents reported.

Mar 9, 2026

No incidents reported.

Mar 8, 2026

No incidents reported.

Mar 7, 2026

No incidents reported.

Mar 6, 2026

No incidents reported.

Mar 5, 2026

No incidents reported.

Mar 4, 2026
Some customers experience errors in asset columns
Resolved - Asset objects might be displayed as "Object data missing" in JXL sheets because Atlassian Jira APIs intermittently stop responding with the requested data.

We have worked through this problem with Atlassian. They have identified the cause on their side. Atlassian-internal secondary API requests are hitting recently newly established rate limits when large amounts of asset objects data are requested. The resulting request failures are not transparent to external apps such as JXL. Data is silently omitted, which is why we cannot improve this experience e.g. by serving more graceful and descriptive error messages at this point.

Atlassian has categorised this fix as a feature request and created https://jira.atlassian.com/browse/JSDCLOUD-18576 to track it. We can only highly recommend everyone affected to engage there by upvoting, commenting, and watching the work item. Additionally, if you have a Customer Success Manager, we suggest bringing it up with them as well. The ideal outcome would be if Atlassian decided to continue to allow larger amounts of your data to be retrieved.
Mar 4, 23:10 UTC
Update - Asset objects might be displayed as "Object data missing" in JXL sheets because Atlassian Jira APIs have intermittently stopped responding with the requested data. We have filed incident ECOHELP-113734 with Atlassian and are actively working with them on the problem. Atlassian has narrowed it down to an internal API's request limiting behaviour, but have yet "determine what options we have to reduce the impact".
Feb 26, 21:24 UTC
Update - Asset objects might be displayed as "Object data missing" in JXL sheets because Atlassian Jira APIs have intermittently stopped responding with the requested data. Potential causes being investigated include changes in assets permission interpretation, data volume, and API request limits. We have filed incident ECOHELP-113734 with Atlassian and are still awaiting their help and escalation on the case.
Feb 23, 21:48 UTC
Identified - Some asset objects might be displayed as "Object data missing". This is caused by Atlassian Jira APIs, which have intermittently stopped responding with the requested data. We have filed incident ECOHELP-113734 with Atlassian and are awaiting their first response on the case.
Feb 20, 10:35 UTC
Mar 3, 2026

No incidents reported.

Mar 2, 2026

No incidents reported.

Mar 1, 2026

No incidents reported.

Feb 28, 2026

No incidents reported.

Feb 27, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage