Apr 11, 00:00 UTC
Resolved - Email login was broken between approximately 3:46 PM and 4:52 PM PDT on April 10, 2026.
Apr 10, 16:51 UTC
Resolved - The issue affecting requests to non-Opus models has been resolved.
Apr 10, 16:42 UTC
Identified - We have identified the current issue as affecting requests to models other than Claude Opus 4.6, and are working to fully resolve this issue. We will provide additional updates shortly.
Apr 10, 16:30 UTC
Investigating - We are investigating reports of elevated errors on requests to Claude across all products. We will provide an update as soon as possible.
Apr 10, 14:00 UTC
Resolved - Between April 2 and April 10, some users who were not signed in to Claude.ai (web, mobile, desktop) were not able to access some Claude.ai sharing links.
Apr 10, 04:38 UTC
Resolved - This incident has been resolved.
Apr 10, 04:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 10, 04:28 UTC
Investigating - We are currently investigating this issue.
Apr 9, 17:34 UTC
Resolved - This incident has been resolved.
Apr 9, 16:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 9, 16:54 UTC
Investigating - Certain connectors are experiencing higher error rates. We are investigating the issue.
The incident has been resolved.
The incident has been resolved.
The incident has been resolved. The team will continue monitoring.
Apr 8, 20:33 UTC
Resolved - The Usage API incident is resolved on an ongoing basis. There was a 4-hour period yesterday 4/7 for which we did not capture RAM and CPU utilization in our logs. We will not be backfilling the data for that period. Appreciate your patience.
Apr 8, 13:20 UTC
Identified - We have identified an issue causing Insights workflow and job data to be delayed when requested through the Usage API. Some data for the last 24 hours may not be fully reflected while we work to process the backlog of events. Insights UI is not impacted by this issue. Thank you for your patience.
Apr 6, 21:12 UTC
Resolved - This incident has been resolved.
Apr 6, 20:43 UTC
Monitoring - A fix has been implemented and we are monitoring the results. Thank you for your patience.
Apr 6, 20:33 UTC
Investigating - We are currently investigating an issue in the CircleCI UI impacting approval jobs and SSH key navigation. This is an interface-only issue and builds continue to flow as usual.
Apr 3, 02:18 UTC
Resolved - The Usage API issue affecting 4/1 data has been resolved. Updated data will be available on 4/3. Thank you for your patience.
Apr 2, 21:23 UTC
Identified - The Usage API issue has been identified and the fix is being implemented.
Apr 2, 19:19 UTC
Investigating - We are currently investigating this issue.
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.
Apr 10, 17:04 UTC
Resolved - This incident has been resolved.
Apr 10, 16:42 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 10, 15:56 UTC
Update - We are continuing to work on a fix for this issue.
Apr 10, 15:55 UTC
Identified - Cloudflare is investigating an increased level of 5xx errors in Philadelphia. We are working to analyse and mitigate this problem. More updates to follow shortly.
Apr 10, 16:26 UTC
Resolved - This incident has been resolved.
Apr 10, 16:20 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 10, 14:06 UTC
Identified - Cloudflare has identified an issue impacting Workers Assets uploads. Customers may be seeing an increase in Workers Assets upload failures.
This issues does not affect the serving of Workers Assets traffic. We are working to mitigate this problem. More updates to follow shortly.
Apr 9, 14:30 UTC
Resolved - Between 14:41 and 16:34 UTC on April 9th, 2026, we experienced an elevated level of HTTP 5xx errors affecting traffic through our Philadelphia (PHL) data center. The issue has been mitigated now.
Apr 8, 19:30 UTC
Resolved - Between 19:47 and 21:57UTC on April 8, 2026, Cloudflare identified and mitigated a network performance issue specifically affecting our Miami and Atlanta regions.
Users may have experienced increased latency or intermittent connectivity due to degraded routing paths in the Southeast.
Our engineering team has since stabilized the connection and confirmed that all systems are back to full operational capacity; we will continue to monitor these nodes closely to ensure ongoing performance.
Apr 8, 09:48 UTC
Resolved - This incident has been resolved.
Apr 8, 08:04 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 8, 07:28 UTC
Investigating - Cloudflare is investigating issues with operations on the Cloudflare One Dashboard.
Customers using the Cloudflare One dashboard are impacted. Customers may face issues when creating a new device profile on the Cloudflare One dashboard.
Apr 6, 18:35 UTC
Resolved - This incident has been resolved.
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.
Apr 4, 08:01 UTC
Resolved - This incident has been resolved.
Apr 4, 06:58 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 4, 06:00 UTC
Investigating - We’re aware of an issue causing some processes to become stuck in the UI. Our team is actively investigating and working to resolve it 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.
Apr 7, 20:31 UTC
Resolved - We have completed the rollout of the fix and believe all organizations should have restored functionality.
Apr 7, 19:44 UTC
Identified - We have identified the issue and are beginning to roll out a fix. We anticipate this taking approximately one hour, and will continue to provide updates. This incident is impacting web app views only for certain components, but is not impacting data.
Apr 7, 19:33 UTC
Investigating - We've spotted that something has gone wrong with certain components in the web app. We're currently investigating the issue, and will provide an update soon.
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.
Apr 8, 10:49 EDT
Resolved - The issue affecting email notification delivery has been resolved. A temporary third-party blocklist listing was identified and removed. Email notifications are now functioning normally.
If you continue to experience issues, please contact support.
Apr 7, 19:56 EDT
Monitoring - We have identified the cause of the email notification delivery issue as a temporary listing of one of our sending IPs on a third-party blocklist, which resulted in email rejections for some customers.
The listing has since been removed, and we have not observed any new rejection logs since 2:21 PM ET. Email notifications should now be functioning normally.
We are continuing to monitor the situation to ensure stability. We will provide another update once we confirm the issue is fully resolved.
Apr 7, 15:35 EDT
Investigating - Some customers are reporting that email notifications aren't being sent as expected upon form completion, and our team is investigating now.
We will post more information as it becomes available.
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.
Apr 10, 13:28 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 10, 13:08 UTC
Update - We are investigating third party Claude and Codex Cloud Agent sessions not being listed in the agents tab dashboard.
Apr 10, 13:07 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 9, 20:36 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 9, 19:52 UTC
Update - We continue to investigate periodic delays in Copilot Cloud Agent job processing
Apr 9, 18:57 UTC
Update - We are continuing to investigate Copilot Cloud Agent job delays
Apr 9, 17:48 UTC
Update - Copilot Cloud Agent jobs are being processed and we are monitoring recovery
Apr 9, 16:57 UTC
Update - We are investigating delays processing Copilot Cloud Agent jobs
Apr 9, 16:20 UTC
Update - We are experiencing issues where jobs are being delayed to start for copilot coding agent
Apr 9, 16:20 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 9, 10:15 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 9, 10:15 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 9, 09:57 UTC
Update - We are investigating an issue affecting GitHub Copilot coding agent. Users may experience significant delays when starting new agent sessions, with jobs remaining queued longer than expected. Our team has identified increased load as a contributing factor and is actively working to restore normal performance.
Apr 9, 09:50 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 9, 04:57 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 9, 04:57 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 9, 04:42 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 2, 21:48 UTC
Resolved - Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour. During this hour, some new jobs would time out, while others would resume once rate limiting ended. Roughly 40% of jobs in this period were affected.
Once the cause of this rate limiting was identified, we were able to disable the new CCR feature via a feature flag. Once the jobs that were already in the queue were able to clear, we didn't see additional instances of rate limiting afterwards.
Apr 2, 21:48 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 2, 20:35 UTC
Update - Although we are observing recovery once again, we expect continued periods of degradation.
Work that is queued during times of degradation does eventually get processed.
We continue to investigate and find a mitigation, and will update again within 2 hours.
Apr 2, 19:28 UTC
Update - This issue has recurred. Customers will once again experience false job starts when assigning tasks to Copilot Cloud Agent.
We are still investigating and trying to understand the pattern of degradation.
Apr 2, 18:25 UTC
Update - We are once again seeing recovery with Copilot Cloud Agent job starts.
We are keeping this open while we verify this won't recur.
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 9, 12:53 EDT
Resolved - Activity and Event features are no longer experiencing impairments. We've identified and addressed the cause of the delays that began at 9:00 AM EDT (UTC -04:00) on Apr 9, 2026 as a problem with a database configuration. The issue is now fully resolved.
Apr 9, 11:53 EDT
Update - We've addressed the issue that was causing Activity and Event feature impariment starting at 9:00 AM EDT (UTC -04:00) on Apr 9, 2026. We're monitoring the tools closely to ensure all processes recover properly. Only customers hosted in North America are currently impacted. We will be back with an update within an hour.
Apr 9, 10:50 EDT
Monitoring - We’ve identified the issue that is causing impairments in Activities and Events features beginning at 9:00 AM EDT (UTC -04:00) on Apr 9, 2026. We’re addressing the cause of this issue. Only customers hosted in North America are currently impacted. We will be back with an update within an hour.
Apr 9, 12:20 EDT
Resolved - Between 11:44 AM (UTC -04:00) and 12:18 PM (UTC -04:00), all customers in North America experienced issues with all impaired tools. This was caused by a database impairment. As of 12:18 PM (UTC -04:00), our all impaired tools 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.
Apr 9, 12:15 EDT
Identified - We estimate that we will restore service in the next half an hour.
We are mitigating impact from a database impairment which we believe is caused by a bad production configuration change. We are failing over to a healthy node.
We will be back with an update within 15 minutes.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 9, 12:00 EDT
Update - commerce tools, content tools, customer platform tools, hubspot APIs, marketing tools, operations tools, sales tools, service tools have been unavailable in North America since 11:44 AM (UTC -04:00). We are investigating the cause and will update this page when we have more information. We will be back with an update within 15 minutes.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 9, 11:48 EDT
Investigating - We're investigating reports that HubSpot may be unavailable for some users. We'll update this page when we have more information.
Apr 8, 16:51 EDT
Resolved - Between 04:35 PM (UTC -04:00) and 04:50 PM (UTC -04:00), some customers in North America experienced issues with event processing delays. This was caused by a server impairment. As of 04:50 PM (UTC -04:00), event processing 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.
Apr 8, 11:54 EDT
Resolved - Between 10:55 AM (UTC -04:00) and 11:28 PM (UTC -04:00), some customers in all affected regions experienced issues with company record creation. This was caused by bad deploy which has been rolled back. As of 11:28 PM (UTC -04:00), company record creation 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.
Apr 7, 12:48 EDT
Resolved - Between 10:00 AM (UTC -04:00) and 12:45 PM (UTC -04:00), some customers in North America experienced delays with event processing. This was caused by a server impairment. As of 12:45 PM (UTC -04:00), event processing is restored 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.
Apr 7, 12:23 EDT
Monitoring - We've addressed the issue that caused event processing to be delayed in North America since 10:00 AM (UTC -04:00).
The issue has been isolated to List Segmentation processing which is still delayed, but recovering.
We're monitoring performance closely to ensure all tools recover properly.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 7, 12:12 EDT
Update - We are continuing to investigate events processing delays in HubSpot in North America.
In order to alleviate downstream processing bottlenecks List Segmentation updates may be delayed.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 7, 11:39 EDT
Update - Events processing in HubSpot is experiencing delays of up to 30 minutes in North America since 10:00 AM (UTC -04:00).
This may impact tools such as Automation/Workflow triggers, CRM Events Timeline, Reporting, and Frontend dashboard components in HubSpot
We are investigating the cause and will update this page when we have more information.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 7, 11:24 EDT
Investigating - We are currently experiencing delays with data processing and page performance. Some users may notice that updates are delayed by up to 30 minutes and pages are loading slower than expected. We are investigating the cause and will provide updates shortly.
Apr 8, 11:43 UTC
Resolved - The issue has now been resolved, and the service is operating normally for all affected customers.
Apr 8, 09:03 UTC
Monitoring - The issue has been resolved, and services are now operating normally. Some customers may still experience delays when searching for data changed within the last hour, while new data continues to be indexed. We'll continue to monitor closely to confirm stability.
Apr 8, 09:03 UTC
Update - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus.
Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution.
We will provide further update within 1 hour.
Apr 8, 08:33 UTC
Update - We have restored core search functionality and services are operating again, but some customers may still experience delays when searching for data changed within the last hour while new data continues to be indexed. We are actively working to complete reindexing and will update this page as performance fully recovers.
Apr 8, 08:33 UTC
Update - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus.
Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution.
We will provide further update within 1 hour.
Apr 8, 07:40 UTC
Update - Confluence and Jira search reliability is improving, and we expect full recovery shortly; we will continue to closely monitor the services to ensure they remain stable.
Apr 8, 07:40 UTC
Update - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus.
Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution.
We will provide further update within 1 hour.
Apr 8, 06:25 UTC
Identified - We are also aware of impact as a result of these search failures to Customer Service Management, Asset Reports, Jira Service Management and dashboards within Focus.
Our team have identified the potential root cause of the issue and our teams are working with urgency on a resolution.
We will provide further update within 1 hour.
Apr 8, 06:25 UTC
Update - The impact of this incident is now understood to also be impacting search in Jira and Confluence, as well as additional downstream impacts to Rovo Chat, User Management, Administration and Guard.
Our team is continuing to investigate with urgency and we will provide further update within 1 hour.
Apr 8, 06:25 UTC
Update - Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.
Apr 8, 06:24 UTC
Investigating - Our team is aware that users are currently experiencing errors while attempting to search in Confluence and Jira. Our team is investigating with urgency and will be providing an update within 1 hour.
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
Apr 10, 08:18 UTC
Investigating - We are aware of a recent change made in the latest Chrome browser version, which likely affects Edge functionality as well (based on Chromium). This change affected LastPass site launch and autofill capabilities. If you're experiencing problems with the extension, fully quitting and restarting your browser resolves the issue and allows you to continue using LastPass normally. If you haven't yet updated to browser version 147, we recommend holding off until further notice.
Our team has identified a likely cause and is actively working on a fix. Once confirmed, we'll prepare a release and submit it to the browser stores. We'll post updates here as they become available.
Apr 8, 10:39 UTC
Resolved - We have confirmed that the issue has been resolved with the latest Chrome extension version 4.152.1. Affected users are advised to upgrade to this version to ensure proper functionality.
We will conduct an internal investigation of this issue to help prevent or minimize future recurrence.
Apr 8, 08:10 UTC
Identified - Our engineers have identified an issue where a subset of Business Chrome Extension users are being logged out frequently when the extension setting "Logout on browser close" is turned on via policy. A fix has been identified to mitigate the issue and we are actively working to implement this fix. We will provide another update shortly.
Apr 6, 19:04 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.
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.
Apr 9, 18:00 UTC
Resolved - between 17:40 UTC and 18:10 UTC, some customers may have experienced failures when purchasing credits or updating auto top-ups. This issue has been resolved.
Apr 6, 09:30 UTC
Resolved - Between 08:50 UTC and 09:41 UTC, Agent Runner experienced an outage caused by an issue with a third-party dependency. Customers may have experienced failures or degraded performance when running agents during this period. The issue has been resolved.
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.
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.
All impacted services have now fully recovered.
Affected components
- Login (Operational)
All impacted services have now fully recovered.
All impacted services have now fully recovered.
Affected components
- Login (Operational)
- Login (Operational)
All impacted services have now fully recovered.
Affected components
- Login (Operational)
- File uploads (Operational)
- Search (Operational)
- Conversations (Operational)
- Agent (Operational)
- ChatGPT Atlas (Operational)
- Voice mode (Operational)
- Compliance API (Operational)
- Image Generation (Operational)
- GPTs (Operational)
- Deep Research (Operational)
- Connectors/Apps (Operational)
Apr 10, 01:08 PDT
Resolved - Our engineers have resolved the issue affecting the Low Rate email swimlane in the email pipeline. The impact lasted approximately 40 minutes and affected customers who attempted to send mail between 11:57 PM and 12:35 AM Pacific Time. All services are now operating normally.
Apr 8, 13:30 PDT
Resolved - Our engineers have identified an issue with accessing SendGrid's Support Portal around 1:20pm PDT on April 8th. Some customers may have experienced issues with accessing the support UI, which inhibited the ability to access and create new support requests. Our engineers have implemented a fix, and monitored and confirmed the issue as being resolved. All services are now operating normally at this time.
Apr 8, 10:06 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with Legacy Marketing Campaigns unable to load has been resolved. All services are now operating normally at this time.
Apr 8, 09:19 PDT
Update - Our engineers are continuing to monitor the fix for the issue. We will provide another update in another hour, or as soon as more information becomes available.
Apr 8, 08:17 PDT
Monitoring - Starting around 08:00 AM PDT on April 8th, 2026, our engineers began investigating an issue with a subset of customers not being able to access Legacy Marketing Campaigns. They have deployed a fix & are continuing to monitor for functionality. This did not impact mail send.
We will provide another update in 1 hour or as soon as more information becomes available.
Apr 7, 14:00 PDT
Resolved - Our engineers have identified a delay in Email Log Data as well as Email Activity Data starting around 2pm PST on April 7th. All Email Log Data and Activity Feed Data was restored and no longer delayed at 3pm PST. Our engineers have monitored and confirmed the delay with Email Log and Activity Data has been resolved. All services are now operating normally at this time.
Apr 7, 11:53 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with the Billing processing payment failures has been resolved. All services are now operating normally at this time. Thank you for your understanding and patience.
Apr 7, 11:40 PDT
Update - Our engineers are continuing to monitor the fix for the issue. We will provide another update in 3 hours or as soon as more information becomes available.
Apr 7, 11:36 PDT
Update - We are continuing to monitor for any further issues.
Apr 6, 18:05 PDT
Monitoring - Our engineers are continuing to monitor the fix for the issue. We will provide another update in 3 hours or as soon as more information becomes available.
Apr 6, 12:11 PDT
Update - .
Apr 6, 12:10 PDT
Update - Our engineers are continuing to monitor the fix for the issue causing intermittent errors with account-level actions, including management and settings changes, as well as other account-specific functions such as login-related activity. At this time, there is no new information to share.
Mail send is not impacted.
We will provide another update in 3 hours or as soon as more information becomes available.
Apr 6, 09:37 PDT
Update - Our engineers have identified a fix for the issue affecting our customers’ ability, and our systems’ ability, to process payments. Customers may continue to experience notifications about their payments not being processed while we work to implement the fix.
We have also identified that customers using Email Validation may receive 403 errors until their account is activated.
This does not impact mail send.
We will provide another update in 2 hours or as soon as more information becomes available.
Apr 6, 08:43 PDT
Identified - Our engineers have identified a fix for the issue affecting our customers’ ability, and our systems’ ability, to process payments. Customers may continue to experience notifications about their payments not being processed while we work to implement the fix. This does not impact mail send.
We will provide another update in 2 hours or as soon as more information becomes available.
Apr 6, 08:28 PDT
Update - Our engineers are continuing to investigate an issue affecting our customers’ ability, and our systems’ ability, to process payments. Customers may experience notifications about their payments not being processed, and we are aware of this issue. This does not impact mail send.
We will provide another update in 2 hours or as soon as more information becomes available.
Apr 6, 06:23 PDT
Investigating - Starting around 05:30 AM, PST, on April 6th, 2026, our engineers began investigating an issue with our customer's ability (and system's ability) to process their payments. Customer may experience notifications about their payments not being processed, and we are aware of this issue. This does not impact mail send.
We will provide another update in 2 hours or as soon as more information becomes available.
Apr 10, 11:44 UTC
Resolved - Following the ingestion delay experienced between 08:40 – 08:55 UTC, all systems are now fully operational. Data ingestion is running normally across all data types.
Apr 10, 09:20 UTC
Monitoring - We experienced a delay in data ingestion affecting all data types between 08:40 – 08:55 UTC.
Apr 7, 23:42 UTC
Resolved - Hot fix merged, all customers can access their subscription pages now.
Apr 7, 22:28 UTC
Monitoring - We are rolling out a fix
Apr 7, 21:36 UTC
Identified - We have identified an issue for customers trying to access their subscription page. we are working on a fix
Apr 7, 21:23 UTC
Resolved - This incident has been resolved
Apr 7, 21:02 UTC
Monitoring - We performed a manual change that caused degraded performance and delayed ingestion in spans, crons, replays, and uptime that caused issues between 13:45 and 13:52 PT. The change has been cancelled and operations have returned to normal
Apr 6, 21:26 UTC
Resolved - This incident has been resolved and backlogs have been processed.
Apr 6, 20:52 UTC
Monitoring - We have identified the source of postgres load and mitigated it. We are continuing to monitor conditions as backlogs process.
Apr 6, 20:04 UTC
Update - We are continuing to mitigate load in our postgres clusters.
Apr 6, 19:04 UTC
Update - We are continuing to mitigate load in our postgres clusters.
Apr 6, 18:26 UTC
Update - We're continuing to mitigate load in our caching and postgres infrastructure.
Apr 6, 17:11 UTC
Identified - We have identified the problem as a load issue in our caching layer and are working to mitigate the issue.
Apr 6, 15:56 UTC
Investigating - We are investigating processing delays for errors and spans in the US region
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
The migration of Timesheets, Capacity Planner, and Financial Manager to Forge: https://www.tempo.io/product-news/tempo-moves-to-forge is underway, but the automatic rollout did not start on March 31, 2026 as planned. The deployment on March 30, 2026: https://help.tempo.io/release-notes/latest/tempo-cloud-release-notes#2026-03-31 only affected new installations and admins who manually clicked the Update button. Recommendation: Do not manually trigger the update or reinstall apps at this time. The automatic rollout will happen gradually over the coming weeks and we'll keep you posted here when it begins. Please note that once the rollout starts, it will not be possible to opt out, delay, or schedule your migration. You'll also receive an in-app notification once your instance has been migrated. Breaking changes Most of the migration is seamless, but a few things will change that may affect you, particularly around JQL filters: • JQL filter syntax – issueInternal, Account, Tempo Team, and custom field IDs • Tempo Panels in Jira issue view • Keyboard shortcuts • OAuth app URLs Please review the relevant documentation to prepare for changes that might affect you: • Expected Changes in Timesheets on Forge: https://help.tempo.io/timesheets/latest/expected-changes-in-timesheets-on-forge • Expected Changes in Capacity Planner on Forge: https://help.tempo.io/planner/latest/expected-changes-in-capacity-planner-on-forge • Expected Changes in Financial Manager on Forge: https://help.tempo.io/financialmanager/latest/expected-changes-in-financial-manager-on-forge
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)
Apr 2, 19:53 UTC
Resolved - Replication complete, incident resolved.
Apr 2, 18:45 UTC
Identified - Servers in the iad region experienced unexpected disk load, resulting in elevated latencies and a temporary read-only state. We are migrating replicas to new instances to mitigate the issue and expect to have it fully resolved shortly.
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 7, 18:56 UTC
Resolved - This incident has been resolved.
Apr 7, 18:27 UTC
Update - A fix has been rolled out, and we are monitoring the results. Queued deployments are being processed and new deployments are building normally now.
Apr 7, 18:06 UTC
Identified - We have identified an issue causing elevated queue times for deployments on the Hobby plan. We are investigating a fix and will share more updates as soon as we have more information.
Apr 7, 08:37 UTC
Resolved - The incident has been resolved. If you don't see build logs for a specific deployment, please redeploy.
Apr 7, 08:29 UTC
Monitoring - We identified the cause of build logs stuck in the loading state affecting iad1 and are working around the issue for new builds. Please redeploy to your build to view build logs.
Apr 7, 07:19 UTC
Investigating - We are investigating reports of build logs stuck in loading state.
Apr 2, 23:09 UTC
Resolved - This incident has been resolved.
Apr 2, 20:02 UTC
Monitoring - The fix has been rolled out and we are monitoring the results. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.
Apr 2, 19:26 UTC
Identified - We have identified the issue and are rolling out a fix. Deployments created between 16:10 to 19:12 UTC may be affected. If you are still seeing issues, we recommend redeploying or performing an instant rollback to fix the issue.
Apr 2, 18:39 UTC
Investigating - We are investigating reports of elevated INTERNAL_UNEXPECTED_ERROR responses affecting some customer deployments. We will provide updates as we learn more.
Apr 2, 18:53 UTC
Resolved - This incident has been resolved.
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.
Apr 11, 02:51 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 11, 02:41 PDT
Monitoring - The issue affecting Zoom Blog and Contact Us webpages has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 11, 02:39 PDT
Identified - We have identified the issue affecting Zoom Blog and Contact Us webpages.
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 11, 02:01 PDT
Investigating - We are currently investigating a service degradation affecting Zoom Blog and Contact Us webpages.
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 8, 22:05 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 8, 21:39 PDT
Monitoring - The issue preventing users from joining meetings via Web client in Saudi Arabia has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 8, 21:19 PDT
Investigating - We are currently investigating a service degradation affecting users ability to join Zoom meetings via web client in Saudi Arabia.
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 7, 10:28 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 7, 10:17 PDT
Monitoring - On 4/7/2026 between 16:42 UTC to 16:53 UTC, a subset of users may have experienced issues with Zoom Phone and Zoom Contact center with call drops in Singapore region.
This incident has been resolved and the affected services have been restored.
Apr 4, 01:32 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 4, 01:22 PDT
Monitoring - On 04/04/2026, between 6:05 UTC and 7:50 UTC, a subset of users may have experienced issues with Zoom Phone calls in North America region.
This incident has been resolved and the affected services have been restored.
Apr 3, 22:21 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 3, 21:40 PDT
Monitoring - The service degradation affecting a subset of users with Zoom Chat in the North America Region has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 3, 14:53 PDT
Update - 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 3, 05:57 PDT
Update - 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 2, 21:53 PDT
Update - 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 2, 17:53 PDT
Update - 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 2, 13:21 PDT
Update - 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 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 Chat 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 Chat 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 Chat 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 Chat 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 Chat 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 Chat 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 Chat 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 Chat 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 Chat 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 who upgraded Zoom Workplace client to 7.0.0 or 7.0.1 (Windows) version who are experiencing Zoom Chat stuck at "connecting..." status.
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.