Apr 1, 22:16 UTC
Resolved - This incident has been resolved.
Apr 1, 22:15 UTC
Identified - We have identified an issue which results in the Claude.ai desktop application returning an error when attempting to connect. We are working to resolve this issue as quickly as possible, and the Claude.ai website is unaffected.
Apr 1, 10:40 UTC
Resolved - This incident has been resolved.
Apr 1, 09:06 UTC
Identified - We have identified an issue resulting in elevated errors on requests to Claude Opus 4.6, and are working to resolve this. We will provide an update as soon as possible.
Apr 1, 07:01 UTC
Resolved - We have identified an issue which resulted in elevated rates of timeouts when making requests to Claude Opus 4.6 and Sonnet 4.6 from 17:45 UTC on March 31 through 05:52 UTC on April 1. This issue has been resolved.
Apr 1, 02:14 UTC
Resolved - This incident has been resolved.
Apr 1, 01:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 1, 01:27 UTC
Investigating - We are currently investigating this issue.
Mar 31, 22:59 UTC
Resolved - We have resolved an issue that resulted in the unavailability of connectors in the Claude.ai desktop application. Affected connectors were removed from organization allowlists, and can be manually re-added while we work to automatically restore impacted allowlists.
Mar 31, 20:12 UTC
Identified - We have identified an issue which has resulted in some Claude.ai connectors becoming unavailable within the desktop application. We are working to restore access to these extensions, and will provide an update as soon as possible.
The incident has been resolved.
The incident has been resolved. The team will continue monitoring.
Apr 1, 12:23 UTC
Resolved - It appears that GitHub's `GET /repos/{owner}/{repo}/commits` API is now stable and responsive.
Apr 1, 12:12 UTC
Monitoring - GitHub's `GET /repos/{owner}/{repo}/commits` API has appeared to recover. We will continue to monitor this.
Apr 1, 11:58 UTC
Identified - We are continuing to see very high error rates from GitHub's `GET /repos/{owner}/{repo}/commits` API.
Apr 1, 11:55 UTC
Investigating - Some pipelines may not trigger due to a high rate of API failures on one of GitHub's API endpoints. This includes some manually-triggered pipelines, some OAuth hooks and some scheduled pipelines.
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.
Apr 2, 18:17 UTC
Resolved - This incident has been resolved.
Apr 2, 17:10 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 2, 16:50 UTC
Investigating - Cloudflare is investigating an issue affecting Digital Experience Monitoring (DEX). Customers may experience delays in DEX data. We will provide updates as our investigation progresses.
Apr 2, 17:39 UTC
Investigating - Cloudflare is investigating elevated latency uploading Workers Static Assets. Workers scripts which are already uploaded are not impacted.
Apr 2, 14:17 UTC
Resolved - This incident has been resolved.
Apr 2, 14:07 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 2, 14:02 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 2, 12:42 UTC
Investigating - Cloudflare is investigating issues with creating Managed Rules exceptions via the Cloudflare Dashboard. These issues do not affect the Cloudflare API, serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Dashboard to make these changes are impacted as requests might fail and/or errors may be displayed.
Apr 2, 12:58 UTC
Resolved - This incident has been resolved.
Apr 2, 12:43 UTC
Update - We are continuing to investigate this issue.
Apr 2, 12:41 UTC
Investigating - Cloudflare single-file cache purging (purge by URL) called via the Dashboard/API are delayed. We are working to resolve this issue as soon as possible. Until then you may use the Purge Everything feature but do be aware it may cause a surge in traffic to your origin server(s). More updates to follow.
Apr 2, 10:29 UTC
Resolved - This incident has been resolved.
Apr 2, 10:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 2, 09:05 UTC
Investigating - Cloudflare is aware of and investigating an issue with AI Search. Customers may observe 7001 and internal error messages. We are working to analyse and mitigate this problem. More updates to follow shortly.
Apr 2, 13:58 UTC
Investigating - Our upstream provider, Vultr, is currently experiencing a partial outage in their Sydney location. Their network engineers are actively working to restore connectivity as quickly as possible. We regret any inconvenience caused and appreciate your patience.
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 25, 15:30 UTC
Resolved - This incident has been resolved.
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: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.
Mar 31, 15:03 UTC
Resolved - We have validated that the fix resolved the issue and customers are no longer seeing errors when accessing the org settings page in the Contentful WebApp.
Mar 31, 14:58 UTC
Monitoring - We have identified an issue where customers see an error when trying to access organisation settings in the Contentful WebApp. We have already applied a fix and are verifying the results.
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.
Mar 26, 11:57 EDT
Resolved - This incident has been resolved.
Mar 26, 11:18 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 26, 10:50 EDT
Investigating - We are investigating reports of inaccessible form lists affecting accounts in the Frankfurt region. We understand the disruption this may cause and are actively working to resolve it as quickly as possible. We will provide updates as more information becomes available.
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.
Apr 2, 17:59 UTC
Update - When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running.
We are investigating.
Apr 2, 17:49 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 2, 16:30 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.
Apr 2, 16:28 UTC
Update - When assigning tasks to Copilot Cloud Agent, the task will appear to be working, but may not actually be running.
We are investigating.
Apr 2, 16:18 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 1, 23:45 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.
Apr 1, 23:45 UTC
Update - Code search has recovered and is serving production traffic.
Apr 1, 22:00 UTC
Update - We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.
Apr 1, 19:37 UTC
Update - We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.
Apr 1, 17:48 UTC
Update - We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April 2026). We are still working on recovering our ingestion pipeline, and synchronizing the indexed data.
We will update again within 2 hours.
Apr 1, 16:00 UTC
Update - We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic configuration which is causing most requests for Code Search results to fail. We are working to restore the service and to re-ingest the misaligned data.
Apr 1, 15:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 1, 16:10 UTC
Resolved - On April 1, 2026, between 15:34 UTC and 16:02 UTC, our audit log service lost connectivity to its backing data store due to a failed credential rotation. During this 28-minute window, audit log history was unavailable via both the API and web UI. This resulted in 5xx errors for 4,297 API actors and 127 github.com users. Additionally, events created during this window were delayed by up to 29 minutes in github.com and event streaming. No audit log events were lost; all audit log events were ultimately written and streamed successfully. Customers using GitHub Enterprise Cloud with data residency were not impacted by this incident.
We were alerted to the infrastructure failure at 15:40 UTC — six minutes after onset — and resolved the issue by recycling the affected environment, restoring full service by 16:02 UTC. We are conducting a thorough review of our credential rotation process to strengthen its resiliency and prevent recurrence. In parallel, we are strengthening our monitoring capabilities to ensure faster detection and earlier visibility into similar issues going forward.
Apr 1, 16:07 UTC
Update - A routine credential rotation has failed for our our audit logs service; we have re-deployed our service and are waiting for recovery.
Apr 1, 16:06 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 1, 12:41 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.
Apr 1, 12:10 UTC
Update - The success rate and latency for creating and viewing agent sessions has stabilized at baseline levels, we are continuing to monitor recovery
Apr 1, 12:02 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 1, 11:37 UTC
Update - The success rate for creating and viewing agent sessions has stabilized, and we're continuing to monitor latency, which is trending toward baseline levels.
Apr 1, 11:24 UTC
Update - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 1, 10:56 UTC
Monitoring - The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability.
Apr 1, 10:31 UTC
Update - Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate.
Apr 1, 10:00 UTC
Update - We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation.
Apr 1, 09:58 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Mar 25, 17:17 EDT
Resolved - Between 03:44 PM (UTC -04:00) and 04:39 PM (UTC -04:00), some customers in all affected regions experienced issues with Email replies. This was caused by a server impairment. As of 04:39 PM (UTC -04:00), our Email replies are 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.
Mar 25, 16:56 EDT
Investigating - We are investigating an issue impacting Email replies. 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 23, 11:22 EDT
Resolved - Between 10:15 AM (UTC -04:00) and 10:37 AM (UTC -04:00), all customers in all affected regions experienced issues with Forms on landing pages. This was caused by a server impairment. As of 10:37 AM (UTC -04:00), our Forms on landing pages are 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.
Mar 23, 10:48 EDT
Monitoring - We've addressed the issue that caused Forms to be unavailable in all affected regions since 10:26 AM (UTC -04: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.
Mar 23, 10:42 EDT
Investigating - We are investigating an issue impacting Forms. 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, 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.
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.
Apr 1, 17:16 UTC
Update - We are continuing to monitor for any further issues.
Apr 1, 00:25 UTC
Update - We are continuing to monitor for any further issues.
Mar 31, 21:06 UTC
Update - We are continuing to monitor for any further issues.
Mar 31, 18:38 UTC
Update - We are continuing to monitor for any other issues.
Mar 31, 17:19 UTC
Monitoring - A fix has been implemented to mitigate the issue. We are now monitoring the system to ensure continued stability.
Mar 31, 15:58 UTC
Identified - Our engineers have identified the issue and are now actively working towards a resolution. In the meantime impacted users should ensure they are running the latest version of the browser extension, and try using a different browser if issues persist. We will provide another update shortly.
Mar 31, 15:30 UTC
Investigating - We are actively investigating reports that some LastPass customers may be experiencing intermittent login issues. Our engineers are working to identify the issue and will provide another update shortly.
Mar 26, 13:26 UTC
Resolved - We have confirmed that the issue has been resolved. We will conduct an internal review of this issue to help prevent or minimize future recurrence.
Mar 25, 15:00 UTC
Monitoring - We have deployed a fix to production and are continuing to monitor the issue.
Mar 25, 13:49 UTC
Update - We are continuing to investigate this issue.
Mar 25, 13:15 UTC
Investigating - We are investigating reports that some LastPass customers are experiencing login issues. Our engineering team is working to identify the cause and will provide an update soon.
Mar 25, 12:11 UTC
Resolved - We have confirmed that the issue has been resolved. We will conduct an internal review of this issue to help prevent or minimize future recurrence.
Mar 25, 11:48 UTC
Update - We are continuing to investigate this issue.
Mar 25, 11:27 UTC
Investigating - We are actively investigating reports that some LastPass customers may be experiencing login issues and access to the vault and Admin console. Our engineers are working to identify the issue and will provide another update shortly.
Mar 24, 13:19 UTC
Resolved - We have confirmed that the issue has been resolved. We will conduct an internal review of this issue to help prevent or minimize future recurrence.
Mar 24, 13:00 UTC
Investigating - We are actively investigating reports that
Our engineers are working to resolve the issue and will provide another update shortly.
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.
Apr 2, 17:59 UTC
Resolved - This incident has been resolved.
Apr 2, 15:34 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 2, 14:19 UTC
Update - We are continuing to investigate this issue.
Apr 2, 14:19 UTC
Update - We're also experiencing errors on the High Performance Edge Network. We're investigating the issue.
Apr 2, 12:26 UTC
Investigating - We're currently experiencing some errors on the Standard Edge Network. High Performance Edge Network should be unaffected.
Mar 30, 21:09 UTC
Resolved - We’ve deployed a fix for the environment variables issue affecting some sites, and this all sites have received this fix as of 4:45pm UTC 3-31.
Mar 30, 19:38 UTC
Monitoring - We’ve identified the root cause of the environment variables issue affecting some sites and have deployed a fix. The fix is now live, and impacted sites should have automatically received it. Customers do not need to take any further action.
We’ll keep monitoring our channels for any additional reports. If you continue to experience issues, please contact support.
Mar 30, 12:59 UTC
Update - We've identified the issue and applied a fix. No new sites are affected by the issue and we are applying a fix for previously affected customers.
Mar 30, 11:20 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 30, 08:48 UTC
Investigating - We are investigating an issue where environment variables were not being read at runtime for some sites. We will provide an update shortly.
Mar 27, 16:30 UTC
Resolved - From 16:30 UTC, we observed increased errors for Edge Function invocations on the Standard Edge Network. This includes framework generated Edge Functions like Next.js Middleware. The issue has been resolved as of 16:52 UTC.
Mar 24, 01:32 UTC
Resolved - This incident has been resolved.
Mar 24, 00:30 UTC
Monitoring - We experienced an increased number of delayed cache purges on both the Standard and HP Edge Networks between 22:30 and 0:10 UTC. We have deployed a fix and are currently monitoring the results.
Apr 1, 13:12 UTC
Resolved - This incident has been resolved.
Apr 1, 12:20 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 1, 10:05 UTC
Investigating - We are observing increased errors in viewing packages and authentication on npmjs website. We are investigating this issue.
Mar 31, 21:49 UTC
Resolved - This incident has been resolved.
Mar 31, 21:12 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 31, 20:42 UTC
Update - We have implemented initial fixes and are continuing to investigate this issue
Mar 31, 19:12 UTC
Investigating - We are seeing degraded performance in package viewing and authentication on npmjs website. We are currently investigating the issue.
Mar 30, 19:17 UTC
Resolved - This incident has been resolved.
Mar 30, 18:19 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 30, 17:56 UTC
Update - We have implemented some initial fixes. We are continuing to investigate the issue.
Mar 30, 16:41 UTC
Investigating - We are currently investigating this issue.
Mar 30, 15:59 UTC
Resolved - This incident has been resolved.
Mar 30, 15:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 30, 15:17 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 30, 14:54 UTC
Investigating - We are currently investigating this issue.
All impacted services have now fully recovered.
Affected components
- Voice mode (Operational)
The issue is now resolved.
Affected components
- Chat Completions (Operational)
All impacted services have now fully recovered.
Affected components
- Login (Operational)
All impacted services have now fully recovered.
Affected components
- Login (Operational)
Mar 25, 13:58 PDT
Resolved - From 9:08 AM PT - 9:22AM PT today, customers in the EU region may have experienced mail delay for up to 14 minutes. Customer may have received "Internal Deferral" errors when attempting to send mail at this time. Our engineers have investigated and resolved the issue. All impacted services are operating normally.
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
- Timesheets (Operational)
- Financial Manager (Operational)
- Capacity Planner (Operational)
The disruption has now been resolved.
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
- Jira (Operational)
- Tempo for Slack (Operational)
- Tempo for Jira Cloud Help Center (Operational)
- Adaptive Planner (Operational)
- Time Tracker (Operational)
Mar 27, 15:30 UTC
Resolved - Due to a race condition in a process that attaches static IPs to nodes, some of the IPs in the dns were detached from the nodes, causing timeouts.
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.
Apr 2, 18:09 UTC
Monitoring - The root cause has been identified, a fix has been rolled out, and we are actively monitoring. Newly deployed Vercel Functions on Node.js 20 in cle1 and dub1 no longer terminate with SIGSEGV. We recommend redeploying affected Vercel Functions if you are still seeing issues.
Apr 2, 16:13 UTC
Update - We are continuing to investigate increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV in Vercel's cle1 and dub1 regions. Other regions are unaffected. We recommend redeploying affected Vercel Functions or upgrading them to either Node js 22 or 24.
Apr 2, 14:10 UTC
Investigating - We are currently investigating increased rates of Vercel Functions running on Node.js 20 terminating with SIGSEGV. We recommend redeploying affected Vercel Functions or upgrading them to either Node.js 22 or 24.
Apr 1, 22:17 UTC
Resolved - This incident has been resolved.
Apr 1, 21:57 UTC
Monitoring - A fix has been implemented and we are monitoring the results. Webhook events are being delivered normally, and deployments with integrations are building successfully.
Apr 1, 20:48 UTC
Identified - We have identified an issue causing elevated latency and errors with delivering webhooks and creating deployments that use integrations. We are working on a fix for this issue and will provide further updates as soon as they become available.
Mar 31, 21:23 UTC
Resolved - This incident has been resolved.
Mar 31, 21:17 UTC
Monitoring - A fix has been applied for an issue where deployments were erroring with "invalid request" and we are monitoring the results. We recommend redeploying any failed deployments.
Mar 31, 21:11 UTC
Investigating - We are investigating reports of elevated errors when creating deployments. Existing deployments and live traffic are unaffected. We will provide updates as they become available.
Mar 31, 13:29 UTC
Resolved - This incident has been resolved.
Mar 31, 13:16 UTC
Update - Support case submission has been confirmed to be functioning normally. We will share updates as they become available.
Mar 31, 13:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results. We will share updates as they become available.
Mar 31, 13:10 UTC
Investigating - We are currently investigating reports of elevated errors when submitting support cases. Some customers may experience timeouts when creating support tickets. We will share updates as they become available.
Mar 25, 17:31 UTC
Resolved - This incident has been resolved.
Mar 25, 16:41 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 25, 16:32 UTC
Investigating - We are currently investigating reports of elevated error rates on the Vercel Dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Apr 2, 11:03 PDT
Update - Our teams continue to actively work towards a resolution. An update will be provided when more information becomes available.
Apr 2, 06:51 PDT
Update - Our team continue to work on the resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 2, 01:28 PDT
Update - Our team continue to work on the resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 1, 23:20 PDT
Identified - We have successfully identified the root cause affecting a subset of users using Zoom Client in the North America 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.
Apr 1, 21:53 PDT
Update - We continue to investigate the service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 20:59 PDT
Update - We continue to investigate the service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 19:55 PDT
Update - We continue to investigate the service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 18:52 PDT
Update - We continue to investigate the service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 17:51 PDT
Update - We continue to investigate the service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 16:21 PDT
Update - We continue to investigate the service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 15:46 PDT
Update - We continue to investigate the service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 15:07 PDT
Update - We continue to investigate service degradation affecting a subset of users with Zoom Client in the North America 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.
Apr 1, 14:24 PDT
Investigating - We are currently investigating a service degradation with a subset of users affecting Zoom Client in the North America 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 31, 20:15 PDT
Resolved - A subset of users might have experienced error code 1132 with sign in and joining meetings.
On 03/31/206 Between 03:15 UTC to 17:02 UTC, A subset of us may have experienced error code 1132 with sign in and joining meetings.
This incident has been resolved and the affected services have been restored.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Mar 31, 08:56 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Mar 31, 08:17 PDT
Monitoring - The issue affecting Zoom Phone Outbound Calls in India has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Mar 31, 06:45 PDT
Identified - We have successfully identified the root cause affecting Zoom Phone Outbound Calls in India.
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 31, 06:38 PDT
Investigating - We are currently investigating a service degradation affecting Zoom Phone Outbound Calls in India.
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 31, 05:51 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Mar 31, 05:36 PDT
Monitoring - On 2026-03-31 11:08 to 12:25 UTC users might have experienced issues with Zoom Phone outbound calls in the Hyderabad region. We have successfully resolved this issue. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Mar 30, 10:55 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Mar 30, 10:37 PDT
Monitoring - The service degradation affecting Zoom Phone and Zoom Contact Center PCI Integration has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Mar 30, 10:01 PDT
Identified - We have identified an issue with our vendor partner impacting Zoom Phone and Zoom Contact Center PCI integration.
We are actively working with our vendor partner to resolve the issue.
We will share updates as soon as they become available.
Mar 30, 09:55 PDT
Investigating - We are currently investigating a service degradation affecting Zoom Phone and Zoom Contact Center PCI Integration.
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.