Adaptavist Cloud Apps Outage History

Adaptavist Cloud Apps degraded · 1 active incident · 2 long-running issues View live status →

Pingoru has recorded 58 incidents for Adaptavist Cloud Apps: 56 in the last 12 months and 17 in the last 90 days.

Source: status.connect.adaptavist.com

58incidents recorded
56last 12 months
17last 90 days
20 hourstypical duration
Incidents per month
0510AprMayJunJulAugSepOct10
Share of hours with an open incident, any severity
0%50%100%AprMayJunJulAugSepOct100%
Pingoru began tracking Adaptavist Cloud Apps in April 2026, so earlier months are not shown. Hover a bar for its value.
Show as a table
MonthIncidentsHours with an open incident
April 20265106 of 720 (15%)
May 2026114 of 744 (2%)
June 2026423 of 720 (3%)
July 2026528 of 744 (4%)
August 202612 of 744 (0%)
September 2026437 of 720 (5%)
October 202610582 of 582 (100%)

Incidents, newest first

Minor April 16, 2026 Event webhook processing is failing for some events 38m ScriptRunner for Jira Cloud, Enhanced Search for Jira Cloud, ScriptRunner for Confluence Cloud

Started Apr 16, 2026, 08:17 AM UTC· resolved Apr 16, 2026, 08:56 AM UTC

  1. investigating Apr 16, 2026, 08:17 AM UTC

    We are seeing webhook processing for certain types of events fail with authentication errors. We are looking into the problem and will update here more when we have more information.

  2. identified Apr 16, 2026, 08:31 AM UTC

    We believe we have identified a resolution to the webhook processing issues we have been experiencing this morning. We are currently validating that this solution has mitigated the errors.

  3. monitoring Apr 16, 2026, 08:46 AM UTC

    The solution seems to have mitigated the issues we were seeing this morning. We are continue to monitor the situation closely.

  4. resolved Apr 16, 2026, 08:56 AM UTC

    We are confident that the issues we were seeing with processing event webhooks are resolved now. Please get in touch with our team if you experience any more issues.

Read the full incident report →

Notice April 13, 2026 Outage for Scriptrunner and EnhancedSearch apps in US region 3m ScriptRunner for Jira Cloud, Behaviours - ScriptRunner for Jira Cloud, Enhanced Search for Jira Cloud, ScriptRunner for Confluence Cloud

Started Apr 13, 2026, 09:59 AM UTC· resolved Apr 13, 2026, 10:02 AM UTC

  1. resolved Apr 13, 2026, 10:31 AM UTC

    At 9:59 to 10:02 UTC (10:59 to 11:02 BST), there was an outage for ScriptRunner and EnhancedSearch apps in the US region only.

Read the full incident report →

Notice March 25, 2026 A subset of customer requests in customer scripts failed 4m ScriptRunner for Jira Cloud

Started Mar 25, 2026, 11:40 AM UTC· resolved Mar 25, 2026, 11:45 AM UTC

  1. identified Mar 25, 2026, 11:40 AM UTC

    We have identified that some requests within customer scripts failed on 24/03/2026 between 16:27 -> 19:52 UTC

  2. resolved Mar 25, 2026, 11:45 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 12, 2026 Custom Macro Not Working Due to Atlassian Issue 9h 41m ScriptRunner for Confluence Cloud

Started Mar 12, 2026, 03:06 PM UTC· resolved Mar 13, 2026, 12:47 AM UTC

  1. identified Mar 12, 2026, 03:06 PM UTC

    Macros are currently impacted due to an Atlassian platform incident.

  2. identified Mar 12, 2026, 03:23 PM UTC

    We continue to monitor the Atlassian incident affecting Scriptrunner macros. We will provide updates as more information becomes available.

  3. identified Mar 12, 2026, 06:42 PM UTC

    We are still monitoring the Atlassian incident for Macros outage, that is impacting the scriptrunner macros. We will update once we see the change in status on Atlassian status page

  4. monitoring Mar 13, 2026, 12:36 AM UTC

    Atlassian has resolved the incident affecting macro functionality. We are monitoring to ensure services is stable.

  5. resolved Mar 13, 2026, 12:47 AM UTC

    Our monitoring has now confirmed that the issue affecting macro functionality has been resolved and that services are running normally again. We apologise for any inconvenience caused.

Read the full incident report →

Notice March 12, 2026 Temporary script executions outage 5h 1m ScriptRunner for Jira Cloud

Started Mar 12, 2026, 03:24 AM UTC· resolved Mar 12, 2026, 08:25 AM UTC

  1. identified Mar 12, 2026, 10:30 AM UTC

    A small minority of scripts failed to run between 11th March 03:24 UTC and 12th March 08:25 UTC due to excessive load on the ScriptRunner execution environment and hitting rate limits with our hosting provider. This was due to an unexpected and significant spike in script execution demand.

  2. resolved Mar 12, 2026, 10:31 AM UTC

    At 08:25 UTC the execution demand dropped to normal levels and the system resumed normal operation.

Read the full incident report →

Notice February 25, 2026 2026-02-25 Temporary script executions outage 2m ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud

Started Feb 25, 2026, 05:33 PM UTC· resolved Feb 25, 2026, 05:35 PM UTC

  1. identified Feb 27, 2026, 02:20 PM UTC

    Some scripts failed to run between 17:33 UTC and 17:35 UTC due to excessive load on the ScriptRunner execution environment and hitting rate limits with our hosting provider. This was due to an unexpected and significant spike in script execution demand.

  2. resolved Feb 27, 2026, 02:23 PM UTC

    At 17:35 the execution demand dropped to normal levels and the system resumed normal operation.

Read the full incident report →

Minor February 20, 2026 Delays in filter syncing in SR Enhanced Search US 4h 25m ScriptRunner for Jira Cloud

Started Feb 20, 2026, 02:16 PM UTC· resolved Feb 20, 2026, 06:42 PM UTC

  1. identified Feb 20, 2026, 02:16 PM UTC

    We are currently experiencing delays in filter syncing in SR Enhanced Search US. Filter results may be out of date temporarily until the issue is resolved. We have identified the root cause and working on a potential fix.

  2. monitoring Feb 20, 2026, 02:41 PM UTC

    A potential fix is being deployed and will be monitored on production shortly.

  3. monitoring Feb 20, 2026, 03:24 PM UTC

    While we continue to monitor the situation, the ES filters can be manually synced as a workaround in the meantime.

  4. monitoring Feb 20, 2026, 03:30 PM UTC

    ES filters are starting to be automatically synced again; we'll continue to monitor the situation until we can confirm the issue is fully resolved. In the meantime, manual filter syncing is also possible as a temporary workaround.

  5. monitoring Feb 20, 2026, 04:57 PM UTC

    Upon further review, an additional fix is still required and in the process of being deployed. Automatic filter syncing may only work intermittently at this point; we'll continue to monitor the situation until the issue is fully resolved.

  6. identified Feb 20, 2026, 05:06 PM UTC

    ES Filters may not have been synced during the last 30 minutes; we have identified the cause and we are in the process of deploying another fix. Apologies for the inconvenience; we appreciate your patience while we resolve this issue.

  7. monitoring Feb 20, 2026, 06:29 PM UTC

    The issue may have been resolved after the latest fix was deployed. We'll continue to monitor the situation and we are hopeful the incident can be resolved soon.

  8. resolved Feb 20, 2026, 06:42 PM UTC

    The issue has been resolved, after verifying that ES filter syncing is now working as expected. Apologies for the inconvenience, and thank you for your patience.

Read the full incident report →

Notice January 21, 2026 Some customers might not be able to load executed Scriptrunner post functions 4h 13m ScriptRunner for Jira Cloud

Started Jan 21, 2026, 09:30 AM UTC· resolved Jan 21, 2026, 01:43 PM UTC

  1. identified Jan 21, 2026, 09:30 AM UTC

    We have identified an issue affecting ScriptRunner for Jira Cloud post functions, where some customers are unable to access their post functions.

  2. monitoring Jan 21, 2026, 10:49 AM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jan 21, 2026, 01:43 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice January 14, 2026 Lifetenant service failure due to unhealthy host 38m ScriptRunner for Jira Cloud, Enhanced Search for Jira Cloud, ScriptRunner for Confluence Cloud

Started Jan 14, 2026, 04:21 PM UTC· resolved Jan 14, 2026, 04:59 PM UTC

  1. identified Jan 14, 2026, 04:21 PM UTC

    We have identified the issue and working on resolving the issue asap.

  2. monitoring Jan 14, 2026, 04:33 PM UTC

    We have updated the task count to help resolve the issue, we are monitering the metrics to check if the incident is resolved.

  3. resolved Jan 14, 2026, 04:59 PM UTC

    We have rolled back the changes, the incident is resolved now.

Read the full incident report →

Minor January 9, 2026 Forge product events relating to boards and sprints failing 1h 29m ScriptRunner for Jira Cloud

Started Jan 09, 2026, 09:23 AM UTC· resolved Jan 09, 2026, 10:52 AM UTC

  1. investigating Jan 09, 2026, 09:23 AM UTC

    We are experiencing issues processing sprint and board events from Jira, meaning automated workloads relating to sprints and boards may be failing. We are investigating the issue and will provide more updates soon.

  2. monitoring Jan 09, 2026, 09:56 AM UTC

    We have reversed a change that we believe to be cause of the problem. The errors that we were witnessing before have stopped since then. We also believe this issue only affected a very small number of clients. We will continue to monitor the situation closely.

  3. resolved Jan 09, 2026, 10:52 AM UTC

    We are confident that the issue we witnessed this morning is resolved and did not impact the vast majority of our users. We will close this incident, but will continue to monitor the status of the relevant systems as necessary.

Read the full incident report →

Minor January 8, 2026 Filter syncing delays in ScriptRunner Enhanced Search in US 2h 3m

Started Jan 08, 2026, 07:57 PM UTC· resolved Jan 08, 2026, 10:00 PM UTC

  1. resolved Jan 09, 2026, 09:22 AM UTC

    We experienced delays in automated filter syncing for ScriptRunner for Jira Enhanced Search customers in the US from 19:57 UTC to 22:00 UTC. Some filter results may have been out of date during this period for some customers. A work around was available at this time by manually syncing the filter from the Enhanced Search page. We apologise for the disruption and are implementing architecture changes to improve the stability of this service.

Read the full incident report →

Minor December 31, 2025 Some customer scripts may fail to execute in US region 5h 18m ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud

Started Dec 31, 2025, 07:56 AM UTC· resolved Dec 31, 2025, 01:14 PM UTC

  1. investigating Dec 31, 2025, 07:56 AM UTC

    We are investigating an active issue in the US region where some customer scripts may fail to execute or experience delays due to a problem in our script execution service.

  2. monitoring Dec 31, 2025, 08:45 AM UTC

    We have identified the issue related to script executions, applied the fix and we are monitoring the services.

  3. resolved Dec 31, 2025, 01:14 PM UTC

    We’re confident the ScriptRunner Cloud issues are now resolved, so we’re closing this incident. If you experience any further issues, please contact our team.

Read the full incident report →

Minor December 29, 2025 Some customer scripts failed to execute in US region 2d 2h ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud

Started Dec 29, 2025, 12:30 PM UTC· resolved Dec 31, 2025, 03:10 PM UTC

  1. investigating Dec 30, 2025, 09:54 AM UTC

    A minority of customer scripts didn't run in the US region. This occurred between 12:30 and 16:30 on 29th December.

  2. identified Dec 30, 2025, 09:58 AM UTC

    We have identified the issue and we are deploying a patch

  3. monitoring Dec 30, 2025, 12:33 PM UTC

    All scripts are now running as normal. We've implemented a fix that improves our fallback behaviour in the distributed cache system.

  4. resolved Dec 31, 2025, 03:10 PM UTC

    We’re confident the ScriptRunner Cloud issues are now resolved, so we’re closing this incident. If you experience any further issues, please contact our team. Apologies for the inconvenience

Read the full incident report →

Minor December 12, 2025 Automated migrations using JCMA are blocked due to ScriptRunner for Jira cloud appearing to not have an Automated migration path 3d 21h ScriptRunner for Jira Cloud

Started Dec 12, 2025, 04:55 PM UTC· resolved Dec 16, 2025, 02:28 PM UTC

  1. investigating Dec 12, 2025, 04:55 PM UTC

    Automated migrations of ScriptRunner config via JCMA may be bocked due to JCMA not discovering that ScriptRunner for Jira Cloud has an automated migration path.

  2. monitoring Dec 15, 2025, 02:17 PM UTC

    After some updates, we have observed the automated path for JCMA migrations to have returned. We are still monitoring the situation and working with Atlassian to ensure it is resolved across the board.

  3. resolved Dec 16, 2025, 02:28 PM UTC

    We have confirmed that automated migrations are working properly. We have identified the root cause and putting things in place to prevent a future outage.

Read the full incident report →

Minor December 10, 2025 Delays in Script executions 17h 4m ScriptRunner for Jira Cloud

Started Dec 10, 2025, 04:48 PM UTC· resolved Dec 11, 2025, 09:52 AM UTC

  1. identified Dec 10, 2025, 04:48 PM UTC

    W've become aware of delays in script executions and are deploying a measure that should improve matters. We'll monitor its efficacy and update further.

  2. identified Dec 10, 2025, 07:58 PM UTC

    The measures we deployed to address delays in script execution have been effective, and scripts are now running at normal performance levels. We will continue to monitor the application, and will mark this incident as resolved if no further issues are observed.

  3. resolved Dec 11, 2025, 09:52 AM UTC

    Scripts appear to have continued to perform at their standard level throughout a period of monitoring, therefore we're marking this incident as resolved. Apologies for any inconvenience caused.

Read the full incident report →

Minor December 10, 2025 Scripted fields value not syncing on background refresh 20h 15m ScriptRunner for Jira Cloud

Started Dec 10, 2025, 11:29 AM UTC· resolved Dec 11, 2025, 07:44 AM UTC

  1. identified Dec 10, 2025, 11:29 AM UTC

    We have identified the cause of the issue with Scripted Fields not displaying. We are currently working on creating a fix for the issue and will post a further update for this issue once a fix has been deployed. We apologise for any inconvenience caused.

  2. resolved Dec 11, 2025, 07:44 AM UTC

    We deployed a fix on 10 Dec at 19:32 UTC to resolve the issue and can confirm that the incident is now fully resolved. We apologise for any inconvenience caused.

Read the full incident report →

Minor December 3, 2025 Scripts using Saved Script fail to execute 1d 1h ScriptRunner for Jira Cloud

Started Dec 03, 2025, 04:08 PM UTC· resolved Dec 04, 2025, 05:50 PM UTC

  1. investigating Dec 03, 2025, 04:08 PM UTC

    ScriptRunner scripts using Saved Scripts from Script Manager are experiencing failures to download the Saved Scripts resulting in failures to run the script. It affects ScriptRunner config importing Saved Scripts as well as config pointing directly to saved scripts.

  2. identified Dec 04, 2025, 10:49 AM UTC

    We have identified an issue with the access to Saved Scripts from the execution environment

  3. monitoring Dec 04, 2025, 10:53 AM UTC

    We have deployed a fix to the scripts execution process to allow for more robust access to the Saved Scripts from the execution environment.

  4. resolved Dec 05, 2025, 11:45 AM UTC

    All script using saved scripts from Script Manager are now working as expected.

Read the full incident report →

Notice November 25, 2025 Script Listeners and Workflow functions are not executing. 5h 28m

Started Nov 25, 2025, 10:03 PM UTC· resolved Nov 26, 2025, 03:32 AM UTC

  1. investigating Nov 25, 2025, 10:03 PM UTC

    We’ve identified an issue affecting the Script Listeners and Workflows service. Our team is currently investigating the cause and working to resolve it. We’ll provide an update as soon as we have more information.

  2. investigating Nov 25, 2025, 10:06 PM UTC

    We have identified that this issue affects only the US region. We are continuing to investigate further and will provide an update as soon as we have more information.

  3. investigating Nov 26, 2025, 12:41 AM UTC

    We’ve identified the issue and are working on a fix.

  4. investigating Nov 26, 2025, 02:23 AM UTC

    We found the issue, deployed a fix, and are continuing to monitor the situation.

  5. resolved Nov 26, 2025, 03:32 AM UTC

    We’re confident the ScriptRunner Cloud issues are now resolved, so we’re closing this incident. If you experience any further issues, please contact our team.

Read the full incident report →

Notice November 21, 2025 Workflows page showing blank screen 2h 48m ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud

Started Nov 21, 2025, 08:27 AM UTC· resolved Nov 21, 2025, 11:15 AM UTC

  1. investigating Nov 21, 2025, 08:27 AM UTC

    We have an identified an issue with the Workflows service which is causing this page not to load. We are currently investigating what is causing this issue and will post a further update here once we have identified what is causing the issue. We apologise for any inconvenience caused.

  2. identified Nov 21, 2025, 09:00 AM UTC

    We have deployed a fix to resolve the issue and will continue to monitor our services to ensure the incident is fully resolved. We apologise for any inconvenience caused.

  3. resolved Nov 21, 2025, 11:15 AM UTC

    Our monitoring has now confirmed that the incident has been resolved and that all services are running as normal again. We apologise for any inconvenience caused.

Read the full incident report →

Minor November 19, 2025 Unable to load the SR portal 19h 15m ScriptRunner for Jira Cloud, Behaviours - ScriptRunner for Jira Cloud, Enhanced Search for Jira Cloud, ScriptRunner for Confluence Cloud

Started Nov 19, 2025, 03:59 PM UTC· resolved Nov 20, 2025, 11:15 AM UTC

  1. investigating Nov 19, 2025, 03:59 PM UTC

    We have received reports that the Script Runner portal is failing to load. We are currently investigating

  2. monitoring Nov 19, 2025, 04:41 PM UTC

    We have implemented a fix and the portal should now load as expected. We will continue to monitor the situation

  3. monitoring Nov 19, 2025, 05:26 PM UTC

    We are continuing to monitor the situation.

  4. monitoring Nov 19, 2025, 08:54 PM UTC

    We are continuing to monitor the situation to see if it remains stable.

  5. monitoring Nov 20, 2025, 09:11 AM UTC

    We are continuing to monitor system health after yesterday's issues with using the ScriptRunner Cloud applications. We will post further updates here when we are confident that the issues have been resolved.

  6. resolved Nov 20, 2025, 11:15 AM UTC

    We are confident that the issues experienced with using ScriptRunner Cloud apps yesterday are now resolved, so we are closing this incident. If you experience any further issues then please get in touch with our team.

Read the full incident report →

Notice November 13, 2025 Failing to fetch behaviours logs 1h 29m Behaviours - ScriptRunner for Jira Cloud

Started Nov 13, 2025, 07:29 AM UTC· resolved Nov 13, 2025, 08:58 AM UTC

  1. investigating Nov 13, 2025, 07:29 AM UTC

    We've identified an issue with customers not being able to view their behaviours logs

  2. monitoring Nov 13, 2025, 08:21 AM UTC

    We have deployed a fix to resolve the issue and will continue to monitor our services to ensure the incident is fully resolved. We apologise for any inconvenience caused.

  3. resolved Nov 13, 2025, 08:58 AM UTC

    Our monitoring has now confirmed that the incident has been resolved and that all services are running as normal again. We apologise for any inconvenience caused.

Read the full incident report →

Notice November 10, 2025 Some customers experiencing a shorter 60s timeout on script executions 8m ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud

Started Nov 10, 2025, 08:54 AM UTC· resolved Nov 10, 2025, 09:03 AM UTC

  1. identified Nov 10, 2025, 08:54 AM UTC

    We have identified the issue relating to timeouts occuring on a limited number of script executions

  2. resolved Nov 10, 2025, 09:03 AM UTC

    We have reverted the change causing the shorter timeouts. This has been confirmed to fix the issue.

Read the full incident report →

Notice October 22, 2025 Incident with the SR Confluence Cloud Script Listener Service 6h 48m ScriptRunner for Confluence Cloud

Started Oct 22, 2025, 03:33 PM UTC· resolved Oct 22, 2025, 10:21 PM UTC

  1. investigating Oct 22, 2025, 03:33 PM UTC

    We have identified an issue with the Script Listener service that is related to an incident with Atlassian's Confluence Webhooks not being delivered. Due to this degradation in the delivery of Webhooks, Script Listeners may not be triggered as a result of this. We are currently monitoring the incident and will post a further update here once we have more information. We apologize for any inconvenience caused.

  2. identified Oct 22, 2025, 09:45 PM UTC

    Atlassian has identified the issue causing Confluence webhooks to not be delivered and is testing a fix internally.

  3. resolved Oct 22, 2025, 10:21 PM UTC

    Atlassian has deployed a fix to mitigate the webhooks problem, and we've verified that the Script Listener service is now operating normally. If your Script Listener did not work between 01:00 and 20:47 UTC on October 22, 2025, it was likely affected by this incident.

Read the full incident report →

Notice October 21, 2025 AWS and Atlassian Major Outages Across Most Services and API's – ScriptRunner for Jira Cloud, Behaviours - ScriptRunner for Jira Cloud, Enhanced Search for Jira Cloud, ScriptRunner for Confluence Cloud

Started Oct 21, 2025, 07:24 AM UTC· resolved Oct 21, 2025, 07:24 AM UTC

  1. resolved Oct 21, 2025, 07:24 AM UTC

    Between 20-21 October, Atlassian Cloud experienced a major service disruption due to an outage in AWS’s US-EAST-1 region that affected DNS resolution and dependent global services (e.g., DynamoDB, IAM). This caused partial or complete unavailability across multiple Atlassian systems, including: * Jira Cloud, Confluence Cloud, and Bitbucket Cloud APIs * Marketplace (app listings, installations, licensing, and vendor management) * Forge developer platform (app deployment, logging, and monitoring) * Atlassian Support portal and related service desks * Authentication and user management flows ScriptRunner for Jira and Confluence Cloud, Enhanced Search and Behaviours functionality were indirectly affected through Atlassian platform dependencies (e.g., API latency and Marketplace licensing validation), though no internal ScriptRunner infrastructure outage occurred. AWS mitigated the underlying DNS issue in US-EAST-1, after which Atlassian restored full functionality across affected products. Atlassian has confirmed full recovery of core services, with residual monitoring on migrations and JSM virtual service agents still ongoing. We apologise for any inconvenience caused.

Read the full incident report →