- Detected by Pingoru
- Aug 07, 2026, 11:30 AM UTC
- Resolved
- Aug 07, 2026, 12:52 PM UTC
- Duration
- 1h 21m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 3 updates
-
investigating Aug 07, 2026, 11:30 AM UTC
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
-
monitoring Aug 07, 2026, 12:22 PM UTC
Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
-
resolved Aug 07, 2026, 12:52 PM UTC
On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 11:30 AM UTC
- Resolved
- Aug 07, 2026, 12:52 PM UTC
- Duration
- 1h 21m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 3 updates
-
investigating Aug 07, 2026, 11:30 AM UTC
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
-
monitoring Aug 07, 2026, 12:22 PM UTC
Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
-
resolved Aug 07, 2026, 12:52 PM UTC
On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 11:30 AM UTC
- Resolved
- Aug 07, 2026, 12:52 PM UTC
- Duration
- 1h 21m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 3 updates
-
investigating Aug 07, 2026, 11:30 AM UTC
We are investigating issues affecting your services. We are actively working to identify the cause and resolve the issue. We will provide further updates within one hour.
-
monitoring Aug 07, 2026, 12:22 PM UTC
Some customers experienced issues accessing affected services in the Central European region. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
-
resolved Aug 07, 2026, 12:52 PM UTC
On August 7th - 2026, between 10:27 UTC to 11:49 UTC, some users in the Central European region may have experienced service access issues. The issue has now been resolved and the service is operating normally for all the customers.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:33 AM UTC
- Resolved
- Aug 07, 2026, 01:46 AM UTC
- Duration
- 13m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 3 updates
-
investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
-
resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:33 AM UTC
- Resolved
- Aug 07, 2026, 01:46 AM UTC
- Duration
- 13m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 3 updates
-
investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
-
resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:26 AM UTC
- Resolved
- Aug 07, 2026, 01:46 AM UTC
- Duration
- 19m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
-
investigating Aug 07, 2026, 01:26 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
-
resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:26 AM UTC
- Resolved
- Aug 07, 2026, 01:46 AM UTC
- Duration
- 19m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
-
investigating Aug 07, 2026, 01:26 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
-
resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Aug 07, 2026, 01:24 AM UTC
- Resolved
- Aug 07, 2026, 01:46 AM UTC
- Duration
- 21m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 5 updates
-
investigating Aug 07, 2026, 01:24 AM UTC
We are actively investigating reports of performance degradation affecting JIRA. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
investigating Aug 07, 2026, 01:26 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
investigating Aug 07, 2026, 01:33 AM UTC
We are actively investigating reports of performance degradation affecting JIRA and JSM. Affected users may experience errors viewing issues and boards. We will share updates here as more information is available.
-
monitoring Aug 07, 2026, 01:39 AM UTC
The performance degradation of JIRA has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
-
resolved Aug 07, 2026, 01:46 AM UTC
On August 7, 2026, JIRA, JWM, and JSM users may have experienced performance degradation when viewing issues and boards. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Aug 03, 2026, 03:26 AM UTC
- Resolved
- Aug 03, 2026, 03:37 AM UTC
- Duration
- 11m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags EvaluationsForge Object Store
Timeline · 2 updates
-
investigating Aug 03, 2026, 03:26 AM UTC
Our team is aware of an issue that was impacting the ability to install, uninstall or manage Forge and OAuth 2.0 integrated apps between 2026-08-03 01:47 UTC and 02:29 UTC. Apps that were already installed should have continued to run as normal during this impact window. We believe we have now rectified this issue and are monitoring for ongoing impact. We apologize for any inconvenience this may have caused.
-
resolved Aug 03, 2026, 03:37 AM UTC
We have confirmed that the issues relating to installing, uninstalling and managing Forge and OAuth 2.0 apps should now be fully resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 31, 2026, 01:09 PM UTC
- Resolved
- Jul 31, 2026, 03:38 PM UTC
- Duration
- 2h 28m
Affected: WebsiteAPIGit via SSHAuthentication and user managementGit via HTTPSWebhooksSource downloadsPipelinesGit LFSEmail deliveryPurchasing & LicensingSignupPackages
Timeline · 3 updates
-
monitoring Jul 31, 2026, 01:09 PM UTC
Some customers experienced intermittent errors when accessing Bitbucket Cloud, including failures loading the site and associated impacts to Pipelines. We have been able to apply the fix to mitigate the issues and we are seeing recovery. We continue to monitor the situation and should be fully recovered soon. We should be able to provide more updates in the next one hour or earlier.
-
monitoring Jul 31, 2026, 02:28 PM UTC
A fix has been implemented and services are operating normally for all affected customers. We are continuing to monitor to confirm stability. We will provide a further update within 60 minutes.
-
resolved Jul 31, 2026, 03:38 PM UTC
On July 31, 2026, affected Bitbucket Cloud users for some customers may have experienced failures loading the site and impacts to associated pipelines. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 09:48 AM UTC
- Resolved
- Jul 24, 2026, 01:07 PM UTC
- Duration
- 3d 3h
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 3 updates
-
identified Jul 21, 2026, 09:48 AM UTC
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
-
identified Jul 22, 2026, 06:59 AM UTC
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
-
resolved Jul 24, 2026, 01:07 PM UTC
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 09:48 AM UTC
- Resolved
- Jul 24, 2026, 01:07 PM UTC
- Duration
- 3d 3h
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 3 updates
-
identified Jul 21, 2026, 09:48 AM UTC
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
-
identified Jul 22, 2026, 06:59 AM UTC
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
-
resolved Jul 24, 2026, 01:07 PM UTC
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Read the full incident report →
- Detected by Pingoru
- Jul 21, 2026, 09:48 AM UTC
- Resolved
- Jul 24, 2026, 01:07 PM UTC
- Duration
- 3d 3h
Affected: Incident FlowIncident FlowAlert FlowAlert FlowEmail Notification DeliveryEmail Notification DeliveryPublic WebsiteSMS Notification DeliverySMS Notification DeliveryVoice Notification DeliveryVoice Notification DeliveryMobile Notification DeliveryMobile Notification DeliveryHeartbeat MonitoringHeartbeat MonitoringIncident REST APIIncident REST APIAlert REST APIAlert REST APIHeartbeat REST APIHeartbeat REST APIIncoming Email ServiceIncoming Email ServiceIncoming Integration FlowIncoming Integration FlowOutgoing Integration FlowOutgoing Integration FlowSignup, Login & AuthorizationSignup, Login & AuthorizationOpsgenie ActionsOpsgenie ActionsWeb ApplicationWeb ApplicationMobile ApplicationMobile ApplicationConfiguration REST APIsConfiguration REST APIsReporting & AnalyticsReporting & AnalyticsPricing & BillingPricing & BillingLogsLogsIncoming Call RoutingIncoming Call Routing
Timeline · 3 updates
-
identified Jul 21, 2026, 09:48 AM UTC
We are working with our notification provider to resolve the issue. We will provide another update in 24 hours or as soon as more information becomes available.
-
identified Jul 22, 2026, 06:59 AM UTC
A small number of voice notifications for Jira Service Management and Opsgenie customers using India based mobile numbers may fail. Customers may see failed voice call logs and not receive the expected paging call. Our 3rd party notification provider is actively working towards restoring the voice notification delivery and we will provide updates once the issue is resolved. If you need any further support or information, please reach out to our support team.
-
resolved Jul 24, 2026, 01:07 PM UTC
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 08:18 PM UTC
- Resolved
- Jul 22, 2026, 12:56 AM UTC
- Duration
- 1d 4h
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 4 updates
-
investigating Jul 20, 2026, 08:18 PM UTC
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
-
investigating Jul 20, 2026, 09:27 PM UTC
Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available.
-
identified Jul 21, 2026, 04:53 AM UTC
The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in place.
-
resolved Jul 22, 2026, 12:56 AM UTC
Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 08:18 PM UTC
- Resolved
- Jul 22, 2026, 12:56 AM UTC
- Duration
- 1d 4h
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 4 updates
-
investigating Jul 20, 2026, 08:18 PM UTC
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
-
investigating Jul 20, 2026, 09:27 PM UTC
Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available.
-
identified Jul 21, 2026, 04:53 AM UTC
The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in place.
-
resolved Jul 22, 2026, 12:56 AM UTC
Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 20, 2026, 08:18 PM UTC
- Resolved
- Jul 22, 2026, 12:56 AM UTC
- Duration
- 1d 4h
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 4 updates
-
investigating Jul 20, 2026, 08:18 PM UTC
We are actively investigating reports of performance degradation affecting Automation rules for Jira and Jira Service Management. We will share updates here as more information is available.
-
investigating Jul 20, 2026, 09:27 PM UTC
Our teams are continuing to investigate delays in Jira and Jira Service Management automation rule executions for some customers. We are seeing signs of improvement, but affected users may still experience delays. We'll share updates here as more information is available.
-
identified Jul 21, 2026, 04:53 AM UTC
The team has identified a root cause and after initial testing, is now enacting scaling changes to help to prevent these rule execution delays. We'll monitor performance over the next 24 hours and provide an update at that time or sooner if we can confirm the improvement is in place.
-
resolved Jul 22, 2026, 12:56 AM UTC
Our team has been able to validate that all rule executions are performing normally and this issue is now resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 13, 2026, 03:48 PM UTC
- Resolved
- Jul 13, 2026, 05:46 PM UTC
- Duration
- 1h 57m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags EvaluationsForge Object Store
Timeline · 3 updates
-
investigating Jul 13, 2026, 03:48 PM UTC
Marketplace partner pages are unavailable. Partners are unable to access dashboards and management interfaces, experiencing timeouts when attempting to load these pages. All partner-related functionality is affected. Investigation into the underlying cause is underway. Next comms will be sent in 60 minutes or upon significant progress.
-
monitoring Jul 13, 2026, 05:17 PM UTC
The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.
-
resolved Jul 13, 2026, 05:46 PM UTC
On Jul 13, 2026, partner operations may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 04:11 PM UTC
- Resolved
- Jul 06, 2026, 06:52 PM UTC
- Duration
- 2h 40m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 10:04 AM UTC
- Resolved
- Jul 06, 2026, 01:04 PM UTC
- Duration
- 2h 59m
Affected: Customer experienceCustomer Service Management AI agentSupport websiteEmail requestCustomer Service Management spacesCustomer profilesAutomation for Jira
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 09:23 AM UTC
- Resolved
- Jul 06, 2026, 01:04 PM UTC
- Duration
- 3h 40m
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 09:23 AM UTC
- Resolved
- Jul 06, 2026, 01:04 PM UTC
- Duration
- 3h 40m
Affected: View ContentiOS AppCreate and EditAndroid AppCommentsAuthentication and User ManagementSearchAdministrationNotificationsMarketplace AppsPurchasing & LicensingSignupConfluence AutomationsCloud to Cloud Migrations - Copy Product DataServer to Cloud Migrations - Copy Product Data
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 09:23 AM UTC
- Resolved
- Jul 06, 2026, 01:04 PM UTC
- Duration
- 3h 40m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jul 06, 2026, 09:23 AM UTC
- Resolved
- Jul 06, 2026, 01:04 PM UTC
- Duration
- 3h 40m
Affected: Jira Service Management WebService PortalOpsgenie Incident FlowOpsgenie Alert FlowOpsgenie Incident FlowOpsgenie Alert FlowJira Service Management Email RequestsAuthentication and User ManagementPurchasing & LicensingSignupAutomation for JiraAssistAssets
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jun 30, 2026, 02:45 AM UTC
- Resolved
- Jul 02, 2026, 04:43 AM UTC
- Duration
- 2d 1h
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags EvaluationsForge Object Store
Timeline · 2 updates
-
investigating Jun 30, 2026, 02:45 AM UTC
We are aware that some customers that are using the Time Tracker for Jira Cloud and DC app were incorrectly notified about the app converting to a free or a trial subscription. Our team is investigating this issue with urgency, and we will plan to notify any customers that received the incorrect email with a correction. There is no action required from those customers that have incorrectly received these emails. We apologize for any inconvenience this may have caused.
-
resolved Jul 02, 2026, 04:43 AM UTC
All customers that had previously received the incorrect notifications about the Time Tracker for Jira Cloud and DC app should have received corrective communications at this time. We are now resolving this issue.
Read the full incident report →
- Detected by Pingoru
- Jun 26, 2026, 02:32 PM UTC
- Resolved
- Jun 26, 2026, 09:39 PM UTC
- Duration
- 7h 6m
Affected: Bitbucket Cloud APIsApp listing managementApp DeploymentApp listingsConfluence Cloud APIsArtifactory (Maven repository)Atlassian Support contact formApp pricingJira Cloud APIsCreate and manage appsDeveloper communityDeveloper documentationDeveloper service deskApp submissionsAuthentication and user managementProduct EventsMarketplace service deskUser APIsCategory landing pagesForge App InstallationWebhooksEvaluations and purchasesAtlassian SupportForge CDN (Custom UI)In-product Marketplace and app installation (Cloud)Forge Function InvocationWeb TriggersVulnerability management [AMS]In-product Marketplace and app installation (Server)aui-cdn.atlassian.comNotificationsForge App LogsPrivate listingsForge App MonitoringReporting APIs and dashboardsDeveloper consoleSearchForge direct app distributionVendor managementHosted storageVendor Home PageForge CLIEnd-user consentForge App AlertsApp Data ResidencyForge SQLForge MonetisationForge Feature Flags Evaluations
Timeline · 5 updates
-
identified Jun 26, 2026, 02:32 PM UTC
We have identified the source of service performance issues, affecting your forge remote-apps services. Our team has initiated a remediation and is actively monitoring recovery. We will provide the next update within the next one hour.
-
identified Jun 26, 2026, 03:28 PM UTC
Our team has applied the mitigation, and we are seeing recovery. We will continue to share additional updates here as more information becomes available.
-
identified Jun 26, 2026, 07:43 PM UTC
Our team continues to monitor the recovery in progress, and we will share additional updates here as more information becomes available.
-
monitoring Jun 26, 2026, 09:24 PM UTC
The issue has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor closely to confirm stability.
-
resolved Jun 26, 2026, 09:39 PM UTC
On June 26, 2026, some customers may have experienced performance degradation with remote Forge apps facing rate-limiting issues. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
