Apr 16, 22:41 UTC
Resolved - This incident has been resolved.
Apr 16, 22:40 UTC
Update - We are continuing to monitor for any further issues.
Apr 16, 22:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 16, 22:26 UTC
Investigating - We are currently investigating this issue.
Apr 16, 21:29 UTC
Resolved - This incident has been resolved in the v1.3109.0 release of Claude Desktop. Please "Check for Updates".
Apr 16, 20:47 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 16, 19:24 UTC
Investigating - We are currently investigating this issue on the v1.3036.0 release of Claude Desktop
Apr 16, 07:43 UTC
Resolved - Earlier today we had an outage on Opus 4.6 that started at 23:03 PT / 6:03 UTC and ended at 00:26 PT / 7:26 UTC.
Apr 16, 06:50 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 15, 17:42 UTC
Resolved - This incident has been resolved.
Apr 15, 16:29 UTC
Update - We have seen success rates for login to Claude.ai, including via Claude Code, stabilize and are working to fully resolve this issue. We will provide an update shortly.
Apr 15, 15:40 UTC
Update - Claude.ai and Platform are down. Login for Claude Code does not work via Claude.ai.
Apr 15, 15:20 UTC
Update - The Claude API has fully recovered as of 8:01 PT / 16:01 UTC. We are currently working on mitigating the ongoing errors for Claude AI. Claude Code users who are logged in are still able to use it, but logging in is still broken.
Apr 15, 15:03 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 15, 14:55 UTC
Update - We are continuing to investigate this issue.
Apr 15, 14:53 UTC
Investigating - We are seeing increased errors on Claude.ai, API, and Claude Code
Apr 14, 15:21 UTC
Resolved - This incident has been resolved.
Apr 14, 13:20 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 14, 11:47 UTC
Identified - Root cause identified. Fixes have been merged and are progressing through our deployment pipeline. Intermittent 503 errors on usage and analytics admin API endpoints may continue until the rollout completes. We will update once the fix is live in production.
Apr 14, 09:24 UTC
Investigating - We are investigating reports of degraded performance affecting the usage and analytics admin API endpoints. We will provide an update as soon as possible.
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 16, 23:55 UTC
Resolved - This incident has been resolved.
Apr 16, 15:32 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 16, 14:22 UTC
Investigating - We are currently investigating a temporary drop in the availability of our Analytics API. We are working to mitigate this problem. More updates to follow shortly.
Apr 16, 22:10 UTC
Identified - The DEX analytics overtime data for CF1 client devices may show missing data.
Apr 16, 13:34 UTC
Resolved - This incident has been resolved.
Apr 16, 13:03 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 16, 13:02 UTC
Investigating - We are currently investigating a temporary drop in the availability of our Analytics API. We are working to mitigate this problem. More updates to follow shortly.
Apr 16, 13:30 UTC
Resolved - Cloudflare is aware of and has mitigated an issue which impacted Workers script uploads between 14:51 UTC to 15:00 UTC on 16th April 2026
This did not impact Workers traffic.
Apr 16, 12:48 UTC
Resolved - This incident has been resolved.
Apr 16, 12:40 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 16, 12:11 UTC
Investigating - Cloudflare is investigating issues with Cloudflare APIs. These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge. Customers using the Cloudflare APIs are impacted as requests might fail and/or errors may be displayed.
Apr 14, 15:00 UTC
Resolved - This incident has been resolved.
Apr 14, 12:33 UTC
Investigating - We are currently experiencing a service disruption with our chat tool, which is impacting conversations. Our chat tool team is actively investigating the issue and working towards a resolution. We will provide updates here as more information becomes available.
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.
Apr 13, 14:03 UTC
Resolved - The issue has been resolved.
Apr 13, 13:33 UTC
Monitoring - Customers are reporting spaces are accessible in the web app again. We are monitoring the situation.
Apr 13, 13:02 UTC
Investigating - Some customers are reporting spaces not being shown in the Contentful web app. We are investigating.
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.
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 16, 18: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 16, 18:22 UTC
Monitoring - The degradation affecting Codespaces has been mitigated. We are monitoring to ensure stability.
Apr 16, 16:37 UTC
Update - Our provider is implementing a mitigation and we are seeing signs of recovery.
Apr 16, 15:49 UTC
Update - We found an issue that impacts 70% of Codespaces. We are engaged with the provider and working towards mitigation.
Apr 16, 15:41 UTC
Update - Codespaces is experiencing degraded availability. We are continuing to investigate.
Apr 16, 15:08 UTC
Update - We are experiencing degraded performance in Codespaces related to creating a new Codespace or starting an existing Codespace from the VS Code editor. SSH connections to Codespaces are not impacted. We are working toward mitigation and will continue to keep you updated on progress.
Apr 16, 15:06 UTC
Investigating - We are investigating reports of degraded performance for Codespaces
Apr 14, 06:08 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 14, 06:07 UTC
Update - This incident has been resolved. We will continue to monitor to ensure stability. Thank you for your patience and understanding as we addressed this issue.
Apr 14, 06:07 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Apr 14, 04:40 UTC
Update - We identified an issue that impacts the Copilot Dashboard on the Insights tab and are working on mitigation. We will continue to keep you updated on progress.
Apr 14, 03:47 UTC
Update - The team continues to investigate issues accessing with Copilot Dashboard on the Insights tab. We will continue providing updates on the progress towards mitigation.
Apr 14, 02:40 UTC
Update - The Copilot Dashboard on the Insights tab is not accessible and we are continuing to investigate.
Apr 14, 02:37 UTC
Update - Degradation of Service - Insights Page
Apr 14, 01:57 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 13, 20:35 UTC
Resolved - On Sunday April 13th, 2026, between 18:53 UTC and 20:30 UTC, the GitHub Pages service experienced elevated error rates. On average, the error rate was 10.58% and peaked at 12.77% of requests to the service, resulting in approximately 17.5 million failed requests returning HTTP 500 errors. This was due to an automated DNS management tool (octodns) erroneously deleting a DNS record for a Pages backend storage host after its upstream data source intermittently failed to return the record, causing the tool to treat it as stale and remove it.
We mitigated the incident by re-creating the deleted DNS record. To prevent future incidents, we are implementing availability-zone-tolerant routing in the Pages frontend so that an unresolvable backend host triggers failover to healthy hosts rather than returning errors, adding safeguards to prevent automated deletion of DNS records owned by other systems, and improving logging and alerting for DNS resolution failures in the Pages serving path.
Apr 13, 20:32 UTC
Update - We have mitigated the issue with Pages.
Apr 13, 20:30 UTC
Monitoring - The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.
Apr 13, 19:57 UTC
Update - We are investigating reports of issues with Pages. We will continue to keep users updated on progress towards mitigation.
Apr 13, 19:56 UTC
Investigating - We are investigating reports of degraded availability for Pages
Apr 13, 17:40 UTC
Resolved - On April 13, 2026, between 14:41 UTC and 17:29 UTC, the Copilot service experienced degraded performance. All Copilot users were impacted by increased latency, and approximately 20% experienced request failures when interacting with Copilot Cloud Agent (CCA). On average, request latency increased to approximately 950ms. The GitHub User Dashboard also displayed intermittent errors loading Copilot quota information. CCA and the User Dashboard were impacted for approximately 2 hours and 56 minutes.
This was due to an infrastructure change that reduced the available compute capacity for a backend service responsible for Copilot rate limiting and quota management. The reduced capacity caused resource exhaustion under normal traffic load, leading to cascading failures in downstream request processing.
We mitigated the incident by increasing compute resources allocated to the affected service and scaling out the number of service instances to distribute load more effectively.
We are working to improve proactive capacity monitoring to detect resource degradation before it impacts users, reviewing retry and timeout configurations across dependent services to reduce amplification during degraded states, and evaluating connection management strategies to improve resilience under constrained resources.
Apr 13, 16:59 UTC
Update - We have identified the root cause and are rolling out a fix for Copilot. The services should now be in recovery, with expected full recovery in 5 to 10 minutes.
Apr 13, 16:41 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 10, 13:28 UTC
Resolved - On April 9, 2026, between 22:59 UTC and April 10, 2026, 13:24 UTC, the Copilot Mission Control service was degraded and did not display Claude and Codex Cloud Agent sessions in the agents tab dashboard. Customers were unable to see, list, or manage their third party agent sessions during this period. The underlying agent sessions continued to function normally. This was a visibility and management issue only, and no HTTP errors were generated. The API returned successful responses with incomplete results, with an average error rate of 0% and a maximum error rate of 0%. This was due to a code change that introduced a filter which inadvertently excluded third party agent sessions.
We mitigated the incident by reverting the problematic code change and deploying the fix to production.
We are working to add automated monitoring for dashboard content visibility and improve integration test coverage for third party agent session listing to reduce our time to detection and mitigation of issues like this one in the future.
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 16, 15:44 EDT
Resolved - Between 12:19 PM (UTC -07:00) and 12:40 AM (UTC -07:00), many customers in North America experienced issues with marketing tools, operations tools, sales tools, service tools. This was caused by a server impairment. As of 12:40 AM (UTC -07:00), our marketing tools, operations tools, sales tools, service 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 16, 15:32 EDT
Identified - We estimate that we will restore service in the next half an hour.
We are mitigating impact from a server impairment which we believe is caused by resource exhaustion. We are scaling the system.
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 16, 15:23 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 16, 11:36 EDT
Resolved - Between 10:56 AM (UTC -04:00) and 11:30 AM (UTC -04:00), many customers in all affected regions experienced issues with generating quotes from deal records. As of 11:30 AM (UTC -04:00), quote generation 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 16, 11:31 EDT
Identified - We have identified an issue impacting quote generation from deal records. Users can still create quotes from the quote index page. 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.
Apr 16, 11:16 EDT
Investigating - We are investigating an issue impacting sales tools. 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.
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 14, 16:11 UTC
Resolved - On April 14, 2026, affected users may have experienced some service disruption with automation rules that use Rovo agents. The issue has now been resolved, and the service is operating normally for all affected customers.
Apr 14, 15:46 UTC
Monitoring - The issue has been resolved, and services are now operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Apr 14, 14:11 UTC
Identified - We have identified the issue, and our teams are working to resolve it and restore normal operations as quickly as possible. We will provide further updates as they become available.
Apr 14, 12:25 UTC
Update - We have identified that this incident also affects automation rules in Confluence that use Rovo agents. We are investigating and will provide updates as we learn more.
Apr 14, 12:12 UTC
Investigating - We are actively investigating reports of a partial service disruption affecting Rovo, specifically for customers using automation rules that invoke Rovo agents. Some customers may find that these automations are not completing as expected. We'll share updates here as more information becomes available.
Apr 13, 10:17 UTC
Resolved - On April 13, 2026, between 05:49 a.m. and 06:25 a.m. UTC, some users were unable to log in to Atlassian products with their Atlassian accounts. The underlying issue has been addressed, and authentication services have remained stable with no new impact observed.
Apr 13, 08:33 UTC
Update - Atlassian account login services are now operating as expected, and we are not observing new errors. We continue to closely monitor our systems to ensure they remain stable. We will provide another update within 60 minutes or sooner if we detect a change in status.
Apr 13, 07:29 UTC
Monitoring - Our team is aware that some users were unable to log in to Atlassian products with their Atlassian accounts. While we believe this issue is now resolved, we are continuing to monitor all products and services for any ongoing impact.
Our team is investigating with urgency, and we will provide an update within 1 hour.
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.
Apr 15, 14:57 UTC
Monitoring - Our engineers have corrected the issue and we are confirming that the latest extension release has been approved. The fastest way to ensure you are running the latest version is to manually update your LastPass browser extension. We will continue monitoring the situation and provide a final update shortly.
Apr 14, 20:12 UTC
Update - The fix has been validated and submitted to the browser extension store for review. We are continuing additional testing during the review process and will share further updates as available.
Apr 14, 17:14 UTC
Update - A hotfix has been implemented and is under validation. After validation, we plan to release the update via the browser stores and begin a broader rollout. Further updates will follow.
Apr 13, 15:35 UTC
Identified - The issue has been identified and our engineering team is actively working through final validation.
Additional updates will be shared as more information becomes available.
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 13, 01:16 UTC
Resolved - This incident has been resolved. A fix was deployed for the issue affecting Scheduled Functions auto-triggering, and scheduled invocations have recovered. During the incident, manual executions continued to work, but some scheduled runs did not trigger automatically as expected.
Apr 13, 01:04 UTC
Monitoring - We implemented a fix for the issue affecting Scheduled Functions auto-triggering and are seeing signs of recovery. Manual executions were unaffected during the incident, and scheduled invocations now appear to be resuming. We are continuing to monitor closely
Apr 13, 00:39 UTC
Investigating - Investigating an issue affecting Scheduled Functions auto-triggering. Manual “Run now” executions are succeeding, but some scheduled functions are not automatically invoking at their expected times.Beginning around April 12, 2026 at 1:00 AM UTC and are actively investigating.
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.
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
- Responses (Operational)
All impacted services have now fully recovered.
Affected components
- FedRAMP (Operational)
All impacted services have now fully recovered.
Affected components
- Login (Operational)
- Login (Operational)
- Login (Operational)
All impacted services have now fully recovered.
Affected components
- Responses (Operational)
- Chat Completions (Operational)
- Embeddings (Operational)
Apr 15, 11:44 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with EU subusers unable to send emails has now been resolved. All services are now operating normally at this time.
Apr 15, 11:37 PDT
Monitoring - Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available.
Apr 15, 10:06 PDT
Update - We are continuing investigating this issue. We will provide more updates in 2 hours, or as soon as they become available.
Apr 15, 09:00 PDT
Investigating - Starting around 08:30 AM PST on April 15th, 2026, our engineers began investigating an issue with EU subusers that are unable to send emails. Customer may experience the error "User is not authorized to send mail based on their regional attribute." This is currently being investigated. This impacts mail send only for subusers located in EU. We will provide another update in an hour or as soon as more information becomes available.
Apr 15, 08:49 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with the support page and ticket creation has been resolved. All services are now operating normally at this time.
Apr 15, 08:28 PDT
Monitoring - Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available.
Apr 15, 08:19 PDT
Investigating - Starting around 07:30 AM PST on April 15th, 2026, our engineers began investigating an issue with users able to open support tickets. Customers are being redirected to a blank page when trying to open a support ticket, but chat options are still available. This does not impact mail send. We will provide another update in two hours or as soon as more information becomes available.
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 16, 16:08 UTC
Resolved - The fix has been rolled out and ingestion is recovered.
Apr 16, 15:05 UTC
Monitoring - The delay has recovered and we are monitoring the fix.
Apr 16, 14:30 UTC
Identified - We have identified the issue and are working on a fix.
Apr 16, 13:36 UTC
Investigating - We are currently investigating this issue.
Apr 13, 21:52 UTC
Resolved - Login with SSO in Chromium browser was broken. Users experienced form submission failures due to a bug in CSP. The problem is now fixed.
Apr 13, 20:31 UTC
Identified - Login with SSO in Chromium browser is broken right now. Signing in using cmd or ctrl + click on the "Login with Provider" button is a workaround you can use while our team fixes the issue.
Apr 13, 19:57 UTC
Resolved - Ingestion and alerts should be back to normal
Apr 13, 19:13 UTC
Investigating - US customers may experience delay in data ingestion and alerts. The issue is resolved and we are burning the backlog.
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
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 automatic migration to Forge is tentatively scheduled to begin on June 15, 2026. You have the option to do either of the following: • Perform a manual update Review the expected changes (see links below) and assess any impacts to your workflows. If the impact is manageable, we recommend updating manually to control the timing of your instance’s migration. • Wait for automatic update The automatic rollout will occur gradually, so we are unable to confirm the exact date your instance will be updated. It will not be possible to schedule, delay, or opt out once started. After your instance is updated, you will receive an in-app notification confirming the change. You can also verify if your instance has migrated to Forge by checking the app versions: https://tempo-io.atlassian.net/wiki/spaces/DRAFTTIMESHEETS/pages/5679415354/Timesheets+Migration+to+Forge+FAQs#How-to-Check-Your-Current-Version. 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 16, 13:54 PDT
Resolved - This incident has been resolved.
Apr 16, 13:40 PDT
Monitoring - The issue with our underlying provider affecting Zoom Rooms Microsoft Teams Meeting Direct Guest join feature has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 16, 12:41 PDT
Update - Our team continue to work with our underlying provider affecting Zoom Rooms Microsoft Teams Meeting Direct Guest join feature and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 16, 11:41 PDT
Update - Our team continue to work with our underlying provider affecting Zoom Rooms Microsoft Teams Meeting Direct Guest join feature and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 16, 10:44 PDT
Update - Our team continue to work with our underlying provider affecting Zoom Rooms Microsoft Teams Meeting Direct Guest join feature and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 16, 09:24 PDT
Identified - We have identified an issue with our underlying provider affecting Zoom Rooms Microsoft Teams Meeting Direct Guest join feature.
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 16, 04:37 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 16, 02:02 PDT
Monitoring - The issue preventing users with WEBRTC 2.0 feature ability to join Zoom meetings in Amsterdam and Germany has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 16, 01:30 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 16, 00:16 PDT
Identified - We have successfully identified the root cause preventing users with WEBRTC 2.0 feature with joining meetings in Amsterdam and Germany.
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 16, 00:12 PDT
Investigating - We are currently investigating a service degradation affecting users with WEBRTC 2.0 feature ability to join Zoom meetings in Amsterdam and Germany.
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 14, 18:31 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 14, 06:34 PDT
Monitoring - On 4/14/2026 between 12:28 UTC to 12:58 UTC, a subset of users may have experienced issues with Client login, AI Chat Compose, Meeting joining features & Dashboards in the Europe Region. Will continue to monitor the services.
This incident has been resolved and the affected services have been restored. Thank you for your patience.
Apr 14, 06:31 PDT
Investigating - On 4/14/2026 between 12:28 UTC to 12:58 UTC, a subset of users may have experienced issues with Client login, AI Chat Compose, Meeting joining features & Dashboards in the Europe Region.
This incident has been resolved and the affected services have been restored.
Apr 14, 11:26 PDT
Resolved - This incident has been resolved.
Apr 14, 10:27 PDT
Monitoring - The issue affecting trimming Meeting Recordings for subset of users in Europe region has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 14, 09:18 PDT
Investigating - We are currently investigating a service degradation impacting Trimming Meeting Recordings for subset of users in Europe 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 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.