Jun 17, 16:28 UTC
Resolved - This incident has been resolved.
Jun 17, 16:01 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 17, 15:34 UTC
Investigating - We are currently investigating this issue.
Jun 17, 10:03 UTC
Resolved - This incident has been resolved.
Jun 17, 09:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 17, 08:54 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 17, 08:24 UTC
Investigating - We are currently investigating this issue.
Jun 17, 06:37 UTC
Resolved - This incident has been resolved. Requests to Claude Opus 4.8 received elevated errors between 9:59pm PT / 04:59 UTC and 10:41pm PT / 05:41 UTC.
Jun 17, 05:44 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 17, 05:08 UTC
Investigating - We are currently investigating this issue.
Jun 17, 02:50 UTC
Resolved - This incident has been resolved.
Jun 17, 01:52 UTC
Identified - At this time, success rates for Claude Sonnet 4.6 have recovered and we are working to resolve an issue resulting in elevated errors on Opus 4.8. We will provide additional updates as soon as possible.
Jun 17, 00:47 UTC
Investigating - We are currently investigating this issue.
Jun 16, 22:02 UTC
Resolved - This issue has been resolved. We saw elevated errors on requests to Claude Opus 4.8 between 1:45pm PT / 20:45 UTC and 1:58pm PT / 20:58 UTC.
Jun 16, 21:01 UTC
Monitoring - We have resolved the issue resulting in elevated errors on requests to Claude Opus 4.8, and are currently monitoring closely to prevent any further issues.
Jun 16, 20:50 UTC
Investigating - We are investigating elevated errors on requests to Claude Opus 4.8. We will provide an update as soon as possible.
Jun 12, 00:18 UTC
Resolved - Customers using Bitbucket as their VCS provider or as their login provider experienced errors when interacting with Bitbucket repositories and authenticating to CircleCI. This was caused by an incident with Atlassian Bitbucket's OAuth service, which has now been resolved and all affected functionality has returned to normal.
Jun 12, 00:10 UTC
Monitoring - What's happening
Atlassian Bitbucket has moved their OAuth service incident to monitoring. You can follow their status at https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx
What's impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitbucket as their login provider may also be unable to authenticate to CircleCI.
Thank you for your patience while we continue to monitor recovery.
Jun 11, 22:57 UTC
Update - What's happening
Atlassian Bitbucket has acknowledged an incident affecting their OAuth service, which is the cause of the errors our customers are experiencing. The status of their incident is available at: https://bitbucket.status.atlassian.com/incidents/h51sr145gsmx
What's impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Customers using Bitbucket as their login provider may also be unable to authenticate to CircleCI.
We will provide an update as soon as we have more information. Thank you for your patience while we monitor Bitbucket's incident and recovery.
Jun 11, 22:05 UTC
Identified - What's happening
We are investigating an issue we believe is related to an ongoing incident with Atlassian Bitbucket's authentication service. We are actively monitoring Bitbucket's status.
What's impacted
Customers using Bitbucket as their VCS provider may be experiencing disruptions.
What can you expect
You may see errors when CircleCI attempts to interact with your Bitbucket repositories. Thank you for your patience while our engineers investigate.
We will provide an update as soon as we have more information.
Jun 11, 21:31 UTC
Investigating - We are currently investigating this issue.
Jun 10, 23:07 UTC
Resolved - This incident has been resolved.
Jun 10, 22:56 UTC
Monitoring - The fix has been rolled out and we are monitoring for recovery.
Jun 10, 22:55 UTC
Identified - We have identified the cause of the failure and are rolling out a change.
Jun 10, 22:39 UTC
Investigating - We are investigating reports of orb publishing failing.
Jun 10, 16:41 UTC
Resolved - This incident has been resolved.
Jun 10, 16:32 UTC
Monitoring - We are seeing signs of recovery from the GitHub API.
Jun 10, 16:30 UTC
Update - We are continuing to investigate this issue.
Jun 10, 16:30 UTC
Investigating - Some users may have seen delays or missing commit statuses on GitHub PRs due to an ongoing GitHub API incident.
We are continuing to process builds as normal.
We will provide further updates as we get more information
Jun 9, 18:43 UTC
Resolved - Between 13:29 UTC and 18:20 UTC on June 9, 2026, some customers experienced 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs running were not impacted during this window. The issue has been resolved and all affected functionality has returned to normal. We thank you for your patience while our team worked on implementing a fix.
Jun 9, 18:32 UTC
Monitoring - A fix has been deployed for the 500 errors customers were experiencing on the pipeline values and workflow API endpoints and in the UI. Engineers are monitoring the change. Jobs running are not impacted
Jun 9, 18:20 UTC
Update - Our engineers are continuing to investigate the 500 errors customers are experiencing on the pipeline values and workflow API endpoints, as well as errors in the UI. Jobs currently running are not impacted.
Jun 9, 17:45 UTC
Investigating - Some customers are experiencing 500 errors when making requests to the pipeline values and workflow API endpoints, as well as errors in the UI.
Engineers are actively investigating.
Jun 7, 04:44 UTC
Resolved - This issue has been resolved and macOS jobs across all resource classes are starting normally again. Customers whose jobs failed to start during this window may rerun them. We thank you for your patience while our team worked on implementing a fix.
Jun 7, 04:20 UTC
Identified - We have identified an issue causing macOS jobs to fail to start and are working to restore service. This impacts customers running macOS jobs across all resource classes.
Thank you for your patience while our engineers work to resolve this. We will provide another update within 30 minutes.
Jun 17, 12:57 UTC
Resolved - This incident has been resolved.
Jun 17, 12:13 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 17, 11:34 UTC
Identified - Cloudflare Network Interconnect customers using may experience issues related to BGP functionality and route propagation. The issue has been identified and a fix is being implemented.
Jun 17, 11:44 UTC
Resolved - This incident has been resolved.
Jun 17, 10:32 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 17, 09:42 UTC
Update - We are continuing to work on mitigating this issue.
Jun 17, 08:07 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 17, 07:26 UTC
Investigating - Cloudflare has identified an issue impacting some customers where Workers Observability queries may be returning errors. We are working to mitigate the impact.
Jun 17, 00:52 UTC
Identified - We have identified an additional path that leads to users not seeing the correctly reflected payment state on invoices and are working on a fix.
Jun 16, 22:51 UTC
Investigating - We are currently investigating this issue.
Jun 16, 15:53 UTC
Identified - Customers may not see invoice payment status accurately reflected in the Cloudflare UI for payments made since June 11.
Impacted customers will see paid Invoices shown as Unpaid via the Cloudflare Dashboard.
Jun 16, 14:04 UTC
Update - Cloudflare is aware of and investigating Workers AI experiencing degraded availability in some models.
Impacted models:
- @cf/moonshotai/kimi-k2.6
- @cf/moonshotai/kimi-k2.7-code
Jun 16, 14:02 UTC
Investigating - We are currently investigating this issue.
Jun 6, 05:04 UTC
Resolved - Our upstream provider, Vultr, has resolved the network connectivity issue affecting their Chicago location.
Jun 6, 00:37 UTC
Investigating - Our upstream provider Vultr is currently experiencing a partial outage in their Chicago - United States location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.
Jun 3, 06:50 UTC
Resolved - This incident has been resolved.
Jun 2, 17:37 UTC
Monitoring - A fix has been implemented by the Cloudlfare and they are monitoring the results.
Jun 1, 15:21 UTC
Investigating - Cloudflare is currently investigating issues related to the SaaS Custom Hostname API. Customers may experience slow responses when adding new domains, and newly added domains may also encounter SSL-related errors. Existing domains or applications using Cloudflare remain unaffected and are operating normally.
We will provide further updates as soon as more information becomes available.
May 28, 12:26 UTC
Resolved - This incident has been resolved.
May 25, 13:04 UTC
Investigating - We are currently receiving multiple reports from customers who are unable to add mailboxes or log in to their Rackspace mailboxes.
The issue has already been identified by the Rackspace team, and they are actively working toward a resolution. We will update our status page with further information as soon as we receive additional updates from Rackspace. We sincerely apologize for the inconvenience caused and appreciate your patience and understanding.
May 20, 12:40 UTC
Resolved - This incident has been resolved.
May 20, 02:48 UTC
Monitoring - DO team has implemented mitigation measures for the infrastructure issue affecting Block Storage Volumes in the NYC3 region. The team is monitoring the situation, and we will share another update once the issue is fully resolved
May 20, 01:31 UTC
Investigating - We are observing an issue with some of the Block Storage Volume Performance in the New York region on Digital Ocean. During this time, users may experience degraded write performance and intermittent impact to services dependent on the affected storage infrastructure. Our Engineering team is working closely with DO team to resolve this issue. We apologize for the inconvenience and will share an update once we have more information.
May 19, 17:58 UTC
Resolved - This incident has been resolved.
May 19, 14:21 UTC
Investigating - Our upstream provider, Vultr, is currently experiencing a partial outage at their Seoul, Korea location. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.
Jun 12, 20:40 UTC
Resolved - We have resolved the issue.
Jun 12, 15:49 UTC
Update - We continue working towards full resolution.
Jun 12, 13:48 UTC
Identified - A small amount of EU customers might still experience issues related to locale-based publishing. We are working on resolving these.
Jun 12, 12:26 UTC
Monitoring - We have resolved the issue for all affected customers and are monitoring.
Jun 12, 11:02 UTC
Update - We have resolved the issue for the majority of customers and are continuing working on full resolution.
Jun 12, 07:53 UTC
Identified - Some customers in the EU may experience issues finding content via full-text search. We have identified the issue and are working on a resolution.
Jun 11, 21:00 UTC
Resolved - We have resolved the issue.
Jun 11, 17:05 UTC
Update - We continue working on the fix and have already seen resolution for the majority of customers affected by it.
Jun 11, 15:24 UTC
Update - We continue working on the resolution.
Jun 11, 13:37 UTC
Update - Editing and publishing errors have been resolved, but some published entries may not yet appear in filtered API requests for a small amount of EU customers. We continue working on the resolution.
Jun 11, 12:29 UTC
Identified - Some customers in the EU might see intermittent problems with editing and publishing content. We have identified the underlying issue and are working to resolve it.
Jun 9, 14:18 UTC
Resolved - We have resolved the underlying issue, the Optimization Hub is available again.
Jun 9, 13:57 UTC
Identified - The Optimization tab is unavailable for Contentful Personalization and Contentful Analytics customers.
Jun 2, 14:51 UTC
Resolved - We think the impact from the issue is over, however, uploads using 3rd cloud providers (Google Drive, Instagram, Box, Dropbox etc) are temporarily disabled.
Jun 2, 13:27 UTC
Identified - Uploads via 3rd party cloud integrations are affected. We are working on a resolution.
Jun 2, 13:02 UTC
Investigating - Some customers are experiencing issues uploading files. We are investigating.
May 26, 17:17 UTC
Resolved - The issue has been resolved.
May 26, 17:08 UTC
Monitoring - We have addressed the issue and are monitoring the situation.
May 26, 17:02 UTC
Investigating - Some customers are experiencing issues with the Contentful Web App. We are investigating.
Jun 16, 15:20 EDT
Investigating - We are aware of an issue affecting customers in the UK accessing FormAssembly via BT Internet Service Provider and its subsidiaries (including EE). Affected users may be unable to reach FormAssembly instances and forms.
This issue appears to be network-specific. If you are affected, connecting via an alternative network (such as a mobile data connection or a different ISP) should restore access.
Our team is actively investigating. We will provide updates as we learn more.
May 21, 01:30 EDT
Resolved - Earlier today, one of our sending IPs was listed on a third-party blocklist, causing some outbound email notifications to be blocked or delayed by recipient mail servers. The IP has since been delisted, and email delivery has returned to normal. We apologize for the disruption.
May 20, 15:30 EDT
Resolved - This incident has been resolved. Please note that responses received during the downtime may need to be reprocessed for the connector run to complete. Please check your response log to confirm.
May 20, 11:43 EDT
Update - We are continuing to investigate this issue.
May 20, 11:41 EDT
Investigating - Our team is currently investigating reports of loss of access to a small subset of Team and Enterprise accounts. We will update here with more information shortly.
Apr 22, 00:00 EDT
Resolved - Between April 22 and May 18, 2026, an issue caused Form Analytics metrics to be recorded incorrectly, resulting in metrics detail loss for that period. Form submissions and response data were not affected. The issue has since been identified and resolved.
Our team is actively working to recover form submission counts for the affected timeframe.
Please note that other metrics, including form views, drop-offs, and bounced views, will not display data for the affected period.
We sincerely apologize for the disruption.
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.
Jun 17, 04:44 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 17, 04:44 UTC
Monitoring - Copilot is operating normally.
Jun 17, 04:26 UTC
Update - We've applied a mitigation to unblock Copilot functionality. Users may start to see signs of recovery. Relaunching your client should accelerate signs of recovery. We will continue to monitor the situation.
Jun 17, 03:52 UTC
Update - We are experiencing degraded availability for chat & agent models in Copilot. Multiple models are impacted and customers may experience requests failing. We are investigating and will provide an update as soon as possible.
Jun 17, 03:50 UTC
Investigating - We are investigating reports of degraded availability for Copilot
Jun 16, 18:15 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Jun 16, 18:14 UTC
Update - The issues with our upstream model provider have been resolved, and Opus 4.8 is once again available in Copilot products and IDE surfaces.
We will continue monitoring to ensure stability, but mitigation is complete.
Jun 16, 18:00 UTC
Monitoring - The degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.
Jun 16, 17:47 UTC
Update - We are experiencing degraded availability for the Opus 4.8 model in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue, we recommend choosing another model or selecting 'Auto' to continue using Copilot.
Jun 16, 17:45 UTC
Investigating - We are investigating reports of degraded availability for Copilot AI Model Providers
Jun 15, 19:10 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.
Jun 15, 19:10 UTC
Update - We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services. Customers may have experienced failed requests or degraded functionality. A fix has been deployed and error rates are steadily decreasing. All affected services are now mitigated and we are monitoring recovery.
Jun 15, 19:02 UTC
Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
Jun 15, 18:32 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Jun 15, 17:37 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.
Jun 15, 16:39 UTC
Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 15, 16:39 UTC
Update - Webhooks delivery latency has returned to normal levels. The backlog that built up during the incident has been cleared at approximately 4:29 UTC. We consider this incident resolved.
Jun 15, 15:37 UTC
Investigating - We are investigating reports of degraded performance for Webhooks
Jun 11, 22:19 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.
Jun 11, 20:00 UTC
Monitoring - The degradation affecting Webhooks has been mitigated. We are monitoring to ensure stability.
Jun 11, 19:58 UTC
Update - We have applied a mitigation and are monitoring for recovery.
Jun 11, 19:42 UTC
Update - We are currently experiencing delays in Web Hook delivery and are actively investigating the root cause.
Jun 11, 19:42 UTC
Investigating - We are investigating reports of degraded performance for Webhooks
Jun 12, 14:36 EDT
Resolved - Between 04:05 PM (UTC +02:00) and 08:35 PM (UTC +02:00), all customers in all affected regions experienced issues with Meta service integrations including WhatsApp, Facebook, Instagram and Ads. This was caused by disruptions to Meta services. As of 08:35 PM (UTC +02:00), our Meta service integrations including WhatsApp, Facebook, Instagram and Ads 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.
Jun 12, 13:49 EDT
Update - Most Meta service integrations, including WhatsApp, Facebook, Instagram, and Ads, have recovered. The disruption started at 4:05 PM UTC+02:00 due to issues with Meta services. But, connecting a new phone number to HubSpot and some Coexistence messages are still disrupted. We are monitoring Meta's recovery for these remaining issues. You can follow the issue here: https://metastatus.com/
We will be back with an update within 1 hour.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 12, 13:20 EDT
Monitoring - We are monitoring recovery of service integrations, including WhatsApp, Facebook, Instagram, and Ads, after disruptions to Meta services caused impairment since 4:05 PM UTC+02:00. Meta services appear to be recovering, and we are verifying that all integrations are functioning normally. You can follow the issue here: https://metastatus.com/
We will be back with an update within 1 hour.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 12, 12:19 EDT
Update - We have identified the cause of impaired service integrations, including WhatsApp, Facebook, Instagram, and Ads, since 4:05 PM UTC+02:00 due to disruptions to Meta services. We are monitoring Meta's recovery closely and will confirm once all integrations are functioning normally. You can follow the issue here: https://metastatus.com/
We will be back with an update within 2 hours.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 12, 11:19 EDT
Identified - We have identified the cause of impaired service integrations, including WhatsApp, Facebook, Instagram, and Ads, since 4:05 PM UTC+02:00 due to disruptions to Meta services. We are monitoring Meta's recovery closely and will confirm once all integrations are functioning normally. You can follow the issue here: https://metastatus.com/
We will be back with an update within 1 hour.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 12, 10:50 EDT
Update - Meta service integrations including WhatsApp, Facebook, Instagram and Ads have been impaired since 04:05 PM (UTC +02:00). We are investigating the cause and will update this page when we have more information. We will be back with an update within 1h.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 12, 10:44 EDT
Update - Meta service integrations including WhatsApp, Facebook, Instagram and Ads have been impaired since 04:05 PM (UTC +02:00). We are investigating the cause and will update this page when we have more information. We will be back with an update within 1h.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 12, 10:32 EDT
Investigating - We are investigating an issue impacting sending WhatsApp messages through HubSpot’s integrations. 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.
May 12, 10:55 EDT
Resolved - Between 02:47 PM (UTC +01:00) and 03:15 PM (UTC +01:00), some customers in all affected regions experienced issues with all impaired tools. This was caused by a database impairment. As of 03:15 PM (UTC +01: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.
May 12, 09:57 EDT
Investigating - We're investigating reports that HubSpot may be unavailable for some users. We'll update this page when we have more information.
May 7, 23:14 EDT
Resolved - Between 05:23 PM (UTC -07:00) and 07:56 PM (UTC -07:00), HubSpot experienced degradation in portals in the U.S. . This was related to an AWS outage. HubSpot is now working properly and the incident has been 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
May 7, 22:07 EDT
Update - We are experiencing degradation in portals in the U.S. which is related to AWS outage. We are working with AWS on the full resolution.
We will be back with an update within 30 minutes
The information on this page reflects our understanding of the incident and impact at the time of the update.
May 7, 21:36 EDT
Identified - We are experiencing degradation in portals in the U.S. which we believe is related to AWS outage.
We are working with AWS to resolve the issue. We will be back with an update within 30 minutes.
The information on this page reflects our understanding of the incident and impact at the time of the update.
May 2, 15:31 EDT
Resolved - HubSpot has continued to monitor the fix and believe we have addressed the underlying issue. Some messages deployed before May 1, 5 pm EDT may still experience delayed deliveries or failures over the next ~48 hours as retries and queues fully clear.
May 1, 12:34 EDT
Update - In April, some customers may have experienced intermittent DMARC failures on messages to Microsoft-hosted inboxes. Impact was most visible for senders with a DMARC policy of p=reject or p=quarantine. The root cause was related to how certain email headers were being handled.
We have implemented a fix and will continue to monitor closely. While there may still be some residual impact to messages with elongated headers and as outstanding retries and queue delays clear over the next ~72 hours, we expect impact to remain limited.
May 1, 11:52 EDT
Monitoring - In April, some customers may have experienced intermittent DMARC failures on messages to Microsoft-hosted inboxes. Impact was most visible for senders with a DMARC policy of p=reject or p=quarantine. The root cause was related to how certain email headers were being handled.
We have implemented a fix and will continue to monitor closely. While there may still be some residual impact to messages as outstanding retries and queue delays clear over the next ~72 hours, we expect impact to remain limited.
Apr 30, 11:10 EDT
Resolved - Between April 23 and April 29, some customers in experienced issues with publishing Instagram posts. This was caused by an integration issue. As of April 29 6:17 PM, our social publishing 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 29, 22:15 EDT
Monitoring - We have mitigated an issue with publishing of some Instagram posts since April 23. We're monitoring performance closely to make sure the tools recover properly.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Apr 29, 16:02 EDT
Identified - We estimate that we will restore service in the next several days.
We are mitigating impact from an issue with a third-party integration, and monitoring the situation closely. If you have trouble posting, please retry or post directly on Instagram.
We will be back with an update within 6 hours.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Jun 10, 10:00 UTC
Resolved - On June 10 2026, between 08:10 and 09:08 UTC, users experienced degraded performance and inability to load the Assets page, which is impacting the ability to create, update, and delete assets.
We have implemented a fix and services have been restored to normal operation for all affected customers.
Jun 10, 09:42 UTC
Investigating - Users are facing degraded performance while accessing Assets page which is impacting Assets object creation, updation and deletion activities. Our teams are investigating actively and will be sharing more details in next 1 hour.
Jun 10, 06:31 UTC
Resolved - We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected.
We apologize for any inconvenience that this issue may have caused.
Jun 10, 06:14 UTC
Monitoring - Our team has now determined that performance has returned to expected levels for those impacted by this incident.
Additional products that are now known to have been impacted by this incident are Confluence, Customer Service Management, and Jira Product Discovery. These products would have seen similar impact where email notifications or processing of events may have been delayed while this incident was underway.
We are now monitoring for the full recovery of performance across all products and will update when we are confident this issue is fully resolved, or within one hour, whichever is sooner.
Jun 10, 05:39 UTC
Identified - Our team has identified the root cause for this issue and has now deployed a fix that is rolling out across impacted products.
At this time we are monitoring for the recovery of these events across Jira Service Management, Jira Cloud and Ecosystem app Scheduled Triggers.
We will provide further update within one hour or when we have seen a full recovery of all task processing across these products.
Jun 10, 04:55 UTC
Investigating - We are investigating reports of extended delays being experienced across tasks such as processing of Incoming Emails, Notifications relating to changes or creation of Work Items, in addition to delays in processing Scheduled Triggers from Marketplace apps.
Our team is looking into this with urgency and we will provide further update within one hour as our investigation continues.
Jun 9, 18:27 UTC
Resolved - The issue has now been resolved, and the service is operating normally for all affected customers.
Jun 9, 10:36 UTC
Monitoring - Our team has been able to apply the fix and mitigate the issue. The services have been restored to normal operations.
We will continue to actively monitor over the next 8 hours to confirm stability.
Jun 9, 10:21 UTC
Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.
We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.
Jun 9, 10:20 UTC
Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.
We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.
Jun 9, 09:27 UTC
Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.
We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.
Jun 9, 09:26 UTC
Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.
We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.
Jun 9, 06:22 UTC
Update - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.
We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.
Jun 9, 06:21 UTC
Identified - Our team has now identified what we believe to be the root cause of this issue and is working on a fix. The expected fix for this issue will be rolling out progressively so customers should see resolutions to their issues viewing Jira boards and work items occurring over the next few hours.
We will provide further update either when the update has fully completed or within 3 hours, whichever occurs earlier.
Jun 9, 05:29 UTC
Investigating - We are investigating reports of intermittent errors and degredated performance for some Jira Service Management and Jira Cloud customers.
We will provide further updates within one hour.
Jun 8, 02:56 UTC
Resolved - On June 08 2026, between 01:30 and 02:40 UTC, users experienced degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.
We have implemented a fix and services have been restored to normal operation. We continue to monitor the situation closely.
Jun 8, 02:36 UTC
Identified - We have identified an issue causing degraded performance with Jira Software front-end experiences affecting view board, navigation, and backlog across multiple regions.
Our engineering team is actively working on a resolution. We will provide an update within the next hour.
Jun 8, 01:53 UTC
Investigating - We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. We'll provide an update here within the next hour, or sooner if new information becomes available.
Jun 2, 16:51 UTC
Resolved - On June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.
Jun 2, 15:32 UTC
Investigating - We are actively investigating reports of performance degradation affecting Jira and Jira Software Management customers. Some customers may experiences delays in rule execution. We'll provide an update here within the next hour, or sooner if new information becomes available.
Jun 15, 09:44 UTC
Resolved - This incident has been resolved.
Jun 13, 08:25 UTC
Monitoring - We are aware that requests to claude-fable-5 through Netlify AI Gateway are failing. Anthropic has suspended access to Claude Fable 5, and the model is currently unavailable. https://www.anthropic.com/news/fable-mythos-access
Jun 15, 01:45 UTC
Resolved - This incident has been resolved.
Jun 14, 20:23 UTC
Update - While recovery is in progress, enabling and disabling sites may take longer than usual. Customers using Bolt may continue to experience delays or intermittent errors when accessing, creating, or updating Bolt-powered sites
Jun 14, 19:55 UTC
Identified - We are currently investigating a connectivity issue affecting customers using Bolt. Some customers may be experiencing errors or degraded performance when attempting to use Bolt at this time.
Jun 9, 03:55 UTC
Resolved - This incident has been resolved.
Jun 9, 03:49 UTC
Monitoring - We are seeing recovery from the elevated latency affecting image delivery for some Netlify-hosted sites across our network. Error rates have decreased and image delivery performance has improved. Our engineering team is continuing to monitor the service to confirm stability. We will provide another update once the issue is fully resolved.
Jun 9, 03:41 UTC
Investigating - We are investigating elevated latency affecting image delivery for some Netlify-hosted sites
Some customers may experience slower image load times or intermittent errors when loading images. Our engineering team is actively working to mitigate the issue, and we will provide another update as soon as we have more information.Impact start time: 03:19 AM UTC
Jun 4, 20:59 UTC
Resolved - This incident has been resolved. Between approximately 17:00 and 20:30 UTC, a subset of sites using Edge Functions experienced elevated 504 error rates. We applied a mitigation and error rates have remained at normal levels since. We apologize for the impact to your sites and visitors.
Jun 4, 20:42 UTC
Monitoring - We have applied a mitigation and error rates for affected sites have returned to normal levels as of approximately 20:30 UTC. We are continuing to monitor the situation and will provide a final update once we have confirmed full recovery
Jun 4, 20:34 UTC
Identified - We have identified an issue with a subset of our Edge Functions infrastructure causing elevated 504 errors for some sites beginning at approximately 17:00 UTC. We are applying mitigations and error rates are improving. Customers do not need to take any action. We will continue to provide updates here.
Jun 4, 20:24 UTC
Investigating - Our team is investigating an increase in observed error rates affecting a subset of sites that use Edge Functions. Affected sites may see elevated 504 responses or slow page loads beginning at approximately 17:00 UTC. We are actively working to identify the cause and will provide updates here.
May 29, 15:30 UTC
Resolved - Between May 29th at 15:30 UTC till June 2 6:08 UTC, we experienced sporadic issues with Blobs in our Sydney region, affecting any Function using Blobs, including the ones that are generated by the framework runtimes. Our team has deployed a fix and the errors have subsided.
Jun 12, 12:57 UTC
Resolved - This incident has been resolved.
Jun 12, 12:44 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 12, 12:33 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 12, 12:08 UTC
Investigating - We are currently investigating this issue.
Apr 29, 20:49 UTC
Resolved - This incident has been resolved.
Apr 29, 20:49 UTC
Update - We are continuing to investigate this issue.
Apr 29, 20:07 UTC
Investigating - We are currently investigating this issue.
Apr 29, 19:35 UTC
Resolved - This incident has been resolved.
Apr 29, 18:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 29, 16:48 UTC
Investigating - We are currently investigating this issue.
Apr 28, 22:24 UTC
Resolved - This incident has been resolved.
Apr 28, 21:04 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 28, 19:55 UTC
Investigating - We are currently investigating this issue.
We are still investigating the issue for the listed services.
Affected components
- FedRAMP (Degraded performance)
All impacted services have now fully recovered.
Affected components
- Codex Web (Operational)
- CLI (Operational)
- App (Operational)
- VS Code extension (Operational)
- Codex API (Operational)
All impacted services have now fully recovered.
Affected components
- Codex Web (Operational)
All impacted services have now fully recovered.
Affected components
- Login (Operational)
- Login (Operational)
All impacted services have now fully recovered.
Affected components
- Login (Operational)
- Audio (Operational)
- Realtime (Operational)
- Responses (Operational)
- Sora (Operational)
- Images (Operational)
- Batch (Operational)
- Chat Completions (Operational)
- Fine-tuning (Operational)
- Files (Operational)
- Embeddings (Operational)
- Moderations (Operational)
Jun 14, 14:00 PDT
Resolved - Twilio-Sendgrid mail delivery was degraded for approximately 16 minutes between 3:18 PM and 3:34 PM Pacific Time on 06/14/2026. During this period of time customers may have experienced delays affecting a subset of users. User experience was degraded with delayed mail delivery during this window, though the scope was limited to affected users rather than a system-wide outage. The issue has now been resolved.
Jun 14, 12:23 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with high latency and 5xx errors has been resolved. All services are now operating normally at this time.
Jun 14, 11:11 PDT
Monitoring - Our engineers have implemented a fix and are monitoring system performance. We will continue to observe the platform for the next hour to ensure full stability, and will mark this incident as resolved if no further issues are seen. We will provide another update in 1 hour or as soon as more information becomes available.
Jun 14, 10:34 PDT
Identified - Our engineers have identified the issue and are working toward a fix. Mitigation efforts are underway to resolve the intermittent errors and delays. We will provide another update in 30 minutes or as soon as more information becomes available.
Jun 14, 10:20 PDT
Update - Engineers are still investigating issues causing email sending delays. We will provide a status update in 30 minutes or as soon as more information becomes available.
Jun 14, 09:45 PDT
Investigating - Starting around 12:00 AM PDT on June 14, 2026, our engineers began investigating an issue with our core API and platform services. Users may experience high latency, timeouts, and 5xx errors with sending email through the API and the UI. We will provide another update in 30 minutes or as soon as more information becomes available.
Jun 11, 10:05 PDT
Resolved - Twilio-Sengrid mail delivery was degraded for approximately 9 minutes between 9:18 AM and 9:27AM Pacific Time on 06/11/2026. During this period of time customers may have experienced delays affecting a subset of users.
User experience was degraded with delayed mail delivery during this window, though the scope was limited to affected users rather than system-wide outage.
The issue has now been resolved.
Jun 10, 01:49 PDT
Resolved - Our engineers have monitored the fix and confirmed the issue with email deferrals has been resolved. All services are now operating normally at this time.
Jun 9, 22:51 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.
Jun 9, 22:07 PDT
Investigating - Starting around 9:25 AM GMT+8 on June 10, 2026, our engineers began investigating an issue affecting email processing within SendGrid. Users may have experienced elevated email deferrals, with some messages temporarily receiving "Internal Server Error" responses during delivery attempts. This issue does not impact mail send capability; however, delivery may have been delayed for a subset of messages. Our team continues to investigate the root cause and monitor system performance. We will provide another update in 60 minutes or as soon as more information becomes available.
May 29, 07:30 PDT
Resolved - Customers have experienced elevated latency occurring in US East region from 6:30 AM to 8:58 AM Pacific time. Our engineers have investigated and resolved the issue. All impacted services are operating normally.
Jun 12, 11:30 UTC
Resolved - From approximately 10:55 UTC to 11:10 UTC we experienced a loss of outcomes which power the "Stats" in the organization settings.
The data loss is purely informational without impact on billing or ingested data.
Jun 11, 14:48 UTC
Resolved - This issue has been resolved.
Jun 11, 14:18 UTC
Update - The issue involving some alerts not firing has been mitigated. We will continue to monitor the situation to ensure it does not reoccur.
Jun 11, 13:23 UTC
Update - We have identified an issue with one of our cloud providers that might have caused some alert notifications to not fire starting at around 4:00 AM GMT+2.
Since around 1:30 PM GMT+2, alert notifications are now fully operational in the US region, while delivery is still partially degraded in the EU region.
Jun 11, 13:13 UTC
Monitoring - Notifications delivery is now close to fully functional in US and DE.
We have identified the root cause as caused by one of our cloud providers, and are closely monitoring the situation.
Jun 11, 11:51 UTC
Update - We are continuing to investigate the degraded notifications.
Jun 11, 10:53 UTC
Update - We are continuing to investigate the degraded notifications.
Jun 11, 09:50 UTC
Investigating - We're currently investigating degraded notification delivery.
Jun 10, 10:28 UTC
Resolved - Our auth systems are back operational
Jun 10, 10:17 UTC
Update - We rolled back a configuration change we identified as the root cause of the issue. We'll keep monitoring our systems
Jun 10, 10:15 UTC
Monitoring - We deployed a fix and are monitoring the situation.
Jun 10, 10:05 UTC
Investigating - We are currently investigating the issue.
Jun 2, 07:45 UTC
Resolved - Between 06:00-07:00 UTC, we saw increased numbers of API errors in the EU region. The largest impact was between 06:46-07:00. We've implemented a fix and we're no longer seeing elevated errors.
May 28, 14:28 UTC
Resolved - The issue has been resolved
May 28, 14:20 UTC
Monitoring - The fix has been deployed and we are monitoring the situation
May 28, 13:55 UTC
Identified - We have identified the cause of the issue and are deploying a fix
May 28, 13:40 UTC
Investigating - We are currently investigating the issue
Jun 16, 13:18 EDT
Resolved - This incident has been resolved.
Jun 16, 09:46 EDT
Update - We are continuing to monitor for any further issues.
Jun 16, 09:46 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 16, 09:23 EDT
Identified - The issue has been identified and a fix is being implemented.
Jun 16, 08:39 EDT
Investigating - We are currently investigating this issue.
Jun 11, 15:33 EDT
Resolved - This incident has been resolved.
Jun 11, 14:49 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 11, 14:34 EDT
Investigating - We are currently investigating this issue.
Jun 4, 16:07 EDT
Resolved - This incident has been resolved.
Jun 4, 16:00 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 4, 15:18 EDT
Identified - The issue has been identified and a fix is being implemented.
Jun 4, 14:52 EDT
Investigating - We are currently investigating errors on submitting translations feedback form
May 27, 19:41 EDT
Resolved - This incident has been resolved.
May 27, 19:28 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
May 27, 18:51 EDT
Investigating - We are currently investigating reports of issues with content asignments
May 8, 00:09 EDT
Resolved - This incident has been resolved.
May 7, 21:13 EDT
Monitoring - There is an ongoing AWS outage impacting some of the services.
Our platform and APIs remain fully operational and stable.
We're keeping a close eye on the situation as AWS work through recovery.
May 7, 20:18 EDT
Investigating - We're experiencing an elevated level of API errors and are currently looking into the issue.
Incident has been resolved.
Affected components
- Jira (Operational)
- Tempo for Slack (Operational)
- Tempo for Jira Cloud Help Center (Operational)
- Time Tracker (Operational)
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
We had some delay in event processing during last night, the issue has been resolved.
Our customers are reporting that they're able to access Tempo now.
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
Jun 4, 14:09 UTC
Resolved - This incident has been resolved.
Jun 4, 12:56 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 4, 10:10 UTC
Investigating - We are currently experiencing a service disruption affecting Upstash Vector in the IAD region.
Initial investigation indicates that the issue is related to a Fly.io networking/routing problem impacting connectivity in the region. The Fly.io team is actively investigating the underlying cause.
We will continue to monitor the situation and provide updates as more information becomes available.
May 30, 07:51 UTC
Resolved - The issue affecting some Upstash Vector indexes in the US-EAST-1 region has been resolved.
Our team investigated the incident and identified the conditions that were contributing to elevated memory pressure on the affected servers. We mitigated those conditions by reducing memory utilization on the impacted nodes, rebalancing affected workloads where needed, and increasing available headroom capacity across the region.
All affected indexes should now be operating normally, and based on the mitigations applied, we do not expect this issue to recur. We apologize for any inconvenience this may have caused.
May 29, 23:44 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 29, 20:18 UTC
Investigating - Some Upstash Vector indexes in the US-EAST-1 region may be experiencing intermittent slowness. Initial investigation indicates this may be related to memory pressure on the affected servers.
Our team is actively investigating the root cause and working to restore normal performance. We will provide updates as soon as more information is available.
May 23, 00:00 UTC
Resolved - This incident has been resolved.
May 22, 23:48 UTC
Monitoring - Upstream issue resolved — new database creation is working again. We're monitoring to confirm full recovery.
May 22, 23:27 UTC
Investigating - New database provisioning is currently failing due to an ongoing upstream provider issue affecting DNS. Existing databases and connections are unaffected — only the creation flow is impacted. We're monitoring the situation and will update once the upstream issue is resolved.
May 14, 17:31 UTC
Resolved - Earlier today, unexpected load on our proxies caused intermittent connection issues for Upstash Redis in the following regions:
us-east-1, us-west-1, ap-southeast-2, and ap-south-1.
During this period, some clients may have seen connection timeouts or elevated error rates when reaching their databases.
Our team identified the issue quickly and applied workarounds to relieve pressure on the affected proxies. Connection health has since been restored and we've been monitoring the regions to confirm everything is stable. All systems are now operating normally.
We appreciate your patience and apologize for any disruption this may have caused.
May 14, 16:00 UTC
Monitoring - A fix has been implemented and we are monitoring.
May 14, 15:49 UTC
Identified - The issue has been identified and a fix is being implemented.
May 14, 15:47 UTC
Monitoring - We identified intermittent connection issues affecting some regions. Fix is being deployed. We'll update the list of affected regions shortly.
May 12, 13:48 UTC
Resolved - This incident has been resolved.
May 12, 12:05 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
May 12, 10:50 UTC
Identified - The issue has been identified and the fix is being implemented.
May 12, 09:49 UTC
Investigating - Some regions are experiencing connectivity issues due to an ongoing network problem. We are currently investigating
Jun 16, 15:39 UTC
Resolved - The incident has been resolved.
Jun 16, 15:26 UTC
Monitoring - The team has deployed a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are continuing to monitor.
Jun 16, 15:16 UTC
Identified - The team has identified the source of the issue and is preparing a fix for timeouts and failed requests related to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard.
Jun 16, 14:45 UTC
Update - We are continuing to investigate partial disruption to Observability, Web Analytics, Speed Analytics, Firewall, and Usage in dashboard. We are also investigating delayed usage alerts.
Jun 16, 13:39 UTC
Investigating - We are investigating a partial disruption to Observability, Web Analytics, Speed Analytics and Firewall features.
Jun 15, 01:24 UTC
Resolved - This incident has been resolved.
Jun 15, 00:25 UTC
Monitoring - All traffic has been restored to the FRA1 Vercel Region.
Jun 14, 23:15 UTC
Update - The issue has been fixed. We are starting to re-route traffic from the CDG1 Vercel Region back to the FRA1 Vercel Region. We will provide another status update after this has finished.
Jun 14, 21:26 UTC
Update - The impact is currently mitigated. We are continuing to re-route traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
Jun 14, 21:07 UTC
Identified - We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region.
Jun 14, 21:03 UTC
Investigating - We are currently re-routing traffic from the FRA1 Vercel Region to the CDG1 Vercel Region. We are currently investigating this issue.
Jun 9, 14:46 UTC
Resolved - This incident has been resolved.
Jun 9, 14:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 9, 14:33 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 9, 14:09 UTC
Investigating - We are currently investigating this issue.
Jun 8, 20:00 UTC
Resolved - This incident has been resolved.
Jun 8, 19:36 UTC
Update - We are continuing to monitor for any further issues.
Jun 8, 19:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 8, 19:04 UTC
Update - We're continuing to work on a fix. In the meantime, deployments with multiple function regions or failover regions are being rerouted to the nearest healthy region.
If your project uses only the dub1 function region, you can switch to the nearest region, lhr1, and redeploy to mitigate the issue.
Jun 8, 18:57 UTC
Identified - The issue has been identified and a fix is being implemented.
A small number of requests may have seen elevated error rates in function invocations during this period.
Jun 1, 20:02 UTC
Resolved - This incident has been resolved.
Jun 1, 19:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jun 1, 19:50 UTC
Identified - The issue has been identified and a fix is being implemented.
Jun 1, 19:21 UTC
Investigating - We are investigating reports of some customers experiencing elevated errors creating new deployments. We will provide additional updates as they become available.
Jun 15, 18:04 PDT
Resolved - This incident has been resolved.
Jun 15, 17:54 PDT
Monitoring - The issue where some Zoom Rooms Scheduling Displays may incorrectly appear as offline in the Zoom Dashboard, despite the devices remaining online and operational has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Jun 15, 17:03 PDT
Update - Our team continues to work on the resolution where some Zoom Rooms Scheduling Displays may incorrectly appear as offline in the Zoom Dashboard, despite the devices remaining online and operational.
We will keep you informed with timely updates as progress is made.
Thank you for your patience.
Jun 15, 15:41 PDT
Identified - We have identified the root cause where some Zoom Rooms Scheduling Displays may incorrectly appear as offline in the Zoom Dashboard, despite the devices remaining online and operational.
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.
Jun 15, 12:11 PDT
Update - Our team is actively working to identify the impact and root cause. We will provide further updates as more information becomes available.
We appreciate your patience as we work to resolve this issue.
Jun 15, 11:10 PDT
Update - Our team is actively working to identify the impact and root cause and will provide further updates as more information becomes available.
We appreciate your patience as we work to resolve this issue.
Jun 15, 10:05 PDT
Investigating - We are investigating an issue where some Zoom Rooms Scheduling Displays may incorrectly appear as offline in the Zoom Dashboard, despite the devices remaining online and operational.
This issue is limited to the status displayed in the Dashboard and does not impact the functionality of the affected scheduling displays.
As a workaround, users may perform a physical reboot of the affected scheduling display device to restore the correct status in the Dashboard.
Our team is actively working to identify the impact and root cause and will provide further updates as more information becomes available.
We appreciate your patience as we work to resolve this issue.
Jun 15, 11:16 PDT
Monitoring - The service degradation with Zoom Meeting Recordings has been successfully mitigated.
Users may see two recording files instead of one for meetings that were in progress during the impact window.
Our team is continuing to monitor and evaluate the full scope of impact.
If you have questions about your recordings, please open a support ticket, and our team will investigate.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
We appreciate your patience as we worked to resolve this issue.
Jun 15, 10:25 PDT
Update - We continue to work on a fix for this issue and will provide updates as soon as there is more information to share.
We appreciate your patience as we work to resolve this issue.
Jun 15, 09:34 PDT
Identified - We have successfully identified the root cause affecting Zoom Meeting Records. Users may observe two recording files instead of one.
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.
Jun 15, 09:07 PDT
Investigating - We are currently investigating a service degradation affecting Zoom Meeting Recordings.
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.
Jun 15, 06:07 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Jun 15, 05:47 PDT
Monitoring - The service degradation affecting Zoom Web AIC Docs creation has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Jun 15, 05:14 PDT
Identified - We have successfully identified the root cause affecting Zoom Web AIC Docs creation.
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.
Jun 15, 04:51 PDT
Update - We are continuing to investigate this issue and will provide updates as soon as there is more information to share.
We appreciate your patience as we work to resolve this issue.
Jun 15, 04:03 PDT
Investigating - We are currently investigating a service degradation affecting Zoom Web AIC Docs creation.
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.
Jun 14, 23:35 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Jun 14, 23:24 PDT
Monitoring - The issue affecting My Notes has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Jun 14, 21:49 PDT
Identified - We have successfully identified the root cause affecting My Notes.
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.
Jun 14, 21:31 PDT
Investigating - We are currently investigating a service degradation affecting My Notes.
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.
Jun 14, 23:19 PDT
Resolved - This incident has been resolved and the affected services have been restored.
Jun 14, 23:10 PDT
Update - This incident has been resolved and the affected services have been restored.
Jun 14, 23:02 PDT
Monitoring - On 06/15/2026, between 04:31 UTC to 05:01 UTC, a subset of users might have experienced service degradation with Zoom Contact Center’s Agent Experience.
This incident has been resolved and the affected services have been restored.