Partially Degraded Service

JMWE for JIRA Cloud Operational
90 days ago
99.57 % uptime
Today
3rd party services Operational
90 days ago
100.0 % uptime
Today
Heroku ? Operational
90 days ago
100.0 % uptime
Today
Atlassian Jira Degraded Performance
90 days ago
99.55 % uptime
Today
Jira Core Search Operational
90 days ago
99.58 % uptime
Today
Jira Core Notifications Operational
90 days ago
99.58 % uptime
Today
Jira Core Viewing content Operational
90 days ago
99.65 % uptime
Today
Jira Core Create and edit Operational
90 days ago
97.97 % uptime
Today
Jira Service Desk Service Desk Web Operational
90 days ago
100.0 % uptime
Today
Jira Service Desk Service Desk Portal Operational
90 days ago
99.48 % uptime
Today
Jira Software Administration Operational
90 days ago
99.42 % uptime
Today
Jira Software Notifications Operational
90 days ago
99.46 % uptime
Today
Jira Software Viewing content Operational
90 days ago
99.35 % uptime
Today
Jira Software Create and edit Operational
90 days ago
99.33 % uptime
Today
Jira Software Search Degraded Performance
90 days ago
99.46 % uptime
Today
Jira Core Administration Operational
90 days ago
99.54 % uptime
Today
Atlassian Developer Jira Cloud APIs Operational
90 days ago
100.0 % uptime
Today
Atlassian Developer User APIs Operational
90 days ago
100.0 % uptime
Today
Atlassian Developer Webhooks Operational
90 days ago
100.0 % uptime
Today
Atlassian Developer Authentication and user management Operational
90 days ago
100.0 % uptime
Today
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.
Apr 18, 2025

No incidents reported today.

Apr 17, 2025

No incidents reported.

Apr 16, 2025

No incidents reported.

Apr 15, 2025

No incidents reported.

Apr 14, 2025

No incidents reported.

Apr 13, 2025

No incidents reported.

Apr 12, 2025

No incidents reported.

Apr 11, 2025

No incidents reported.

Apr 10, 2025

No incidents reported.

Apr 9, 2025

No incidents reported.

Apr 8, 2025
Resolved - Atlassian has resolved the issue. JMWE is now fully operational across all instances, and no further action — including reinstalling the app — is required.

Thank you for your patience and understanding while we worked through this.

Apr 8, 06:54 EDT
Update - We’ve identified a number of instances where the token signature is invalid. Reinstalling the app immediately resolves the issue.

We’re currently investigating why these instances did not receive the new secret. This behavior appears to be related to Atlassian’s systems, and we’re working to get more clarity from their side.

Apr 7, 09:53 EDT
Update - We are continuing to investigate this issue.
Apr 7, 09:31 EDT
Investigating - We are currently investigating an issue affecting some clients following the upgrade of JMWE from version 1.2.41 to 1.2.42.

**** Impact:

Clients experiencing this issue may be unable to access the JMWE configuration and settings pages. Additionally, workflow extensions and JMWE actions may not function as expected.

**** Workaround:
Re-installing the JMWE app has resolved the issue for some affected clients. If you are experiencing these symptoms, we recommend trying a re-install as a temporary solution.

The issue has been reported to Atlassian, and we are working closely with them to identify the root cause and implement a permanent fix.

We will provide updates as more information becomes available. Thank you for your patience.

Apr 7, 09:31 EDT
Apr 7, 2025
Resolved - Between 7:00 AM UTC and 9:00 AM UTC, some users experienced intermittent 500 errors and functionality disruptions within the JMWE app. The issue was traced to upstream timeout errors originating from the Atlassian platform, which affected our app’s ability to communicate reliably with their services.

Our development team replicated the issue and actively collaborated with Atlassian to investigate and resolve the problem. Atlassian has acknowledged the issue on their end and has since resolved the underlying cause. System logs now show a return to normal behavior, and our internal checks confirm that JMWE functionality has been restored.

If any users continue to experience issues, performing a re-install of the app may help.

We appreciate your patience while we worked with Atlassian to address this matter.

Apr 7, 03:00 EDT
Apr 6, 2025
Completed - The scheduled maintenance for JMWE has been successfully completed ahead of time. All JMWE services are now fully operational.

Thank you for your patience and understanding.

Apr 6, 05:52 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 6, 04:30 EDT
Update - Updated Scheduled Maintenance for JMWE:

To better accommodate customers working on Saturdays, we are rescheduling our planned maintenance to Sunday, April 6, at the same time.

**** New Maintenance Schedule:

Start Time: Apr 6, 04:30 AM EDT

Estimated Duration: 2 hours

**** Expected Impact:

JMWE will not be available during the maintenance window.
All JMWE-related functionality will be temporarily unavailable.
Services will resume as soon as the maintenance is completed.

**** Action Required:

Users will not be able to access JMWE during this time.
We recommend planning your work accordingly to avoid disruptions.

Thank you for your understanding and flexibility.

Mar 31, 09:58 EDT
Scheduled - We will be performing scheduled maintenance to improve JMWE system performance and reliability.

**** Expected Impact:

JMWE will not be available during the maintenance window.
All JMWE-related functionality will be temporarily unavailable.
Services will resume as soon as the maintenance is completed.

**** Action Required:

Users will not be able to access JMWE during this time.
We recommend planning your work accordingly to avoid disruptions.

Mar 28, 10:29 EDT
Apr 5, 2025

No incidents reported.

Apr 4, 2025

No incidents reported.