Mar 21, 01:42 UTC
Resolved - This incident has been resolved.
Mar 21, 00:58 UTC
Update - We have observed success rates return to normal for Claude Opus 4.6, and are working to fully resolve elevated errors for Claude Sonnet 4.6.
Mar 21, 00:17 UTC
Identified - We have identified an issue resulting in elevated errors on both Claude Opus and Sonnet 4.6, and are working to resolve this issue as quickly as possible.
Mar 21, 00:07 UTC
Investigating - We are currently investigating elevated error rates affecting Claude Opus 4.6. Our team is actively working to identify the root cause.
Mar 19, 16:16 UTC
Resolved - This incident started at 8:53 PT / 15:53 UTC and the errors have now returned to baseline since 9:14 PT / 16:14 UTC.
Mar 19, 15:59 UTC
Investigating - We are currently investigating this issue.
Mar 19, 15:46 UTC
Resolved - As of 8:42 PT / 15:42 UTC the error rate has now returned to baseline.
Mar 19, 15:37 UTC
Investigating - We are currently investigating elevated errors that started at 8:23 PT / 15:23 UTC.
Mar 19, 01:38 UTC
Resolved - This incident has been resolved.
Mar 19, 01:21 UTC
Monitoring - From 23:59–00:30 UTC, users experienced elevated errors when trying to authenticate across various Claude surfaces including Claude.ai and Claude Code. This issue has been resolved, and we are monitoring closely to ensure no further issues.
Mar 19, 00:28 UTC
Investigating - We are currently investigating this issue. Our team is actively working to identify the root cause.
Mar 18, 16:05 UTC
Resolved - This incident has been resolved.
Mar 18, 15:27 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 18, 15:19 UTC
Update - Claude Code login/logout actions are also affected by this outage.
Mar 18, 15:16 UTC
Investigating - We are currently investigating this issue.
Mar 18, 16:00 UTC
Resolved - On March 18, 2026, customers using workflows configured with serial groups or terminal job dependencies experienced two brief periods of disruption due to a code change.
Between approximately 12:08 and 12:35 UTC, affected pipelines encountered errors when creating workflows. For pipelines created in a second window from approximately 14:23 to 14:35 UTC, GitHub status updates were not delivered for some completed jobs. Long-running workflows triggered during this window may encounter these errors after the resolution time. The underlying change was reverted in both cases.
All systems have been operating normally since 14:35 UTC.
Mar 16, 03:52 UTC
Resolved - Our engineering team has identified the root cause and has fixes prepared. Due to the nature of the data refresh process, the fix will require a deployment followed by a full refresh cycle before data is fully up to date. We expect that the data should be available within 24-36 hours. The last-24-hours reporting window continues to work normally, and all pipeline pages and job runs remain unaffected.
Mar 16, 03:02 UTC
Investigating - We are investigating an issue where the Insights API and dashboard are returning outdated metrics for reporting windows longer than 24 hours (last 7 days, last 30 days, last 60 days, last 90 days). The last-24-hours window is unaffected and returning current data.
This issue is limited to the display of aggregated metrics on Insights Page only. All pipeline pages, job runs, and builds remain fully operational and are not impacted. We will provide updates as our investigation progresses.
Mar 11, 02:24 UTC
Resolved - The issue affecting the orb list on the Organization Settings page has been resolved. Our engineers have deployed a fix and users should now be able to view their orb list as expected. Orb usage in pipelines and builds was not impacted during this incident. If you continue to experience issues, please contact CircleCI support.
Thank you for your patience while we worked on resolving this issue.
Mar 11, 01:58 UTC
Investigating - We are investigating an issue where users are unable to view their organization's orb list on the Organization Settings page. The page may appear blank or fail to load the expected list of public and private orbs. Other CircleCI functionality, including pipeline execution and orb usage in builds, is not affected. Our engineering team is actively investigating and working toward a resolution. We will provide an update within 30 minutes.
Mar 2, 18:21 UTC
Resolved - Looks like everything is good. Thank you for your patience.
Mar 2, 18:15 UTC
Monitoring - The fix has gone out. We will continue to monitor the situation. Sorry for any inconvenience.
Mar 2, 17:59 UTC
Identified - We're seeing issues with docker on some convenience images (cimg:*) and a docker update we just pushed this morning. We are working on a fix and will let you know when we have more information. Thank you for your patience.
Feb 27, 00:17 UTC
Resolved - GitHub have acknowledged and resolved an incident affecting their platform.
https://www.githubstatus.com/incidents/vd3xqfq36rgm
Users should no longer experience intermittent checkout failures.
Feb 26, 22:57 UTC
Update - We are continuing to investigate this issue.
Feb 26, 22:56 UTC
Update - We are continuing to investigate this issue.
Feb 26, 22:50 UTC
Identified - Some users are currently experiencing inconsistent failures when checking out.
We believe this to be an issue with an upstream VCS provider and are investigating.
Mar 21, 08:45 UTC
Resolved - This incident has been resolved.
Mar 21, 06:28 UTC
Update - We are continuing to work on a fix for this issue.
Mar 20, 15:30 UTC
Update - We are continuing for work on a fix for this issue
Mar 20, 13:28 UTC
Update - We are continuing for work on a fix for this issue
Mar 20, 12:17 UTC
Update - We are continuing for work on a fix for this issue
Mar 20, 11:21 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 20, 11:09 UTC
Investigating - Cloudflare is investigating issues with Network Performance for customers in the Jakarta area
We are working to analyze and mitigate this problem. More updates to follow shortly.
Mar 19, 15:57 UTC
Resolved - This incident has been resolved.
Mar 19, 15:54 UTC
Investigating - Cloudflare Pages API is seeing increased error rate. This affects the Workers & Pages section in the Cloudflare Dashboard, as well as Workers Builds.
Deployed Workers and Pages projects are unaffected
Mar 19, 15:56 UTC
Resolved - This incident has been resolved.
Mar 19, 15:29 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 19, 14:38 UTC
Update - Cloudflare is continuing to investigate an increased rate of HTTP 530 errors, specifically affecting traffic across a limited number of TLDs routed through our Atlanta (ATL) data center.
We are working to identify the root cause and will provide updates as they become available.
Mar 19, 11:36 UTC
Investigating - Cloudflare is investigating an increased rate of HTTP 530 errors specifically affecting traffic routed through our Atlanta (ATL) data center.
We are working to identify the root cause and will provide updates as they become available.
Mar 19, 09:29 UTC
Resolved - This incident has been resolved.
Mar 19, 08:43 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 19, 08:37 UTC
Investigating - Cloudflare is investigating network performance issues that may impact a subset of users in Mumbai, India.
Some users may experience increased latency or intermittent errors. We are actively working to mitigate this problem.
More updates to follow shortly.
Mar 20, 18:18 UTC
Monitoring - Linode has confirmed that the connectivity issues in their Jakarta region have been addressed. Their team will continue to monitor the situation to ensure stability.
Mar 20, 11:42 UTC
Identified - Our upstream provider, Linode, is currently experiencing a partial outage in their Jakarta region. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.
Mar 17, 09:20 UTC
Resolved - The issue has been resolved. Please contact our support if you continue to experience any related issues.
Mar 16, 22:37 UTC
Monitoring - Storage service is stable and fully restored. Our team continues to monitor system performance.
Mar 16, 21:06 UTC
Investigating - Some Cloudways Autonomous applications hosted in the US region may experience temporary connectivity issues due to a partial disruption in the underlying storage service. Our team is actively working with the infrastructure provider to restore full stability as quickly as possible.
Mar 9, 19:11 UTC
Update - We are still working closely with AWS to resolve this issue. AWS services remain impacted, and our team continues to monitor the situation and coordinate with AWS for a resolution. We will share further updates on this status page as more information becomes available. We sincerely apologize for the inconvenience caused and appreciate your patience.
Mar 2, 18:28 UTC
Update - AWS is currently experiencing a power outage affecting two of its three data centers in Bahrain. The remaining center is currently over capacity, leading to widespread service failures. Since backups are hosted in the same region, recovery is dependent on AWS restoring local power and connectivity. We are monitoring the situation 24/7 and will update you the moment services begin to recover.
Mar 2, 08:05 UTC
Identified - Our upstream provider, Amazon Web Services (AWS), is currently experiencing a connectivity and power outage in the Bahrain region, impacting instances hosted in the ME-SOUTH-1 region.
Their technical teams are actively investigating the issue and working to restore services as quickly as possible. We regret the inconvenience this may cause.
Mar 9, 19:10 UTC
Update - We are still working closely with AWS to resolve this issue. AWS services remain impacted, and our team continues to monitor the situation and coordinate with AWS for a resolution. We will share further updates on this status page as more information becomes available. We sincerely apologize for the inconvenience caused and appreciate your patience.
Mar 2, 18:30 UTC
Identified - AWS is reporting a power outage affecting two Availability Zones in the UAE region. The massive load on the remaining zone is causing widespread disruptions. As backups are localized to this region, they are also impacted. We are tracking AWS updates closely and will notify you as soon as the service is restored.
Mar 1, 13:53 UTC
Investigating - Our upstream provider, Amazon Web Services (AWS), is currently experiencing a connectivity and power outage in the UAE region, impacting instances hosted in the ME-CENTRAL-1 region.
Their technical teams are actively investigating the issue and working to restore services as quickly as possible. We regret the inconvenience this may cause.
Feb 13, 07:16 UTC
Resolved - The issue has been resolved. Please contact our support if you continue to experience any related issues.
Feb 12, 22:47 UTC
Monitoring - Storage service is stable and fully restored. Our team continues to monitor system performance.
Feb 12, 14:48 UTC
Update - We are continuing to investigate this issue.
Feb 12, 14:43 UTC
Investigating - Some Cloudways Autonomous applications hosted in the London region may experience temporary connectivity issues due to a partial disruption in the underlying storage service. Our team is actively working with the infrastructure provider to restore full stability as quickly as possible.
Mar 19, 18:54 UTC
Resolved - The issue is fully resolved.
Mar 19, 18:49 UTC
Monitoring - We have confirmed that customers are seeing resolution of the issue, and are currently monitoring for further confirmation.
Mar 19, 18:42 UTC
Identified - We have identified a possible cause of the SSO login error, and are addressing it now.
Mar 19, 18:36 UTC
Investigating - We're currently investigating reports of SSO login errors.
Mar 13, 13:13 UTC
Resolved - The issue has been resolved
Mar 13, 12:41 UTC
Investigating - We've spotted that something has gone wrong. The Optimization page is not loading. We're currently investigating the issue, and will provide an update soon.
Mar 12, 18:29 UTC
Resolved - This issue is fully resolved.
Mar 12, 18:00 UTC
Monitoring - The issue which caused the error spike on the Contentful Management API (CMA) has resolved. We are continuing to monitor.
Mar 12, 17:48 UTC
Investigating - We observed a high amount of CMA errors in the past 15 minutes. The errors have already subsided but we are actively investigating the problem.
Mar 3, 13:47 UTC
Resolved - This issue should now be resolved for all customers.
Mar 3, 13:01 UTC
Monitoring - We have identified the issue and customers should see errors reduced to normal levels.
Mar 3, 12:25 UTC
Investigating - Some customers may be seeing elevated error rates from Contentful APIs. We are currently investigating the issue.
Feb 17, 22:16 UTC
Resolved - The issue has been resolved.
Feb 17, 22:07 UTC
Monitoring - We have resolved the issue and are monitoring the situation.
Feb 17, 21:54 UTC
Identified - We are still observing issues for some customers and are working on a resolution.
Feb 17, 21:33 UTC
Monitoring - We addressed the issue and are monitoring the situation.
Feb 17, 20:55 UTC
Identified - Some customers will find certain features like e.g. Studio disabled. We have identified the issue and are working on a fix.
Feb 12, 15:22 EST
Resolved - This incident has been resolved.
Feb 12, 14:55 EST
Monitoring - A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector.
Feb 12, 14:10 EST
Investigating - We are currently investigating an issue impacting Microsoft Excel and Sharepoint connectors on the platform.
At this time, customers who encounter connector errors are unable to successfully reconnect to Microsoft. Once the error appears, reconnection attempts are failing, and affected connectors remain blocked.
Our team is actively working to identify the root cause and restore reconnection functionality as quickly as possible.
We will provide updates here as soon as more information becomes available.
Feb 4, 15:27 EST
Resolved - The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored.
Feb 2, 15:58 EST
Identified - We have identified the cause of the issue impacting form submission redirects.
Our engineering team is actively working on a fix, which will be implemented as soon as possible. We will continue to provide updates here as progress is made.
Feb 2, 15:27 EST
Investigating - We are currently investigating an issue where some form submissions are not redirecting respondents as expected after submission.
Under normal circumstances, respondents are redirected back to the form if there is a validation or connector error, allowing them to correct their information and resubmit. If no errors occur, respondents are redirected to the configured thank-you page or redirect URL.
Some submissions may remain on the response processing page and display a default confirmation message instead of submissions displaying potential errors.
Our team is actively investigating the root cause of this issue. We will continue to post updates here as more information becomes available.
Jan 29, 09:51 EST
Resolved - We experienced processing delays with Salesforce connectors in the London region due to increased system load. Our team has upgraded system capacity and the issue is now resolved. All connectors are operating normally.
Jan 23, 14:11 EST
Resolved - This incident has been resolved. Please reach out to [email protected] if you run into any further issues.
Jan 22, 10:00 EST
Identified - We confirmed a secondary issue related to yeseterday's SAML concern where SAML authenticated forms are not preserving URL query parameters after authentication. The team has identified the root cause and is working to resolve the issue. Additional details will be provided here as they become available.
Jan 21, 18:02 EST
Resolved - The issue impacting SAML authentication has been fully resolved. Respondents can now access SAML-authenticated forms as expected, and SAML-based login is functioning normally.
Our team has confirmed service restoration and is continuing to monitor the system to ensure stability. Thank you for your patience while we worked to resolve this issue.
Jan 21, 16:52 EST
Identified - The issue impacting SAML authentication has been identified, and a fix is currently being implemented. Some respondents may still be unable to access SAML-authenticated forms, and SAML-based login may continue to be affected during this time.
Our engineering team is actively deploying the fix and monitoring the situation closely. We will provide another update once the fix has been fully applied and we’ve confirmed service restoration.
Jan 21, 15:40 EST
Investigating - We are currently investigating an issue that is impacting SAML authentication. At this time, some respondents are unable to access SAML-authenticated forms. This issue may also affect SAML-based login.
Our engineering team is actively working to identify the root cause and implement a fix. We will provide updates as more information becomes available.
Mar 20, 01:58 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Mar 20, 01:26 UTC
Update - We are rolling out our mitigation and are seeing recovery.
Mar 20, 01:00 UTC
Update - We are seeing widespread issues starting and viewing Copilot Agent sessions. We understand the cause and are working on remediation.
Mar 20, 00:58 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 20, 00:05 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Mar 20, 00:05 UTC
Update - We have reached stability with git operations through our changes deployed today.
Mar 19, 23:52 UTC
Update - We are seeing early signs of improvement. We are working on one more small change to further improve traffic routing on the west coast.
Mar 19, 22:57 UTC
Update - We have completed the rollout of our new network path and are monitoring its impact.
Mar 19, 21:59 UTC
Update - We are beginning the rollout of our new network path. During this change, users will continue to see higher latency from the west coast. We will provide another update when the rollout is complete.
Mar 19, 18:27 UTC
Update - We are working to enable a new network path in the west coast to reduce load and will monitor the impact on latency for Git Operations
Mar 19, 17:49 UTC
Update - We are still seeing elevated latency for Git operations in the west coast and are continuing to investigate
Mar 19, 17:01 UTC
Update - We are redirecting traffic back to our Seattle region and customers should see a decrease in latency for Git operations
Mar 19, 16:25 UTC
Investigating - We are investigating reports of degraded performance for Git Operations
Mar 19, 14:32 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Mar 19, 14:06 UTC
Update - Copilot is operating normally.
Mar 19, 14:02 UTC
Update - We are investigating reports that Copilot Coding Agent session logs are not available in the UI.
Mar 19, 13:45 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Mar 19, 13:44 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 19, 02:52 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Mar 19, 02:46 UTC
Update - We have rolled out our mitigation and are seeing recovery for Copilot Coding Agent sessions
Mar 19, 02:25 UTC
Update - We are seeing widespread issues starting and viewing Copilot Agent sessions. We have a hypothesis for the cause and are working on remediation.
Mar 19, 02:05 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 19, 01:44 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Mar 19, 01:43 UTC
Update - We are seeing recovery in git operations for customers on the West Coast of the US.
Mar 19, 00:56 UTC
Update - We continue to investigate the slow performance of Git Operations affecting the US West Coast.
Mar 19, 00:10 UTC
Update - We continue to investigate degraded performance for git operations from the US West Coast.
Mar 18, 23:33 UTC
Update - We are continuing to investigate degraded performance for git operations from the US West Coast.
Mar 18, 22:48 UTC
Update - We are experiencing increased latency when performing git operations, especially large pushes and pulls from customers on the west coast of the US. We are not seeing an increase in failures. We are continuing to investigate.
Mar 18, 22:36 UTC
Update - Git Operations is experiencing degraded performance. We are continuing to investigate.
Mar 18, 22:36 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Mar 19, 15:41 EDT
Resolved - We've addressed the issue that caused saved views to disappear upon page refresh or tab change from 9:39 AM EDT (UTC -04:00) until 10:21 AM EDT on Mar 19, 2026. No views were lost but any view tabs will need to be re-added by users.
HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Mar 19, 15:31 EDT
Monitoring - We've addressed the issue that caused saved views to disappear upon page refresh or tab change from 9:39 AM EDT (UTC -04:00) until 10:21 AM EDT on Mar 19, 2026. No views were lost but any view tabs will need to be re-added by users.
HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Mar 5, 07:26 EST
Resolved - The affected areas of HubSpot are now fully accessible. We've identified and addressed the root cause of the issue. The incident has been fully resolved and The affected areas of HubSpot should be working properly. No data was lost.
Mar 5, 07:12 EST
Monitoring - We've addressed the issue that caused multiple areas in HubSpot to be unavailable since 6:00 AM EST (UTC -05:00) on Mar 5, 2026. We're monitoring performance closely to ensure the tools recover properly. Only customers hosted in North America are currently impacted. We will be back with an update within 30 minutes.
Mar 5, 06:57 EST
Update - We've identified the issue that's caused multiple areas in HubSpot to be unavailable since 6:00 AM EST (UTC -05:00) on Mar 5, 2026. We're addressing the cause of this issue and will update this page when we have more information. Only customers hosted in North America are currently impacted. We will be back with an update within 30 minutes.
Mar 5, 06:53 EST
Update - We've identified the issue that's caused multiple areas in HubSpot to be unavailable since 6:15 AM EST (UTC -05:00) on Mar 5, 2026. We're addressing the cause of this issue and will update this page when we have more information. Only customers hosted in North America are currently impacted. We will be back with an update within 30 minutes.
Mar 5, 06:39 EST
Identified - We estimate that we will restore service in the next several hours.
We are mitigating impact from a server impairment which we believe is caused by resource exhaustion. We are reverting the change.
We will be back with an update within 1 hour.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Feb 25, 16:37 EST
Resolved - Workflows are now fully accessible. We've identified and addressed the root cause of the issue. The incident has been fully resolved and Workflows should be working properly. No data was lost.
Feb 25, 16:10 EST
Investigating - We are investigating an issue impacting workflows. We will provide an update when we have more information.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Feb 19, 13:54 EST
Resolved - CRM record creation is now fully accessible. We've identified and addressed the root cause of the issue. The incident has been fully resolved and CRM record creation should be working properly. No data was lost.
Feb 19, 13:53 EST
Monitoring - We've addressed the issue that caused CRM record creation to be unavailable since 1:11 PM EST (UTC -05:00) on Feb 19, 2026. We're monitoring performance closely to ensure the tools recover properly. We will be back with an update within 15 minutes.
Feb 18, 07:24 EST
Resolved - Between 08:48 AM (UTC +00:00) and 12:20 AM (UTC +00:00), many customers in all affected regions experienced issues with session invalidation. This was caused by a load balancer impairment. As of 12:20 AM (UTC +00:00), our session invalidation is working properly and the incident has been fully resolved.
HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Feb 18, 06:19 EST
Monitoring - We've addressed the issue that caused sessions to be invalidated in North America, Europe, the Asian Pacific since 08:48 AM (UTC +00:00). We're monitoring performance closely to ensure the tools recover properly.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Feb 18, 06:01 EST
Investigating - We are investigating an issue impacting session expirations and disconnections. We will provide an update when we have more information.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Mar 19, 04:08 UTC
Resolved - The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway.
We expect these remaining processes to be completed within approximately two hours, if not sooner.
Mar 18, 23:44 UTC
Update - Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.
Mar 18, 21:44 UTC
Update - We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.
Mar 18, 14:53 UTC
Update - We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.
Mar 18, 14:03 UTC
Monitoring - We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.
Mar 18, 14:01 UTC
Update - We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.
Mar 18, 13:07 UTC
Update - We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.
Mar 18, 12:24 UTC
Update - Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.
Mar 18, 11:32 UTC
Update - Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.
Mar 18, 11:32 UTC
Investigating - We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.
Mar 10, 00:59 UTC
Resolved - On 9 March UTC, Automation users in the APAC region may have experienced performance degradation within Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, Confluence. The issue has now been resolved, and the service is operating normally for all affected customers.
Mar 10, 00:51 UTC
Monitoring - The performance degradation of automations has been resolved, and services are now operating normally for all affected customers. We'll continue to monitor performance closely to confirm stability.
Mar 10, 00:15 UTC
Identified - Our team has now identified the cause of this issue relating to delayed automation events and has put a hotfix in place to help restore automation performance. We will continue to monitor performance as the backlog of issues is now being processed.
Mar 10, 00:06 UTC
Investigating - We are aware of customers experiencing delays with their automations within Jira, Jira Service Management, Jira Work Management, Jira Product Discovery and Confluence. Our team is investigating with urgency and we will provide an update within one hour.
Feb 26, 18:55 UTC
Resolved - On February 26, 2026, JSM experienced a disruption, and Atlassian Assist service was unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Feb 26, 18:33 UTC
Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Feb 26, 18:05 UTC
Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience Atlassian Assist unavailability in JSM.
We will continue to share additional updates here as more information is available.
Feb 26, 16:21 UTC
Update - We continue to investigate the issue, and will share an update within next 2 hours or sooner.
Feb 26, 14:25 UTC
Update - We are still actively investigating this issue and working to restore Atlassian Assist in Jira Service Management. We will share another update here within the next 2 hours or sooner.
Feb 26, 13:22 UTC
Investigating - Atlassian Assist in Jira Service Management is currently unavailable. We are actively investigating the problem. We will share updates here as more information in next 60 mins or sooner.
Feb 20, 12:26 UTC
Resolved - This issue has been resolved and all services are functional.
Feb 20, 12:26 UTC
Update - We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 07:13 UTC
Update - We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 04:14 UTC
Update - Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours as we continue our investigation.
Feb 20, 02:52 UTC
Identified - Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately.
We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue.
Feb 20, 2026 - 02:52 UTC
Please see prior notifications relating to this incident below:
Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites.
We anticipate next update to be posted in approximately 8 hours.
Feb 19, 2026 - 21:04 UTC
Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
We will continue to share additional updates here as more information is available.
Feb 19, 2026 - 18:56 UTC
Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
Feb 19, 2026 - 17:34 UTC
Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites.
We will continue to share additional updates here as more information is available.
Feb 19, 2026 - 17:14 UTC
Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites.
We will share updates here as more information is available.
Feb 19, 2026 - 16:44 UTC
Feb 7, 05:38 UTC
Resolved - On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Feb 7, 05:28 UTC
Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Feb 7, 03:43 UTC
Update - Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
Feb 7, 02:22 UTC
Update - Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.
Feb 6, 22:33 UTC
Update - Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.
Feb 6, 20:26 UTC
Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Feb 6, 20:24 UTC
Update - Impact
The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.
Current Status
Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.
Next Steps
The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.
Feb 6, 20:24 UTC
Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Feb 18, 14:29 UTC
Resolved - This incident has been resolved.
Feb 18, 03:21 UTC
Update - We are continuing to investigate this issue.
Feb 17, 22:22 UTC
Update - We are continuing to investigate this issue.
Feb 17, 21:09 UTC
Investigating - We are aware of an issue where some customers are not receiving login verification emails required for verification. As a result, impacted users may be unable to complete the login process.
If you are affected, please contact Support using the Request Help Logging in button from this article: https://support.lastpass.com/s/document-item?language=en_US&bundleId=lastpass&topicId=LastPass/having-trouble-logging-in-faq.html&_LANG=enus for assistance, and our team will help verify your identity and restore access.
We will provide updates as the team continues the investigation.
Feb 3, 17:49 UTC
Resolved - We have confirmed that the issue has been resolved completely and all systems are 100% operational at this time. Affected users may need to log out and log back in.
We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.
Feb 3, 16:24 UTC
Monitoring - Our engineering team has identified the underlying issue and completed a rollback, which has mitigated the issue. Affected users may need to log out and log back in to resolve the issue.
We will provide an additional update shortly.
Feb 3, 16:01 UTC
Investigating - We are actively investigating reports that some LastPass users may be experiencing issues launching saved sites from their vault. Access to Vaults is not affected. Engineers continue to troubleshoot the situation and we will update once resolved.
Oct 30, 00:04 UTC
Resolved - Systems are operational and the incident is resolved
Oct 29, 21:34 UTC
Monitoring - Our third-party provider has applied fixes that are gradually resolving the issue. While many users are seeing improvements, some connectivity issues remain. We are actively monitoring the situation.
Oct 29, 20:01 UTC
Update - LastPass engineers continue to work with the cloud provider to resolve the issue.
Oct 29, 17:44 UTC
Identified - Our third party cloud provider has identified the issue and are now actively working towards a resolution. We will provide another update shortly.
Oct 29, 16:23 UTC
Investigating - We’re currently experiencing service degradation on LastPass's marketing site due to an issue with our external cloud provider. Our team is actively working to resolve the issue and minimize the impact.
Oct 21, 09:42 UTC
Resolved - Service degradation issue has been resolved. Vault access and login functionality, including for federated users, are now fully operational.
Oct 21, 09:19 UTC
Update - We’re currently investigating an issue that may prevent some users from logging in. Our team is working to restore full access as quickly as possible.
Oct 21, 09:12 UTC
Investigating - We’re currently experiencing system degradation. LastPass Vaults may take longer to load. Our team is actively working to resolve the problem and minimize impact.
Oct 20, 13:25 UTC
Resolved - This incident has been resolved.
Oct 20, 11:12 UTC
Update - All of our services are now running and operational. However, we are closely monitoring the situation, as some of our external providers who were also affected by this incident are still in the process of recovery.
We’re keeping a close eye on our integrations to ensure continued stability and prevent further disruptions.
Oct 20, 10:41 UTC
Monitoring - Most services have now been restored and are operational, including our phone lines. We continue to monitor the situation closely to ensure full stability.
Oct 20, 09:57 UTC
Investigating - We’re currently experiencing service degradation due to an issue with our external cloud provider, this has also impacted our phone lines. For support, please reach out through our Support Center. Our team is actively working to resolve the issue and minimize the impact.
Mar 20, 21:08 UTC
Resolved - Between 21:08 and 21:22 UTC, there was an increase in errors and latency on the Standard Edge Network.
Mar 17, 14:44 UTC
Resolved - This incident has been resolved.
Mar 17, 14:10 UTC
Update - We are continuing to monitor for any further issues.
Mar 17, 14:10 UTC
Monitoring - A fix has been implemented and we will continue to monitor the results.
Mar 17, 14:07 UTC
Investigating - We are currently experiencing elevated rates of Edge Function errors on the Standard Edge Network since 13:38-14:07 UTC. We are investigating the cause.
Mar 12, 04:17 UTC
Resolved - This incident has been resolved.
Mar 12, 03:43 UTC
Investigating - We're investigating an increase in errors on the High Performance Edge Network in Mumbai (BOM) region since 3 AM UTC.
Mar 11, 11:33 UTC
Resolved - This incident has been resolved.
Mar 11, 11:19 UTC
Update - We are continuing to monitor for any further issues.
Mar 11, 10:57 UTC
Monitoring - The cause of the issue was identified, and we are monitoring the fix that was applied.
Mar 11, 10:33 UTC
Update - We are continuing to investigate this issue.
Mar 11, 10:08 UTC
Update - We are continuing to investigate this issue
Mar 11, 09:38 UTC
Investigating - We continue to investigate this rise in latencies creating high error rates.
Mar 11, 09:09 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 11, 08:49 UTC
Identified - The issue has been identified and we are working on a resolution.
Mar 11, 08:44 UTC
Investigating - We are experiencing high latencies in our origin. This may cause high error rates and elevated response times, as well as build failures. We are currently investigating.
Mar 10, 16:43 UTC
Resolved - From 16:43 UTC to 16:58 UTC, we served HTTP 500 for paths invoking Edge Functions (including framework-generated ones like Next.js Middleware/Proxy). This affected the Free/Starter as well as some part of the Pro tier users on the Standard Edge Network. The issue has since been resolved.
Mar 5, 17:35 UTC
Resolved - This incident has been resolved.
Mar 5, 13:01 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 5, 11:41 UTC
Investigating - We are currently investigating this issue.
Feb 25, 20:03 UTC
Resolved - This incident has been resolved.
Feb 25, 19:28 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 25, 19:24 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 25, 18:43 UTC
Investigating - We are currently investigating this issue.
Feb 17, 22:28 UTC
Resolved - This incident has been resolved.
Feb 17, 21:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 17, 20:01 UTC
Investigating - We are currently investigating this issue.
Jan 29, 20:49 UTC
Resolved - This incident has been resolved.
Jan 29, 20:18 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 29, 20:04 UTC
Investigating - We are currently investigating this issue.
All impacted services have now fully recovered.
Affected components
- Conversations (Operational)
Video generation error rates have returned to normal levels and services are functional.
Affected components
- Video generation (Operational)
All impacted services have now fully recovered.
Affected components
- Connectors/Apps (Operational)
All impacted services have now fully recovered.
Affected components
- Conversations (Operational)
Mar 18, 19:17 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with CAPTCHA has been resolved. All services are now operating normally at this time.
Mar 18, 14:54 PDT
Monitoring - Our engineers have implemented a fix and are monitoring system performance. Users that were previously impacted by failed CAPTCHA errors should now have the capacity to login without issue. We will provide another update in an hour or as soon as more information becomes available.
Mar 18, 14:32 PDT
Update - Our engineers are continuing to investigate the issue. We will provide another update two hours or as soon as more information becomes available.
Mar 18, 13:34 PDT
Investigating - Our engineers are continuing to investigate the issue. We will provide another update in hour or as soon as more information becomes available.
Mar 18, 12:35 PDT
Identified - Our engineers are continuing to investigate the issue. We will provide another update in hour or as soon as more information becomes available.
Mar 18, 11:33 PDT
Investigating - Starting around 11:06 AM PST on March 18, 2026, our engineers began investigating an issue with Cloudflare CAPTCHA failing to load on SendGrid and Twilio login pages. Customers may experience difficulty accessing the user console, as the failing CAPTCHA prevents successful login. This does not impact mail send. We will provide another update in an hour or as soon as more information becomes available.
Mar 5, 11:14 PST
Resolved - Between 8:53 AM and 9:37 AM PST, customers may have experienced delays in email event processing, including click and open data. Our Engineers identified a bottleneck, and have resolved the issue.
While email delivery continued with low execution times, the reporting of these events to the Stats API and your dashboard was delayed.
However, all downstream queues, including Engagement Stats, have fully caught up as of 9:45 AM PST and are resolved at the time.
Mar 4, 08:44 PST
Resolved - Our engineers have investigated and resolved an issue that occurred causing delays in timezone updates. On 03/03 ~2:09PM customers would have seen errors in the console when trying to update their timezone setting or while fetching timezones via /v3/timezones. A fix was deployed a fix on 03/04 ~7:48AM. This issuse has now been resolved
Mar 4, 07:30 PST
Resolved - Our engineers have investigated and resolved the issues that began on 3/4/2026 from 8am PST to 3/9/2026 at 5pm PST that impacted the reporting for a subset of group unsubscribe and group resubscribe Event Webhooks. Users may have experienced issues with group unsubscribes and group resubscribes that were not processed, although the api calls for those events were processed. The issue has been resolved and all impacted services are operating normally.
Mar 21, 01:09 UTC
Resolved - Ingestions and alerts are caught up and the incident is resolved.
Mar 20, 21:42 UTC
Monitoring - Customers may experience some delay in ingestion and alerts. We are currently burning the backlog
Mar 16, 22:21 UTC
Resolved - The incident has been resolved
Mar 16, 22:11 UTC
Monitoring - Ingestion is back to normal, alerts may still be delayed
Mar 16, 21:39 UTC
Identified - We are actively mitigating the issue
Mar 16, 20:17 UTC
Investigating - We are currently investigating the issue. Some alerts may be dropped if they are for older time windows.
Mar 9, 20:37 UTC
Resolved - Ingestion and alert latency is back to normal.
Mar 9, 18:17 UTC
Monitoring - We are burning the backlog and actively monitoring the progress.
Mar 9, 17:59 UTC
Identified - US customers may experience delay in alerts. We've identified the issue and will be putting in a fix.
Mar 2, 21:09 UTC
Resolved - This incident has been resolved.
Mar 2, 20:57 UTC
Update - EU ingestion has been restored and latency is back to normal levels. US continues to recover and will likely be caught up within the next hour.
Mar 2, 20:29 UTC
Monitoring - We have implemented a fix and are monitoring
Mar 2, 20:09 UTC
Identified - The issue has been identified and the fix is being implemented.
Mar 2, 19:57 UTC
Investigating - We are currently investigating this issue.
Feb 26, 20:56 UTC
Resolved - Ingestion backlog has finished processing and our system is now operating normally.
Feb 26, 20:02 UTC
Monitoring - Our cloud provider has resolved an underlying problem and our dashboard availability issues have been resolved. We're continuing to process our ingestion backlog and monitor the situation.
Feb 26, 19:15 UTC
Investigating - We're investigating intermittent failures loading our dashboard (all regions) and increased latency for ingestion of all events types in US
Feb 19, 12:53 EST
Resolved - This incident has been resolved.
Feb 19, 12:16 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 19, 11:18 EST
Identified - The issue has been identified and a fix is being implemented.
Feb 19, 10:45 EST
Investigating - We are currently investigating delays in processing file published callbacks and webhooks.
Feb 17, 18:10 EST
Resolved - This incident has been resolved.
Feb 17, 17:26 EST
Monitoring - Fix is applied, we're monitoring queue processing
Feb 17, 08:03 EST
Investigating - We are currently investigating possible delays in jobs authorizaiton and processing
Feb 10, 19:46 EST
Resolved - This incident has been resolved.
Feb 10, 17:41 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 10, 16:36 EST
Investigating - We are currently investigating reports of users experiencing difficulty accessing the Translation Workbench.
Feb 9, 22:41 EST
Resolved - This incident has been resolved.
Feb 9, 18:45 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 9, 11:46 EST
Identified - Due to a disruption on GitHub’s side, the GitHub Connector may experience increased latency in deliveries and request processing. Dashboard, Smartling API, Global Delivery Network services remain operational.
Jan 14, 12:04 EST
Resolved - This incident has been resolved.
Jan 14, 11:34 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 14, 10:54 EST
Investigating - We are currently investigating reports of delays in jobs authorizaiton and processing
We have identified and addressed the root cause of the delays. The issue is now resolved.
Affected components
- Timesheets (Operational)
The incident was resolved. Root cause analysis for a permanent solution is in progress.
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
The disruption has now been resolved.
Affected components
- Adaptive Planner (Operational)
- Time Tracker (Operational)
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
- Jira (Operational)
- Tempo for Slack (Operational)
- Tempo for Jira Cloud Help Center (Operational)
Mar 6, 14:49 UTC
Resolved - This incident has been resolved.
Mar 6, 14:08 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 6, 13:50 UTC
Investigating - We are currently investigating this issue.
Jan 23, 15:30 UTC
Resolved - We identified the cause of elevated latency impacting some databases in us-east-1 region between 15:30–15:35 UTC as a sudden surge of connection attempts that hit OS-level connection limits on our proxy layer. This resulted in slower new connection establishment and increased latency for some requests. Databases were not impacted. We are implementing additional proxy-level metrics and safeguards to detect and manage similar edge cases earlier.
Dec 10, 12:08 UTC
Resolved - Issue has been identified and replicas were successfully reconnected.
Dec 10, 11:50 UTC
Investigating - We identified an issue in Regional Databases in US-East-1 where database replicase have connectivity issues with each other.
Other regions are not impacted. Global databases are not impacted.
We are working on the issue.
Dec 5, 09:18 UTC
Resolved - This incident has been resolved.
Dec 5, 09:03 UTC
Investigating - Upstream provider confirmed an incident. We are investigating the impact and potential resolutions.
Dec 1, 07:00 UTC
Resolved - We identified and fixed a bug that could cause messages with Flow Control enabled to be delayed longer than their configured delay, resulting in unexpectedly long pending times.
The fix is in place and the issue should not recur. If you’re still seeing unusually long-delayed messages, please contact [email protected] and we can help with remediation.
Mar 16, 18:44 UTC
Resolved - Due to ongoing issues in the dxb1 region, traffic and regional Vercel services are currently re-routed to bom1. We will share more details on recovery when they become available.
Mar 2, 18:23 UTC
Monitoring - We are monitoring the situation and continue to work toward restoring capacity in the dxb1 region. We will send further updates when new information is available.
Mar 2, 15:29 UTC
Identified - Due to operational issues in the dxb1 region, traffic is currently re-routed to bom1. Additionally, dxb1 is currently unavailable as a Function Region for new deployments.
If your existing deployments that use the dxb1 region are experiencing elevated function invocation errors, we strongly recommend switching to the nearest region (such as bom1) and redeploy until capacity is restored in dxb1. Deployments using multiple regions or failover regions are not affected since traffic is automatically routed to the nearest region based on the configured settings.
Mar 13, 23:15 UTC
Resolved - This incident has been resolved.
Mar 13, 22:53 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 13, 22:32 UTC
Investigating - We are currently investigating elevated error reports of deployment creation during the build phase. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Mar 12, 01:15 UTC
Resolved - Between 01:15 and 05:45 UTC, customers might have experienced elevated GitHub deployment failures, including delays in triggering new deployments for commits and redeploy errors displaying the message "There is no GitHub account connected to this Vercel account". This was due to GitHub API degradations, which they have since resolved.
https://www.githubstatus.com/incidents/lw6j95nyw3py
https://www.githubstatus.com/incidents/02z04m335tvv
Mar 6, 21:38 UTC
Resolved - This incident has been resolved.
Mar 6, 21:20 UTC
Monitoring - A fix has been applied and we are seeing recovery for affected deployments. We are continuing to monitor.
Mar 6, 19:18 UTC
Update - We are applying a fix for the deployments experiencing elevated errors.
We continue to recommend redeploying if you are seeing errors on deployments created between 11:20 UTC and 15:14 UTC. Deployments created outside of this window are unaffected and no action is required. Additionally, deployments with middleware on the Node runtime are unaffected.
Mar 6, 15:25 UTC
Identified - Some deployments created between 11:20 UTC and 15:14 UTC with Edge Middleware may be seeing elevated errors. Deployments created outside of this time window are unaffected. If you are experiencing issues, we recommend redeploying.
Mar 6, 21:22 UTC
Resolved - This incident has been resolved.
Mar 6, 21:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 6, 21:00 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 6, 20:53 UTC
Investigating - We are investigating reports of elevated queue message latency and message retry latency in iad1, as well as elevated sleep times and increased step retries in Workflow. We will provide additional updates as they become available.
Mar 19, 15:11 PDT
Resolved - This incident has been resolved.
Mar 19, 14:59 PDT
Monitoring - The service degradation affecting meeting conversations missing in ZRA (Zoom Revenue Accelerator) conversation list across US regions has been resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Mar 19, 14:47 PDT
Identified - We have successfully identified the root cause affecting meeting conversations missing in ZRA (Zoom Revenue Accelerator) conversation list across US regions.
Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Mar 19, 14:39 PDT
Investigating - We are currently investigating a service degradation with meeting conversations missing in ZRA (Zoom Revenue Accelerator) conversation list across US regions
Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available.
We appreciate your patience as we work to resolve this issue.
Mar 18, 01:48 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Mar 18, 01:26 PDT
Monitoring - On 03/18/2026, Between 7:25 UTC to 8:05 UTC, users may have experienced issues with accessing some of the webpages of zoom.us, Zoom Rooms, Zoom Contact Center Analytics.
This incident has been resolved and the affected services have been restored.
Mar 17, 21:53 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Mar 17, 21:43 PDT
Monitoring - Between 19:42 UTC on 03/17/2026 and 03:23 UTC on 3/18/2026, A subset of users experienced issues with Zoom phone outbound calls to Australia and New Zealand. The incident is now resolved, and all affected services are fully restored.
Mar 17, 01:08 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Mar 17, 00:38 PDT
Monitoring - The service degradation affecting Zoom AIC and Zoom Virtual Agent in US region has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Mar 16, 23:35 PDT
Update - We continue to work on a fix for this issue and will provide updates as soon as there is more information to share.
Mar 16, 22:18 PDT
Identified - We have successfully identified the root cause affecting Zoom AIC and Zoom Virtual Agent in US region.
Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Mar 16, 21:50 PDT
Update - We are continuing to investigate this issue and will provide updates as soon as there is more information to share.
Mar 16, 20:54 PDT
Update - We are continuing to investigate this issue and will provide updates as soon as there is more information to share.
Mar 16, 20:14 PDT
Update - We are continuing to investigate this issue and will provide updates as soon as there is more information to share.
Mar 16, 19:30 PDT
Investigating - We are currently investigating a service degradation affecting Zoom AIC and Zoom Virtual Agent in US region.
Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available.
We appreciate your patience as we work to resolve this issue.
Mar 16, 12:56 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Mar 16, 12:42 PDT
Monitoring - The service degradation affecting Real Time Media Stream has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Mar 16, 11:48 PDT
Update - Our team continues to work on a resolution. An update will be provided when more information becomes available.
Thank you for your patience.
Mar 16, 10:49 PDT
Identified - We have successfully identified the root cause affecting Real Time Media Streams.
Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Mar 16, 10:37 PDT
Investigating - We are currently investigating a service degradation with Real Time Media Streams.
Our team is actively working to identify the impact and root cause. We will provide an update as soon as more information becomes available.
We appreciate your patience as we work to resolve this issue.