Apr 25, 08:57 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 25, 08:43 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 25, 08:37 UTC
Resolved - This incident has been resolved.
Apr 25, 08:25 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 25, 07:48 UTC
Investigating - We are currently investigating this issue.
Apr 25, 02:35 UTC
Resolved - This incident has been resolved.
Apr 25, 01:45 UTC
Monitoring - We have identified an issue in Claude Code version 2.1.120 that causes a crash when resuming a prior session via the --resume or --continue flags. Auto-update will move affected clients back to 2.1.119 on next check, but you can always run `claude install 2.1.119`.
Apr 25, 02:34 UTC
Resolved - The issue affecting requests to Claude Opus 4.7 has been resolved. Impact occurred from 01:24–01:59 UTC.
Apr 25, 02:15 UTC
Monitoring - A fix has been deployed for Claude Opus 4.7 and we are seeing success rates at normal levels. We are continuing to monitor, and ensure no further recurrence.
Apr 25, 01:35 UTC
Investigating - We are investigating elevated errors for requests to Claude Opus 4.7. 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 24, 18:36 UTC
Resolved - Customers running macOS jobs on m4pro.medium and m4pro.large with the xcode:26.4.0 image experienced job rejections with the error: "Job was rejected because resource class
Customers whose jobs failed may rerun affected jobs.
We thank you for your patience while our team worked on implementing a fix.
Apr 24, 18:01 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 24, 17:25 UTC
Identified - There are build failures for Xcode 26.4.0; we have identified the issue and are currently implementing a fix.
Apr 18, 15:05 UTC
Resolved - The Usage API issue has been resolved. All data is now current. Appreciate your patience.
Apr 18, 13:17 UTC
Identified - The Usage API issue has been identified and a fix is being implemented. We expect to the issue be resolved within a few hours.
Apr 18, 12:07 UTC
Investigating - Usage API data is delayed this morning. Team is investigating.
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 24, 23:53 UTC
Resolved - This incident has been resolved.
Apr 24, 22:02 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 24, 20:17 UTC
Identified - A fix has been identified and is being deployed in a controlled rollout across impacted regions. Cloudflare engineering is observing a decrease in overall error rates as the rollout progresses. Errors will continue to occur intermittently until the deployment is complete across all affected infrastructure. We will continue to monitor and provide updates as the rollout advances.
Apr 24, 05:05 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 23, 21:05 UTC
Identified - Beginning April 21, a subset of Cloudflare Access customers experienced intermittent HTTP 500 errors on authentication requests. Impact is limited to a small percentage of requests in specific geographies. Service authentication requests are seeing the highest share of the errors.
Cloudflare engineering is progressing a corrected rollout under tighter monitoring.
Apr 24, 16:14 UTC
Resolved - This incident has been resolved.
Apr 24, 15:51 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 24, 14:34 UTC
Investigating - Cloudflare is investigating issues with Cloudflare WARP and Cloudflare Zero Trust. Cloudflare WARP and Zero Trust users in Bulgaria may experience connectivity issues or a degraded Internet experience.
Apr 24, 10:34 UTC
Resolved - This incident has been resolved.
Apr 24, 06:45 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 24, 02:40 UTC
Investigating - Cloudflare is investigating issues with Healthchecks monitoring, alert notifications and analytics. We are working to understand the full impact and mitigate this problem. More updates to follow shortly.
Apr 24, 10:30 UTC
Resolved - This incident has been resolved.
Apr 24, 01:00 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 24, 00:35 UTC
Investigating - Cloudflare is investigating issues with Cloudflare Dashboard and related APIs where the dashboard is displaying an incorrect error message on the UI at the bottom banner.
These issues do not affect the serving of cached files via the Cloudflare CDN or other security features at the Cloudflare Edge.
Apr 24, 03:48 UTC
Resolved - This incident has been resolved.
Apr 24, 03:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 24, 03:46 UTC
Investigating - Cloudflare is observing network performance issues in Miami. We are actively working to reduce or eliminate any impact to Internet users in this locations.
Apr 21, 02:15 UTC
Resolved - This incident has been resolved.
Apr 20, 14:51 UTC
Monitoring - A fix has been implemented by the cloud provider team and they are monitoring the results.
Apr 20, 12:33 UTC
Investigating - Our upstream provider Linode is currently investigating an emerging service issue affecting connectivity in their Frankfurt (DE-FRA-2) region. We will share further updates as soon as more information becomes available from the provider.
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.
Apr 23, 14:18 UTC
Resolved - The issue has been resolved.
Apr 23, 14:09 UTC
Identified - We are working on improving the situation and see reduced error rates on workflows management.
Apr 23, 13:39 UTC
Investigating - Some Customers are experiencing issues with workflows, we are investigating.
Apr 23, 11:57 UTC
Resolved - The issue has been resolved.
Apr 23, 11:52 UTC
Monitoring - The situation has improved. We will continue to monitor.
Apr 23, 11:38 UTC
Investigating - Some customers are experiencing 500 errors on our APIs. We are investigating.
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.
Apr 17, 00:30 EDT
Resolved - Earlier this morning, some accounts hosted on our Sydney servers experienced errors when loading forms, including “There was a problem on our end trying to load forms” and “An unknown error occurred.”
The issue has been resolved, and services have returned to normal. We will continue to monitor.
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.
Apr 25, 00: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 24, 19:14 UTC
Update - This is related to the public impact, "Multiservice impact for Azure Workloads in East US" shared at https://azure.status.microsoft/
Apr 24, 19:09 UTC
Update - We are investigating reports of degraded performance for Larger Runners with vnet injection in East US and we are working with our service provider on mitigation.
Apr 24, 19:02 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 23, 21:43 UTC
Resolved - This incident has been resolved and we've contacted repository administrators via email who have impacted branches.
Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will also be shared as soon as it is available.
Apr 23, 21:18 UTC
Update - We have resolved a regression present when using merge queue with either squash merges or rebases. If you use merge queue in this configuration, some pull requests may have been merged incorrectly between 2026-04-23 16:05-20:43 UTC.
This behavior is still present in GitHub Enterprise Cloud with Data Residency, and we are rolling out the same fix.
Apr 23, 20:47 UTC
Update - Pull Requests is operating normally.
Apr 23, 19:58 UTC
Update - We have identified a regression in merge queue behavior present when squash merging or rebasing. We have identified the root-cause and are in the process of reverting the change.
Apr 23, 19:50 UTC
Investigating - We are investigating reports of degraded performance for Pull Requests
Apr 23, 19:42 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 23, 19:33 UTC
Update - We have identified the root cause of the issue and are working on mitigation.
Apr 23, 19:28 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Apr 23, 17:30 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Apr 23, 17:10 UTC
Update - Webhooks is operating normally.
Apr 23, 17:04 UTC
Update - Many services are mitigated and are validating the remaining services.
Apr 23, 17:03 UTC
Update - The degradation affecting Actions and Copilot has been mitigated. We are monitoring to ensure stability.
Apr 23, 16:52 UTC
Update - We have identified the root problem and are working on mitigation.
Apr 23, 16:34 UTC
Update - Actions is experiencing degraded performance. We are continuing to investigate.
Apr 23, 16:19 UTC
Update - We are investigating multiple unavailable services.
Apr 23, 16:12 UTC
Investigating - We are investigating reports of degraded availability for Copilot and Webhooks
Apr 23, 15:18 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 23, 15:02 UTC
Monitoring - The degradation affecting Actions, Codespaces, Copilot and Packages has been mitigated. We are monitoring to ensure stability.
Apr 23, 15:02 UTC
Update - A mitigation was applied and services have recovered. Actions is working through queued work before fully recovering.
Apr 23, 14:51 UTC
Update - Users are experiencing errors loading various web pages on github.com. Actions and Copilot Cloud Agent runs will be delayed.
Apr 23, 14:44 UTC
Update - Copilot is experiencing degraded performance. We are continuing to investigate.
Apr 23, 14:42 UTC
Update - Codespaces is experiencing degraded performance. We are continuing to investigate.
Apr 23, 14:41 UTC
Update - Packages is experiencing degraded performance. We are continuing to investigate.
Apr 23, 14:40 UTC
Investigating - We are investigating reports of degraded performance for Actions
Apr 21, 15:37 EDT
Resolved - Between 08:57 AM EST and 3:34 PM EST some customers in North America experienced issues with workflow and automation delays. This was caused by an issue processing a small subset of actions causing a backlog in the processing. As of 3:34 PM EST, our systems are working properly and the incident has been fully resolved. We are continuing to monitor for further impact.
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 21, 14:33 EDT
Update - We've addressed the issue that caused workflows and automation to be delayed in North America since 09:22 AM EST. We're monitoring performance closely to ensure the tools recover properly. Some email workflow actions continue to be delayed up to 6 hours.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 21, 11:25 EDT
Monitoring - We've addressed the issue that caused workflow execution delays in North America since 08:57 AM EST. We're monitoring performance closely to ensure the tools recover properly.
The information on this page reflects our understanding of the incident and impact at the time of the update.
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 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 24, 14:57 UTC
Resolved - This incident has been resolved.
Apr 24, 14:44 UTC
Monitoring - We've confirmed that Image CDN errors have decreased, and we are continuing to monitor this issue.
Apr 24, 14:10 UTC
Investigating - We are currently experiencing an elevated error rate for Image CDN requests, starting at 13:35 UTC. We are investigating this issue.
Apr 23, 17:23 UTC
Resolved - This incident has been resolved.
Apr 23, 17:13 UTC
Monitoring - We've confirmed a decrease in the rate of build failures, which coincides with GitHub's restoration of impacted services. We are continuing to monitor this issue.
Apr 23, 16:23 UTC
Investigating - We're experiencing an increased rate of build failures beginning around 16:00 UTC, caused by a GitHub issue: https://www.githubstatus.com/incidents/myrbk7jvvs6p. We're currently investigating this issue.
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 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
- Codex API (Operational)
GPT-5.5 is now available to all paid users in Codex. If you continue to see access issues, please update to the latest Codex version. We’ll share another update if needed.
Affected components
- Codex Web (Operational)
- CLI (Operational)
- App (Operational)
- VS Code extension (Operational)
- Codex API (Operational)
Error rates and latency for the Moderation API have returned to normal levels after mitigation.
Affected components
- Moderations (Operational)
All impacted services have now fully recovered.
Affected components
- Conversations (Operational)
Apr 23, 14:18 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with module movement in the Design Editor has been resolved. All services are now operating normally at this time.
Apr 23, 10:16 PDT
Update - Our team is still investigating this issue, and we still don't have updates to provide. For now, latest recommendation persist:
For the best experience, please use the latest version of Safari or Firefox while we work on a fix.
We will provide another update as soon as more information becomes available.
Apr 22, 13:51 PDT
Identified - Our engineers are continuing to investigate the issue with the Design Editor preventing module movement. Initial findings suggest Chrome's latest update (ver.147) from last Wednesday may be the cause.
For the best experience, please use the latest version of Safari or Firefox while we work on a fix.
We will provide another update as soon as more information becomes available.
Apr 22, 11:36 PDT
Update - Our engineers are continuing to investigate the issue with the Design Editor preventing module movement. Initial findings suggest Chrome's latest update (ver.147) from last Wednesday may be the cause.
For the best experience, please use the latest version of Safari or Firefox while we work on a fix.
We will provide another update in 2 hours or as soon as more information becomes available.
Apr 22, 10:41 PDT
Update - Our engineers are continuing to investigate the issue with the Design Editor preventing module movement. We will continue to provide another update in 2 hours or as soon as more information becomes available.
Apr 22, 09:32 PDT
Investigating - Starting around 8:22 AM PST on April 22nd, 2026, our engineers began investigating an issue where module movement is not functioning properly within the Design Editor. Customers may experience the inability to select modules for drag-and-drop repositioning. This does not impact mail send. We will provide another update in an hour or as soon as more information becomes available.
Apr 18, 13:07 PDT
Resolved - Our engineers have investigated and resolved the issues with delayed delivery of emails for a subset of customers. From 12:05 pm PST to 12:45 pm PST customers may have seen a delay in the delivery of their emails. The issue has been resolved and all impacted services are operating normally.
Apr 17, 06:13 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with Marketing Campaign uploads and deletion has been resolved. All services are now operating normally at this time.
Apr 17, 05:52 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 17, 04:58 PDT
Investigating - Starting around 04:30 PST on April 17th, 2026, our engineers began investigating an issue with contact upload delays when using TNE Marketing Campaings (Legacy Marketing is NOT affected). Customer may experience delays after uploading or deleting contacts using their Marketing Campaing plans. This does not impact mail send. We will provide another update in 2 hours or as soon as more information becomes available.
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 23, 02:17 UTC
Resolved - All application features are now operating as normal.
Apr 23, 02:12 UTC
Monitoring - Ingestion for spans and replays is about 10 minutes behind and catching up. API and Dashboard performance has returned to normal.
Apr 23, 02:06 UTC
Investigating - We are currently investigating this issue.
Apr 22, 08:26 UTC
Resolved - Between 07:25 UTC and 07:28 UTC, customers sending data to the legacy ingestion endpoint in our US region experienced a brief ingestion disruption lasting approximately 3 minutes. The issue has been fully resolved and ingestion is operating normally.
Customers using modern DSN endpoints (`*.ingest.us.sentry.io`) were not affected.
The disruption occurred during a scheduled configuration change. We're investing in additional tooling to detect and mitigate this class of issue faster. We apologize for the inconvenience and appreciate your patience.
Apr 17, 19:16 UTC
Resolved - This incident has been resolved.
Apr 17, 19:13 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 17, 19:04 UTC
Investigating - We are currently investigating this issue.
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.
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 25, 04:19 UTC
Resolved - This incident has been resolved.
Apr 25, 04:12 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 25, 03:07 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 25, 02:20 UTC
Update - We're continuing to investigate reports of customers being unable to checkout with domains purchases. We're also investigating reports of being unable to purchase AI gateway credits. We'll provide additional updates as they become available.
Apr 25, 00:39 UTC
Investigating - We're investigating reports of customers being unable to checkout with domains purchases. We'll provide additional updates as they become available.
Apr 23, 01:12 UTC
Resolved - This incident has been resolved.
Apr 23, 00:51 UTC
Monitoring - A fix has been implemented for the issue causing delays in loading logs and we are seeing signs of recovery. We'll provide additional updates as-needed.
Apr 22, 23:08 UTC
Identified - We've identified an additional issue causing delays in loading logs. We'll provide additional updates as they become available.
Apr 22, 22:25 UTC
Monitoring - A fix has been implemented for the issue causing delays in loading logs and we are seeing signs of recovery. We'll provide additional updates as-needed.
Apr 22, 21:41 UTC
Update - We are continuing to implement a fix for the issue causing delays in loading logs. We will provide additional updates as they become available.
Apr 22, 19:31 UTC
Update - We are continuing to implement a fix for the issue causing delays in loading logs. We will provide additional updates as they become available.
Apr 22, 19:02 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 22, 18:25 UTC
Investigating - We're investigating an issue causing delays in loading logs. We will provide additional updates as they become available.
Apr 22, 23:00 UTC
Resolved - We've identified an issue causing missing observability data for compute products between April 22, 2026 23:00 UTC and April 23, 2026 05:00 UTC affecting a subset of customers, resulting in missing or incomplete metrics in Observability dashboard during this period.
All underlying compute services - including Vercel Functions, Workflows, and Cron Jobs - continued to operate normally. Logs were not affected and remain fully available.
Apr 21, 14:41 UTC
Resolved - This incident has been resolved.
Apr 21, 14:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 21, 14:21 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 21, 13:51 UTC
Investigating - We are currently investigating this issue.
Apr 20, 22:18 UTC
Resolved - This incident has been resolved.
Apr 20, 22:08 UTC
Monitoring - We have implemented a fix targeted at usage anomalies and are now observing recovery across all anomaly alerts. We will share any additional updates as-needed.
Apr 20, 21:34 UTC
Update - We are continuing to work on a fix for usage anomalies. We'll provide additional updates as they become available.
Apr 20, 18:50 UTC
Update - We are continuing to work on a fix for usage anomalies. We'll provide additional updates as they become available.
Apr 20, 16:51 UTC
Update - We have resolved the issue for error anomalies, and are continuing to work on a fix for usage anomalies.
Apr 20, 14:10 UTC
Update - We are continuing to work on a fix for this issue.
Apr 20, 12:21 UTC
Update - We are continuing to work on a fix for this issue.
Apr 20, 10:40 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 20, 09:38 UTC
Investigating - We are currently investigating Observability Alerts not detecting new events. We will share more updates as soon as we have more information.
Apr 23, 08:41 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 23, 08:14 PDT
Monitoring - The issue affecting Zoom Virtual Agent - Voice bot in North America region from 06:32 AM PDT to 07:13 AM PDT (April 23) has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 22, 21:42 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 22, 21:28 PDT
Monitoring - The issue affecting Zoom Phone Services in North America has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 22, 21:11 PDT
Investigating - We are currently investigating a service degradation affecting Zoom Phone Services in North America.
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 20, 03:06 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 20, 02:19 PDT
Monitoring - The issue affecting users using Zoom Client 7.0.0 and above with My Notes feature disabled to view live transcriptions in Meetings has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 20, 01:14 PDT
Update - Our team continue to work on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 19, 23:25 PDT
Identified - We have successfully identified the root cause affecting users using Zoom Client 7.0.0 and above with My Notes feature disabled to view live transcriptions in Meetings.
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 19, 23:05 PDT
Investigating - We are currently investigating a service degradation affecting Zoom Client 7.0.2 users to view live transcriptions in Meetings.
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 18, 00:22 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Apr 18, 00:12 PDT
Monitoring - The service degradation impacting SMS Delivery in North America region has been successfully resolved by our vendor and a downstream carrier. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Apr 17, 22:44 PDT
Update - We are actively working with our vendor on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 17, 20:59 PDT
Identified - We have successfully identified the root cause of a service degradation impacting SMS Delivery in North America region.
We are actively working with our vendor on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Apr 17, 19:29 PDT
Investigating - We are currently investigating a service degradation impacting SMS Delivery in 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 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.