- 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 · 5 updates
-
investigating Jul 06, 2026, 04:11 PM UTC
We are actively investigating reports of performance degradation affecting Automation for JIRA. We will share updates here as more information is available.
-
investigating Jul 06, 2026, 05:12 PM UTC
We continue to investigate performance degradation affecting Automation for JIRA in Europe regions. We will share updates here as more information becomes available.
-
identified Jul 06, 2026, 05:57 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience performance degradation affecting Automation for JIRA in Europe regions. We will continue to share additional updates here as more information is available.
-
monitoring Jul 06, 2026, 06:41 PM UTC
The performance degradation of Automation for JIRA in Europe regions has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.
-
resolved Jul 06, 2026, 06:52 PM UTC
On July 6, 2026, some users in Europe regions may have experienced performance degradation with Automation for JIRA. The issue has now been resolved, and the service is operating normally for all affected customers. If you believe the issue continues to persist, please contact our Support team for further assistance and troubleshooting.
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 →
- Detected by Pingoru
- Jun 19, 2026, 10:46 PM UTC
- Resolved
- Jun 26, 2026, 05:13 AM UTC
- Duration
- 6d 6h
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 · 2 updates
-
monitoring Jun 19, 2026, 10:46 PM UTC
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.
-
resolved Jun 26, 2026, 05:13 AM UTC
Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 10:46 PM UTC
- Resolved
- Jun 26, 2026, 05:13 AM UTC
- Duration
- 6d 6h
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 · 2 updates
-
monitoring Jun 19, 2026, 10:46 PM UTC
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.
-
resolved Jun 26, 2026, 05:13 AM UTC
Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2026, 10:46 PM UTC
- Resolved
- Jun 26, 2026, 05:13 AM UTC
- Duration
- 6d 6h
Affected: Viewing contentCreate and editAuthentication and User ManagementSearchNotificationsAdministrationMarketplaceMobilePurchasing & LicensingSignupAutomation for Jira
Timeline · 2 updates
-
monitoring Jun 19, 2026, 10:46 PM UTC
Jira and JSM customers using Microsoft OAuth for automatic creation of Jira tickets from email were unable to read email. This is now fixed and functional for all new incoming email processing. The impacted customers during the incident period need to re-authorise the Microsoft mail server to restore and below are the instructions. To re-authorise an incoming Microsoft mail server: Login in Jira as Admin Select > System Select Mail > Incoming Mail. Select Edit incoming mail server. Select re-authorise . Enter your Microsoft credentials to continue using your Microsoft mail server.
-
resolved Jun 26, 2026, 05:13 AM UTC
Our team has proactively reached out to all impacted organizations providing the below instructions to re-authorize their Microsoft mail server. If you are still experiencing this issue, please attempt to complete the re-authorization as advised below. If further issues still occur that you believe to be related to this incident, please reach out to Atlassian support for further assistance.
Read the full incident report →
- Detected by Pingoru
- Jun 16, 2026, 01:46 PM UTC
- Resolved
- Jun 16, 2026, 03:56 PM UTC
- Duration
- 2h 9m
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 · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 05:44 PM UTC
- Resolved
- Jun 17, 2026, 05:00 PM UTC
- Duration
- 1d 23h
Affected: AgentsStudio
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 01:50 PM UTC
- Resolved
- Jun 12, 2026, 02:29 PM UTC
- Duration
- 38m
Affected: Open projectsCreate and delete fieldsAdd/view data points ("Capture")
Timeline · 2 updates
-
monitoring Jun 12, 2026, 01:50 PM UTC
We are investigating reports of incomplete or missing field data in Jira Product Discovery views, including list, timeline, and single idea views. A limited number of customers are affected. Your data is safe, this is a display issue only. We have identified the root cause and a fix is being deployed. We will provide an update once recovery is confirmed.
-
resolved Jun 12, 2026, 02:29 PM UTC
On June 12th 2026, between 07:30 UTC to 13:48 UTC, some users experienced viewing disruptions with our product discovery service. The issue has now been resolved and the service is operating normally for all the customers.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2026, 08:45 AM UTC
- Resolved
- Jun 12, 2026, 11:15 AM UTC
- Duration
- 2h 29m
Affected: View ContentCreate and Edit
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2026, 10:48 PM UTC
- Resolved
- Jun 12, 2026, 12:14 AM UTC
- Duration
- 1h 26m
Affected: WebsiteAPIGit via SSHAuthentication and user managementGit via HTTPSWebhooksSource downloadsPipelinesGit LFSEmail deliveryPurchasing & LicensingSignupPackages
Timeline · 4 updates
-
investigating Jun 11, 2026, 10:48 PM UTC
We are actively investigating reports of performance degradation affecting Bitbucket OAuth login. We will share updates here as more information is available.
-
identified Jun 11, 2026, 11:21 PM UTC
We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience OAuth login issues in Bitbucket. We will continue to share additional updates here as more information is available.
-
monitoring Jun 11, 2026, 11:58 PM UTC
The performance degradation of Bitbucket has been resolved, and services are now operating normally for all affected customers. We will continue to monitor performance closely to confirm stability.
-
resolved Jun 12, 2026, 12:14 AM UTC
On June 11, 2026, Bitbucket users may have experienced performance degradation affecting Bitbucket OAuth login. The issue has now been resolved, and the service is operating normally for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 09:42 AM UTC
- Resolved
- Jun 10, 2026, 10:00 AM UTC
- Duration
- 17m
Affected: Jira Service Management Web
Timeline · 2 updates
-
investigating Jun 10, 2026, 09:42 AM UTC
Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.
-
resolved Jun 10, 2026, 10:00 AM UTC
On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.
Read the full incident report →
- Detected by Pingoru
- Jun 10, 2026, 09:42 AM UTC
- Resolved
- Jun 10, 2026, 10:00 AM UTC
- Duration
- 17m
Affected: Jira Service Management Web
Timeline · 2 updates
-
investigating Jun 10, 2026, 09:42 AM UTC
Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.
-
resolved Jun 10, 2026, 10:00 AM UTC
On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets. We have implemented a fix and services have been restored to normal operation for all affected customers.
Read the full incident report →
