Dec 15, 19:29 UTC
Resolved - This incident has been resolved.
Dec 15, 19:24 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 15, 19:16 UTC
Identified - The issue has been identified and a fix is being implemented.
Dec 15, 18:39 UTC
Investigating - We are currently investigating this issue.
Dec 14, 22:51 UTC
Resolved - As of 14:43 PT / 22:43 UTC we have seen full recovery across all models.
Dec 14, 22:46 UTC
Identified - The issue has been identified and a fix is being implemented.
Dec 14, 22:36 UTC
Update - We are continuing to investigate the issue.
Dec 14, 21:46 UTC
Update - We have identified that the outage is related to Sonnet 4.0, Sonnet 4.5, and Opus 4.5.
Dec 14, 21:31 UTC
Investigating - We are currently investigating this issue.
Dec 12, 18:59 UTC
Resolved - This incident has been resolved.
Dec 12, 17:10 UTC
Investigating - We are currently investigating this issue.
Dec 12, 08:00 UTC
Resolved - This incident has been resolved.
Dec 12, 00:04 UTC
Resolved - The issue has been resolved. We are working on compensation for impacted users.
Dec 9, 23:37 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 8, 01:00 UTC
Identified - Due to a bug introduced in Claude iOS app version 1.251117.1 (November 18), some Apple App Store users who purchased Pro and Max plans on or after November 24 did not receive proper access to their plans.
The mobile purchasing bug has been resolved. New purchases going forward will activate plans correctly.
Engineering is still working on a fix to restore plans for already-impacted customers, expected to go live tomorrow.
Dec 12, 19:07 UTC
Resolved - The Usage API issue has been resolved. Data is loaded for yesterday 12/11. Thank you for your patience.
Dec 12, 17:49 UTC
Identified - The issue has been identified. Expected time to resolution: 90 minutes
Dec 12, 17:22 UTC
Investigating - We are currently investigating an issue affecting Usage API data availability for December 11, 2025. Customers querying usage data for this date will not receive results at this time. Usage data prior to December 11 remains accessible and unaffected.
This issue is isolated to data retrieval for the specified date. All other CircleCI functionality, including job execution and workflow triggering, continues to operate normally.
We are actively investigating the cause and will provide our next update within 30 minutes or as we know more.
Dec 5, 00:15 UTC
Resolved - The incident has been resolved. Thank you for your patience. The "infra-fail" should no longer be occurring.
Dec 5, 00:06 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 4, 23:36 UTC
Identified - We are slowly returning to normal. If you had jobs that failed with "infra-fail", those jobs can be rerun. We thank you for your patience while our engineers worked to get our system back to stability.
Dec 4, 22:53 UTC
Investigating - We're currently investigating a high number of infra failures. We'll update as soon as we know more details.
Dec 4, 17:49 UTC
Resolved - This incident has been resolved.
Dec 4, 17:43 UTC
Monitoring - All jobs should now be running normally. The backlog of jobs has cleared and jobs should be running in typical time. We will continue monitoring to ensure consistent service. Thank you for your patience.
Dec 4, 17:19 UTC
Update - We are continuing to see recovery, but some customers may still experience delays in jobs running on M4 executors. We appreciate your patience whilst we work through the backlog of jobs.
Dec 4, 16:29 UTC
Update - We have mitigated the issue and MacOS jobs which do not have a resource class specified should run normally. Customers can rerun jobs which failed an they should now run normally without any modification to their config. Thank you for your patience whillst we resolved this.
Customers using M4 machine jobs may experience minor delays in jobs starting during this period as there are a large number of re-runs occurring.
Dec 4, 16:04 UTC
Identified - We have identified an issue in our system which mean that MacOS jobs which don't specify a resource class will fail to run with an "Invalid resource class" error. We are working to correct this, but customers can workaround this by specifying a resource class in their config.yml.
Dec 3, 23:48 UTC
Resolved - We have resolved the issues affecting job triggering, workflow starts, and API queries. Our systems have been stabilized and are operating normally.
What was impacted: Job triggering, workflow starts, API queries, and pipeline page loading experienced disruptions for some customers. This affected all resource classes and executors.
Resolution: We implemented mitigation measures to address high volume workflow queries impacting our internal systems and increased system capacity. All new jobs and workflows are now starting normally, pipeline pages are loading, and API queries are functioning as expected.
What to expect: If you have jobs that became stuck during this incident, please rerun them. If you continue to experience issues after rerunning, please contact our support team. Some customers may still see jobs stuck in a cancelling state. Engineering is aware and addressing to mitigate risk.
We will continue monitoring our systems and conducting a thorough review to identify additional preventive measures.
Dec 3, 22:59 UTC
Update - We have deployed changes to mitigate the high volume of workflow queries impacting our systems. Pipeline pages that were previously failing to load are now loading successfully, and we are seeing significant reduction in API errors.
What's impacted: Some customers continue to experience jobs stuck in a not-running state from earlier in the incident. New job triggering and workflow starts are now functioning normally.
What's happening: We have implemented mitigation measures and increased system capacity. We are continuing to investigate the remaining stuck jobs for affected customers.
What to expect: If you experienced issues loading pipeline pages or querying workflow data via the API, these should now be resolved. New jobs and workflows should trigger normally. If you have jobs that appeared stuck earlier, please try rerunning them while we continue to investigate the reports of jobs that do remain stuck for a small number of customers. The data for those workflows should be available and queryable.
Next update: We will provide an update within 30 minutes. Thank you for your patience while our engineers work through this incident.
Dec 3, 21:58 UTC
Update - We are currently experiencing issues affecting job triggering and workflow starts across all resource classes. Jobs may appear stuck in a not-running state, and some customers may encounter 500 errors when making API calls to check job or workflow status.
What's impacted: Job triggering, workflow starts, and API queries for job and workflow status are experiencing disruptions. This affects all resource classes and executors. Some users may also experience issues loading the pipeline page.
What to expect: We are actively working to stabilize our systems and restore normal operations. We will provide updates as we make progress toward resolution.
We thank you for your patience while we work through these issues - we will update with our progress within 30 minutes or earlier.
Dec 3, 21:28 UTC
Investigating - We are currently investigating reports of jobs not starting. We apologize for the inconvenience.
Dec 3, 21:58 UTC
Resolved - The issues affecting the pipelines page display are related to a broader incident impacting our systems. We have opened a separate incident tracking job triggering and API status issues, which encompasses the pipelines page loading problems. Please follow https://status.circleci.com/incidents/jq4bgq2sjt1r for ongoing updates.
Dec 3, 21:31 UTC
Update - We are continuing to investigate this issue.
Dec 3, 21:31 UTC
Investigating - We are seeing some issues loading the pipelines page. This doesn't affect all users but affects the display of pipelines. We are continuing to investigate the cause of this issue.
Dec 15, 04:00 UTC
Resolved - Between 4:10 and 4:47 UTC today, 2025-12-15, customers may have observed network connectivity degradation for traffic through our Mumbai (BOM) facility.
Dec 11, 21:55 UTC
Resolved - This incident is now resolved.
Dec 11, 21:45 UTC
Monitoring - We have implemented a fix for this issue and are currently monitoring the results.
Dec 11, 21:01 UTC
Investigating - Cloudflare single-file cache purging (purge by URL) called via the Dashboard/API is running up to 30 minutes behind in Eastern North America (ENAM). This also affects the "Always Online" feature.
We are working to resolve this issue as soon as possible. Until then you may use the Purge Everything feature but do be aware it may cause a surge in traffic to your origin server(s). More updates to follow.
Dec 11, 10:49 UTC
Resolved - This incident has been resolved.
Dec 11, 10:12 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 11, 09:15 UTC
Identified - The issue has been identified and a fix is being implemented.
Dec 11, 09:08 UTC
Investigating - Cloudflare is investigating issues with network performance in Brazil. We are working to analyse and mitigate this problem. More updates to follow shortly.
Dec 11, 10:14 UTC
Resolved - This incident has been resolved.
Dec 11, 09:44 UTC
Identified - The issue has been identified and a fix is being implemented.
Dec 11, 08:56 UTC
Investigating - Cloudflare is investigating an issue with our abuse form. Customers cannot send Non-Consensual Sexually Explicit Imagery (NCSEI) abuse submissions.
We are currently working on a resolution. More updates to follow shortly.
Dec 5, 17:18 UTC
Resolved - This incident has been resolved.
Dec 5, 09:16 UTC
Monitoring - we have been informed that a fix has been deployed for the issue that was causing intermittent 5xx errors and connectivity disruptions on websites proxied through Cloudflare.
Our team is closely monitoring the situation along with Cloudflare to ensure full service stability.
If you continue to experience any issues, please reach out to our support team.
We will provide further updates as needed.
Dec 5, 09:05 UTC
Investigating - We are aware of an ongoing Cloudflare network issue that may cause intermittent 5xx errors, connection timeouts, or degraded performance for applications using the Cloudways Cloudflare Add-on or any site proxied through Cloudflare directly.
This aligns with the active incident reported on Cloudflare’s status page:
https://www.cloudflarestatus.com/
Our engineering team is actively monitoring the situation and is in direct communication with Cloudflare to ensure the issue is resolved at the earliest.
Customers who are not using Cloudflare are not affected.
Further updates will be posted here as soon as new information becomes available.
Dec 5, 02:40 UTC
Resolved - This incident has been resolved.
Nov 24, 13:44 UTC
Update - We are continuing to investigate this issue.
Nov 24, 13:44 UTC
Investigating - We are currently facing a technical issue that is preventing new Rackspace Addon users from creating mailboxes in Rackspace's email service.
Our team is working on resolving this matter. We apologize for any inconvenience this may cause and appreciate your patience.
Dec 2, 12:26 UTC
Resolved - This incident has been resolved.
Dec 1, 14:10 UTC
Investigating - We are facing degraded performance with Elastic Email, affecting a subset of customers whose emails are not being sent promptly and experiencing delays. Our teams are actively investigating the problem with the elastic email team and we will be updating this status page with further information as soon as it is available. We apologize for any inconvenience this may be causing.
Nov 28, 02:42 UTC
Resolved - This incident has been resolved.
Nov 23, 20:42 UTC
Investigating - Vultr has reported an incident affecting global server provisioning operations. They are continuing to investigate, and we are monitoring the situation closely. We will provide updates as soon as more information becomes available. We regret any inconvenience caused.
Nov 27, 18:23 UTC
Resolved - This incident has been resolved.
Nov 27, 16:39 UTC
Monitoring - The network services are being restored, and our team is actively monitoring the current status.
Nov 27, 14:47 UTC
Investigating - Our upstream provider Vultr is currently experiencing a partial outage in the London region. Their network engineers are actively working to restore connectivity as quickly as possible. We sincerely regret the inconvenience this may cause and appreciate your patience while the issue is being resolved.
Dec 15, 10:55 UTC
Resolved - Between 08:40 and 09:20 UTC customers experienced errors when trying to log in to Contentful ("Something went wrong"). This was due to a change we made to our bot protection logic. Once we saw the impact of the change, we reverted and the issue was resolved. If any customers continue to see the error after that time period, a refresh will resolve the issue.
Dec 10, 14:01 UTC
Resolved - The issue is resolved now
Dec 10, 13:12 UTC
Identified - We've noticed an issue with the captcha service returning "Invalid Captcha" errors for user registrations and email confirmations and are now working on resolving it
Dec 4, 11:40 UTC
Resolved - This issue is now resolved.
Dec 4, 11:23 UTC
Monitoring - This issue has been mitigated and we are monitoring the result.
Dec 4, 10:54 UTC
Identified - We have identified the cause of the issue and are working on a fix.
Dec 4, 10:33 UTC
Investigating - We are investigating spikes of increased latency on our Content Management API (CMA).
Dec 3, 09:03 UTC
Resolved - Audit Logs have returned to their normal state and are fully operational again.
Dec 2, 17:04 UTC
Monitoring - We've fixed the missing fields for Audit Logs and are now monitoring to ensure normal functionality is restored.
Dec 2, 15:45 UTC
Update - The root cause has been identified, and a fix is in progress. At this stage, it appears that usage reporting is unaffected.
Dec 2, 15:12 UTC
Investigating - We've identified an issue affecting CMA API call usage reporting and Audit Logs since Nov 14, where certain fields are missing and data may be incomplete. As a result, some Audit Log events may be absent, and the CMA usage reports displayed in the web app may not accurately reflect actual usage. We are currently investigating and will provide updates as soon as we understand the full impact.
Dec 2, 14:16 UTC
Resolved - The issue is resolved.
Dec 2, 13:35 UTC
Monitoring - We've resolved the issue and are monitoring the situation.
Dec 2, 13:23 UTC
Update - We've identified the issue. It is only affecting cross-space references for customers who are using fallback locales. We are working on a resolution.
Dec 2, 13:06 UTC
Investigating - Some customers are experiencing errors for cross-space references. We are investigating the situation.
Dec 3, 14:40 EST
Resolved - This incident has been resolved.
Dec 3, 14:24 EST
Monitoring - A fix has been implemented, and we are monitoring the results.
Dec 3, 13:31 EST
Investigating - We’re currently investigating reports of the Forms List not loading. Our apologies for the inconvenience. Our team is working to resolve this as quickly as possible. We’ll continue to share updates here as soon as more information becomes available.
Oct 21, 17:29 EDT
Resolved - This incident has been resolved. Users should now be able to access their accounts successfully.
Oct 21, 17:01 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 21, 16:48 EDT
Investigating - We are investigating reports of 404 (Page Not Found) error, which is preventing some users from logging in. Our team is working to identify the cause and will update this page as soon as we have more information.
Oct 20, 01:00 EDT
Resolved - You may be aware of a widespread AWS outage this morning. This event impacted FormAssembly, and we want to provide details on what happened and our current status.
What Happened: Amazon Web Services (AWS) experienced a significant DNS resolution failure in their US-EAST-1 region starting around 12:11 AM ET. This had a cascading impact on many AWS services globally, as many rely on this core region.
How This Affected FormAssembly :Our primary infrastructure runs in AWS US-EAST-1. As a result, we experienced degraded performance and service disruptions. The impact was felt across many services we use.
Current Status: AWS mitigated the primary DNS issue by 3:35 AM ET, and most core services have recovered after working through significant backlogs.
While the major disruption is over, we are still observing some sporadic performance issues. You may still experience some lingering, intermittent slowness as these services fully stabilize.
Next Steps: Our team is continuing to actively monitor the situation until all services report stable, normal performance.
Oct 6, 12:19 EDT
Resolved - A fix has been implemented. The Admin Dashboard, Builder, and connectors are now accessible.
The incident has been resolved.
Oct 6, 10:30 EDT
Identified - Our team has identified the issue affecting the Admin dashboard, Builder and Locked connectors. They are currently working on a fix for the issue. We will continue to update here as more information becomes available and a fix is issued.
Oct 6, 08:56 EDT
Investigating - We are currently investigating reports that are impacting FormAssembly, such as access to the Admin Dashboard and Form Builder for account admins. Our engineering team is actively investigating and working to resolve this as quickly as possible. We will continue to post here as more information is available.
Sep 18, 13:06 EDT
Resolved - As of 12:51 PM ET, a fix has been implemented for the issue affecting the ability to move fields within the form builder.
Thank you for your patience while we worked to resolve the issue.
Sep 17, 17:13 EDT
Identified - We are continuing to work toward a fix for this issue. We will continue to share updates here as more details become available.
Sep 17, 14:09 EDT
Investigating - We are currently investigating an issue where users are unable to drag and drop fields within the form builder. Our team is actively working to identify the root cause and implement a solution.
In the meantime, you can use the form outline as a workaround to reorder your form fields.
https://help.formassembly.com/help/introducing-the-form-builder#form-outline
We will post an update on this page as soon as more information is available.
Dec 15, 18:22 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.
Dec 15, 18:21 UTC
Update - We have seen recovery for Copilot Code Review requests and are investigating long-term availability and scaling strategies
Dec 15, 17:43 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Dec 15, 15:45 UTC
Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
Dec 15, 15:06 UTC
Update - We are continuing to work with our provider on resolving the incident with Grok Code Fast 1. Users can expect some requests to intermittently fail until all issues are resolved.
Dec 15, 14:13 UTC
Update - We are experiencing degraded availability for the Grok Code Fast 1 model in Copilot Chat, VS Code and other Copilot products. This is due to an issue with an upstream model provider. We are working with them to resolve the issue.
Other models are available and working as expected.
Dec 15, 14:12 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Dec 11, 20:05 UTC
Resolved - Between 13:25 UTC and 18:35 UTC on Dec 11th, GitHub experienced an increase in scraper activity on public parts of our website. This scraper activity caused a low priority web request pool to increase and eventually exceed total capacity resulting in users experiencing 500 errors. In particular, this affected Login, Logout, and Signup routes, along with less than 1% requests from within Actions jobs. At the peak of the incident, 7.6% of login requests were impacted, which was the most significant impact of this scraping attack.
Our mitigation strategy identified the scraping activity and blocked it. We also increased the pool of web requests that were impacted to have more capacity, and lastly we upgraded key user login routes to higher priority queues.
In future, we’re working to more proactively identify this particular scraper activity and have faster mitigation times.
Dec 11, 20:05 UTC
Update - We see signs of full recovery and will post a more in-depth update soon.
Dec 11, 19:58 UTC
Update - We are continuing to monitor and continuing to see signs of recovery. We will update when we are confident that we are in full recovery.
Dec 11, 19:04 UTC
Update - We've applied a mitigation to fix intermittent failures in anonymous requests and downloads from GitHub, including Login, Signup, Logout, and some requests from within Actions jobs. We are seeing improvements in telemetry, but we will continue to monitor for full recovery.
Dec 11, 18:47 UTC
Update - We currently have ~7% of users experiencing errors when attempting to sign up, log in, or log out. We are deploying a change to mitigate these failures.
Dec 11, 18:40 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Dec 11, 17:53 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.
Dec 11, 17:20 UTC
Update - Git Operations is operating normally.
Dec 11, 17:19 UTC
Update - We believe that we have narrowed down our affected users to primarily those that are signing up or signing in as well as logged out usage. We are currently continuing to investigate the root cause and are working multiple mitigation angles.
Dec 11, 16:41 UTC
Update - We are experiencing intermittent web request failures across multiple services, including login and authentication. Our teams are actively investigating the cause and working on mitigation.
Dec 11, 16:09 UTC
Update - Codespaces, Copilot, Git Operations, Packages, Pages, Pull Requests and Webhooks are experiencing degraded performance. We are continuing to investigate.
Dec 11, 16:01 UTC
Update - API Requests and Actions are experiencing degraded performance. We are continuing to investigate.
Dec 11, 15:47 UTC
Investigating - We are investigating reports of degraded performance for Issues
Dec 10, 14:52 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.
Dec 10, 14:32 UTC
Update - We've applied a mitigation to ensure all macOS jobs route to macOS fulfillers and are monitoring for full recovery.
Dec 10, 13:34 UTC
Investigating - We are investigating reports of degraded performance for Actions
Dec 5, 04:33 EST
Resolved - Between 04:55 PM (UTC +08:00) and 05:20 PM (UTC +08:00), all customers in all regions experienced issues with all impaired tools. This was caused by a Cloudflare outage. As of 05:20 PM (UTC +08: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.
Dec 5, 04:20 EST
Monitoring - Cloudflare has addressed the issue that prevented HubSpot from loading beginning at 3:55 AM EST (UTC -05:00) on Dec 5, 2025. We're monitoring performance closely to ensure the software recovers properly. We will be back with an update within 15 minutes.
Dec 5, 04:09 EST
Investigating - HubSpot is currently unavailable for all users due to a Cloudflare outage - https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q
We are working with Cloudflare to resolve the issue, and we'll update this page when we have more information. We will be back with an update within 30 minutes.
Dec 1, 11:02 EST
Resolved - Marketing contact updates are no longer delayed. We've identified and addressed the cause of the delays that began at 04:05 AM (UTC +01:00) on Dec 1, 2025. The issue is now fully resolved.
Dec 1, 07:37 EST
Update - We've identified an issue that caused setting contacts to non-marketing on the next update date to be delayed in some regions since 04:05 AM (UTC +01:00).
We're still monitoring performance closely to ensure the tools recover properly as we work through all affected regions.
Dec 1, 04:34 EST
Monitoring - We've identified an issue that caused setting contacts to non-marketing on the next update date to be delayed in some regions since 04:05 AM (UTC +01:00). We're monitoring performance closely to ensure the tools recover properly.
Nov 13, 15:56 EST
Resolved - Between 01:53 PM (UTC -06:00) and 02:45 PM (UTC -06:00), some customers in all affected regions experienced issues with CRM tools. This was caused by a server impairment. As of 02:45 PM (UTC -06:00), our CRM 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.
Nov 13, 15:34 EST
Update - We are investigating an issue impacting the HubSpot CRM. 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.
Nov 13, 15:14 EST
Investigating - We're investigating reports that HubSpot may be unavailable for some users. We'll update this page when we have more information.
Nov 11, 13:15 EST
Resolved - Between 04:53 PM (UTC +00:00) and 05:55 PM (UTC +00:00), some customers in Canada experienced issues with HubSpot tools. This was caused by a production configuration change. As of 05:55 PM (UTC +00:00), our HubSpot 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.
Nov 11, 13:00 EST
Monitoring - We've addressed the issue that caused HubSpot tools to be partially unavailable for users hosted in Canada since 04:53 PM (UTC +00:00). We're monitoring performance closely to ensure the tools recover properly.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Nov 11, 12:34 EST
Update - We estimate that we will restore service in the next 30 minutes.
We are mitigating impact from a service impairment which we believe is caused by a production configuration change. We are scaling the system.
The information on this page reflects our understanding of the incident and impact of the time of the update. Only customers hosted in Canada are currently impacted. We will be back with an update within 30 minutes.
Nov 11, 12:12 EST
Identified - We've identified the issue that caused commerce tools, content tools, customer platform tools, hubspot APIs, marketing tools, operations tools, sales tools, service tools to be unavailable for some users hosted in Canada since 04:53 PM (UTC +00:00). We're addressing the cause of this issue 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.
Nov 7, 05:15 EST
Resolved - Between 10:30 AM EST (UTC -05:00) on Nov 5, 2025, and 8:32 AM EST (UTC -05:00) on Nov 6, 2025, some customers experienced issues with global search. This was caused by a database impairment. As of 9:32 AM EST (UTC -05:00) on Nov 6, 2025, our global search 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.
Nov 6, 11:19 EST
Monitoring - We have mitigated the issue that caused global search to return partial search results since 10:30 AM EST (UTC -05:00) on Nov 5, 2025.
Global contact search is now operational again. Further object indices are continuing to recover. We are closely monitoring performance and search result completeness.
If you still experience missing results while search indices are recovering, please use the dedicated search on each CRM object page as a temporary workaround.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Nov 6, 10:53 EST
Update - We are working to fully restore the search service and expect recovery to complete within the next several hours.
We are mitigating the impact of a database issue that we believe was caused by a recent production code change. We have reverted this change and are restoring the correct database state.
Global contact search has been restored. We are monitoring the roll-out as we bring back all remaining object indices.
In the meantime, please use the dedicated search on each CRM object page to find the records you need.
We will be back with an update within 3 hours.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Nov 6, 09:56 EST
Update - We are working to fully restore the search service and expect recovery to complete within the next several hours.
We are mitigating the impact of a database issue that we believe was caused by a recent production code change. We have reverted this change and are restoring the correct database state.
Global contact search has been restored. We are monitoring the roll-out as we bring back all remaining object indices.
In the meantime, please use the dedicated search on each CRM object page to find the records you need.
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.
Nov 6, 09:01 EST
Update - We estimate that we will restore the full search service in the next several hours.
We are mitigating the impact from a database impairment, which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state.
The global contact search has been restored. We are monitoring the roll-out to restore all object indices.
As a workaround, use the dedicated search functionality of the CRM object page.
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.
Nov 6, 08:32 EST
Update - We estimate that we will restore service in the next several hours.
We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state.
The global contact search has been restored. We are monitoring the roll-out to restore all object indices.
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.
Nov 6, 08:03 EST
Update - We estimate that we will restore service in the next several hours.
We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state.
The global contact search should be partially restored in Europe.
As a workaround, use the dedicated search functionality of the CRM object page.
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.
Nov 6, 07:32 EST
Update - We estimate that we will restore service in the next several hours.
We are mitigating the impact of a database impairment, which we believe is caused by a bad production code change. We are reverting the change.
As a workaround, use the dedicated search functionality of the CRM object page.
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.
Nov 6, 07:03 EST
Update - We estimate that we will restore service in the next hour.
We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change and restoring the correct database state.
As a workaround, use the dedicated search functionality of the CRM object page.
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.
Nov 6, 06:49 EST
Identified - We estimate that we will restore service in the next hour.
We are mitigating impact from a database impairment which we believe is caused by a bad production code change. We are reverting the change.
We will be back with an update within 15 minutes.
As a workaround, use the dedicated search functionality of the CRM object page.
The information on this page reflects our understanding of the incident and impact at the time of the update.
Dec 15, 19:02 UTC
Resolved - On December 15th, 2025, Admin Hub, Atlassian Analytics, Confluence Cloud, Ecosystem, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo users in the prod-us-east region may have experienced performance degradations and errors on the web page and mobile apps. The issue has now been resolved, and the service is operating normally for all affected customers.
Dec 15, 17:47 UTC
Update - Our teams are continuing to implement mitigations. Error rates have decreased across all products and we are seeing improvements.
We will continue to provide updates here in 60 minutes or as more information becomes available.
Dec 15, 16:48 UTC
Update - We have identified the cause of the issue, and our teams are diligently working on mitigations. We're currently seeing signs of improvements. We'll continue to share additional updates here in 60 minutes or as more information becomes available.
Dec 15, 16:26 UTC
Update - We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, Jira Work Management, and Rovo. We'll share updates here as more information is available.
Dec 15, 16:16 UTC
Identified - We are actively investigating reports of performance degradation affecting Admin Hub, Atlassian Analytics, Confluence Cloud, Focus, Jira, Jira Product Discovery, Jira Service Management, and Rovo. We'll share updates here as more information is available.
Dec 5, 15:32 UTC
Resolved - On December 5th, 2025, Jira Service Management users may have experienced an error when creating linked work items that included an attachment. The issue has now been resolved, and the service is operating normally for all affected customers.
Dec 5, 13:16 UTC
Monitoring - We are currently investigating an issue where users encounter a Something Went Wrong error when creating a Linked Work Item that includes an attachment.
Our engineering team is in the process of deploying the fix to production, and the ETA is 9hours from now.
We apologize for the inconvenience and will provide updates as soon as more information becomes available. Thank you for your patience.
Next Steps:
The team will continue to monitor the situation until the hotfix is fully rolled out. Follow-up communications will be sent once the hot fix is fully rolled out.
Dec 1, 18:26 UTC
Resolved - Impact
Jira Software users experienced degraded performance affecting their ability to view issues and boards. Users may have encountered an error or slowdown during this time.
Current Status
The situation is currently mitigated due to actions taken on the affected systems, leading to a stabilization of services.
Next Steps
The team is actively monitoring the systems.
Dec 1, 18:26 UTC
Update - We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.
Dec 1, 17:30 UTC
Update - We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.
Dec 1, 17:26 UTC
Update - We are still investigating an issue with functionality that is mainly affected by Sandboxes and impacting some Jira Work Management, Jira Service Management, and Jira Cloud customers. We will provide more details within 2 hours.
Dec 1, 17:25 UTC
Investigating - We are investigating an incident affecting Jira Work Management, Jira, and Jira Service Management. We will provide updates via Statuspage shortly.
The ability to view issues and boards is experiencing degraded performance for some users. Customers may notice a slowdown in accessing these functionalities.
Nov 21, 16:49 UTC
Resolved - The Trello performance degradation has been resolved. Also, some intermittent errors on some of our other products, has also now been resolved.
The issue has now been resolved, and the service is operating normally for all affected customers.
Nov 21, 16:14 UTC
Monitoring - The Trello performance degradation affecting some customers has been resolved.
A subset of customers may have experienced intermittent errors on some of our other products, but these should also now be resolved too.
We'll continue to monitor closely to confirm stability.
Nov 21, 15:30 UTC
Update - Multiple Atlassian services are experiencing degraded performance. We are investigating and will provide an update within the hour.
Nov 21, 14:55 UTC
Investigating - Multiple Atlassian services are seeing outages and we are investigating the same. We shall keep you posted on the progress in 60 minutes, if not sooner
Nov 18, 17:29 UTC
Resolved - On November 18, 2025, some Jira Service Management users may have experienced some service disruption. The issue has now been resolved, and the service is operating normally for all affected customers.
Nov 18, 15:23 UTC
Monitoring - Impact
Users of Jira and Jira Service Management are facing intermittent issues when attempting to open Jira issues. They encounter an error message stating No such track. This issue randomly affects the user ability to utilize Jira functionalities.
Current Status
We are seeing some recoveries at the moment. We are actively monitoring to check for re-occurrences. We are also working on establishing a detailed root cause for the incident.
Next Steps
Further updates will be communicated in 60 minutes.
Nov 18, 14:43 UTC
Investigating - We are aware that customers are receiving message NO SUCH TRACK intermittently when opening Jira issues. Our team is investigating this issue and we will share next update in 60 mins if not sooner.
Oct 30, 00:04 UTC
Resolved - Systems are operational and the incident is resolved
Oct 29, 21:34 UTC
Monitoring - Our third-party provider has applied fixes that are gradually resolving the issue. While many users are seeing improvements, some connectivity issues remain. We are actively monitoring the situation.
Oct 29, 20:01 UTC
Update - LastPass engineers continue to work with the cloud provider to resolve the issue.
Oct 29, 17:44 UTC
Identified - Our third party cloud provider has identified the issue and are now actively working towards a resolution. We will provide another update shortly.
Oct 29, 16:23 UTC
Investigating - We’re currently experiencing service degradation on LastPass's marketing site due to an issue with our external cloud provider. Our team is actively working to resolve the issue and minimize the impact.
Oct 21, 09:42 UTC
Resolved - Service degradation issue has been resolved. Vault access and login functionality, including for federated users, are now fully operational.
Oct 21, 09:19 UTC
Update - We’re currently investigating an issue that may prevent some users from logging in. Our team is working to restore full access as quickly as possible.
Oct 21, 09:12 UTC
Investigating - We’re currently experiencing system degradation. LastPass Vaults may take longer to load. Our team is actively working to resolve the problem and minimize impact.
Oct 20, 13:25 UTC
Resolved - This incident has been resolved.
Oct 20, 11:12 UTC
Update - All of our services are now running and operational. However, we are closely monitoring the situation, as some of our external providers who were also affected by this incident are still in the process of recovery.
We’re keeping a close eye on our integrations to ensure continued stability and prevent further disruptions.
Oct 20, 10:41 UTC
Monitoring - Most services have now been restored and are operational, including our phone lines. We continue to monitor the situation closely to ensure full stability.
Oct 20, 09:57 UTC
Investigating - We’re currently experiencing service degradation due to an issue with our external cloud provider, this has also impacted our phone lines. For support, please reach out through our Support Center. Our team is actively working to resolve the issue and minimize the impact.
Oct 15, 13:52 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.
Oct 15, 13:21 UTC
Update - We are continuing to work on a fix for this issue.
Oct 15, 13:20 UTC
Identified - We are currently experiencing an issue that is preventing users from downloading invoices. Our engineering team is actively investigating the root cause and working to restore full functionality as quickly as possible.
Oct 8, 13:41 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.
Oct 8, 13:29 UTC
Monitoring - Our engineers have corrected the issue and we are confirming that all services are functional. We will continue monitoring the situation and provide a final update shortly.
Oct 8, 13:24 UTC
Identified - Our engineers have identified the issue and are now actively working towards a resolution. We will provide another update shortly.
Dec 15, 13:36 UTC
Resolved - This incident has been resolved.
Dec 15, 12:55 UTC
Monitoring - We see an increased latency and errors invoking in Edge Functions on HP Edge starting at 12:38 UTC. This has recovered by 12:44 UTC. Our team is monitoring.
Dec 10, 00:28 UTC
Resolved - This incident has been resolved.
Dec 9, 19:04 UTC
Monitoring - We are no longer experiencing delays, we are continuing to monitor.
Dec 9, 15:35 UTC
Identified - The issue has been identified and a fix is being implemented.
Dec 9, 15:01 UTC
Investigating - We experience delays in delivering Function logs through Log Drains, starting at 13:53 UTC. Our team is investigating.
Dec 8, 17:40 UTC
Resolved - Between 15:20 UTC and 16:30 UTC we saw build failures for builds with functions. The incident has been resolved, and we are no longer observing any issues. Thank you for your patience.
Dec 8, 16:33 UTC
Monitoring - We have deployed a fix to our functions deployment pipeline and are currently monitoring the results.
Dec 8, 16:08 UTC
Identified - The issue has been identified and a fix is being implemented.
Dec 8, 15:54 UTC
Investigating - We're seeing failures to deploy sites (sites what have functions) due to a failure to upload functions. Our team has identified the issue and is working on a fix.
Dec 5, 09:30 UTC
Resolved - From 08:48 UTC to 09:11 UTC today, we experienced an increased error rate invoking edge functions.
Dec 3, 18:22 UTC
Resolved - The latencies should be back to normal as of 18:10 UTC.
Dec 3, 18:09 UTC
Investigating - Starting 17:54 UTC we see increased latency for traffic on the High Performance Edge in the São Paulo region. We're currently investigating this issue.
Dec 5, 09:42 UTC
Resolved - This incident has been resolved.
Dec 5, 09:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 5, 09:02 UTC
Investigating - We are currently investigating this issue.
Nov 18, 19:11 UTC
Resolved - We have confirmed that all systems are now fully operational and the connectivity issues have been completely resolved.
Nov 18, 19:09 UTC
Update - This incident has been resolved. All services are now operating normally. We apologize for the disruption and appreciate your patience.
Nov 18, 15:23 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 18, 13:34 UTC
Investigating - We are currently investigating intermittent connectivity issues affecting npmjs.com. Our team is actively working to restore full service. We apologize for any inconvenience and will provide updates as we learn more.
Nov 6, 14:28 UTC
Resolved - This incident has been resolved.
Nov 6, 14:08 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 6, 13:58 UTC
Update - We are continuing to investigate this issue.
Nov 6, 13:56 UTC
Investigating - We are currently investigating this issue.
Oct 20, 20:15 UTC
Resolved - This incident has been resolved.
Oct 20, 19:20 UTC
Monitoring - We are seeing recovery in package publishing. We will continue to monitor the results.
Oct 20, 17:20 UTC
Investigating - We are currently investigating this issue.
Oct 20, 13:32 UTC
Resolved - This incident has been resolved.
Oct 20, 10:50 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 20, 09:31 UTC
Investigating - We are currently investigating this issue.
The issue is now resolved. For the vast majority of affected connectors have been reconnected successfully. For a small fraction of users, manually reconnecting connectors will be required.
Affected components
- Connectors (Operational)
The affected Github connectors should now be fully restored. Users should be able to use Codex (including code reviews) and ChatGPT with the Github connector without issue.
Affected components
- Codex (Operational)
- Connectors (Operational)
The issue has been resolved.
Affected components
- Conversations (Operational)
All impacted services have now fully recovered.
Affected components
- Search (Operational)
- Conversations (Operational)
- Compliance API (Operational)
- Image Generation (Operational)
- Deep Research (Operational)
- Codex (Operational)
- Connectors (Operational)
- Login (Operational)
- File uploads (Operational)
- Voice mode (Operational)
- GPTs (Operational)
- Agent (Operational)
- ChatGPT Atlas (Operational)
Dec 9, 15:41 PST
Resolved - Our engineers have monitored the fix and confirmed the issue with Segments for Marketing Campaigns has been resolved. All services are now operating normally at this time.
Dec 9, 14:59 PST
Update - Our engineers are still monitoring system performance. We will provide another update in two hours or as soon as more information becomes available.
Dec 9, 12:59 PST
Update - Our engineers are still monitoring system performance. We will provide another update in two hours or as soon as more information becomes available.
Dec 9, 10:58 PST
Update - Our engineers continue monitoring system performance. We will provide another update in two hours or as soon as more information becomes available.
Dec 9, 09:43 PST
Update - Our engineers are still monitoring system performance. We will provide another update in one hour or as soon as more information becomes available.
Dec 9, 07:46 PST
Monitoring - Our engineers have identified the issue and have implemented a fix. Any segments created during 12/05 10:00 am (PST) and 12/09 3:53 am (PST) may still experience issues editing segments in the UI, if so a workaround would be to use an api call to update the segment which would also fix the UI.
Dec 9, 05:35 PST
Update - Our engineering team is continuing to investigate this issue. We will provide another update as soon as more information becomes available. Thank you for your patience.
Dec 9, 04:41 PST
Update - Our engineering team is continuing to investigate this issue. We will provide another update in 1 hour or as soon as more information becomes available.
Dec 9, 03:40 PST
Investigating - Starting around 12:30 AM, PST on 8th Dec, our engineers began investigating an issue with editing currently existing segments. Customers may experience an error in the UI that states 'You can't edit the conditions in this segment This segment contains conditions that cannot be edited in the ui. Please contact your developer to edit the conditions contained in this segment.' This does impact mail send. We will provide another update in an hour or as soon as more information becomes available.
Dec 4, 21:50 PST
Resolved - Our engineers have monitored the fix and confirmed the issue has been resolved. All services are now operating normally at this time.
Dec 4, 21:23 PST
Monitoring - Our engineers have identified the problem and implemented a fix and are monitoring system performance. We will provide another update in 30 minutes or as soon as more information becomes available
Dec 4, 20:53 PST
Investigating - Starting around 8.30 PM PST on Dec 4, our engineers began investigating an issue with our support portal. Customers may experience issues in submitting a ticket. We will provide another update in an hour or as soon as more information becomes available
Dec 4, 16:34 PST
Resolved - Our engineers have monitored the fix and confirmed that users can now create API Keys & teammates again.
Dec 4, 16:03 PST
Monitoring - Starting around 3:40 pm PST on 12/04/2025, our engineers began investigating an issue creating API Keys with custom access & teammates in the UI. API calls to create API Keys & teammates were not impacted. This did not impact mail send.
Our engineers have implemented a fix and are monitoring system performance. Users can now create API Keys & teammates again. We will provide another update in 1 hour or as soon as more information becomes available.
Dec 3, 21:23 PST
Resolved - Our engineers have monitored the fix and confirmed that the delays across the Stats service have been resolved. All services are now operating normally.
Dec 3, 20:31 PST
Monitoring - Between 01:32 to 02:12 AM UTC increased latency and timeouts were observed which resulted in delays across the Stats service, including global stats, advanced stats, and category stats. All latencies have returned to normal. We will provide another update in one hour or sooner if additional information becomes available.
Dec 3, 17:09 PST
Resolved - Our engineers have monitored the fix and confirmed the issue with mail send has been resolved. All services are now operating normally at this time.
Dec 3, 16:57 PST
Monitoring - Starting around 4:10 PM PDT on 2/12/2025, our engineers began investigating an issue with mail send. Customers may have experienced delays during this time. The delay ended at approximately 4:41 PM PDT. We will continue to monitor the situation and provide another update in one hour or as soon as more information becomes available.
Dec 3, 16:46 PST
Investigating - Starting around 4:10 PM PDT on 2/12/2025, our engineers began investigating an issue with mail send. Customers may have experienced delays during this time. The delay ended at approximately 4:41 PM PDT. We will continue to monitor the situation and provide another update in one hour or as soon as more information becomes available.
Dec 10, 22:43 UTC
Resolved - This incident has been resolved.
Dec 10, 21:47 UTC
Update - We're continuing to process the backlog of errors and transactions. New events will be processed in a timely fashion.
Dec 10, 20:40 UTC
Monitoring - We are continuing to work through backlogs in errors and transactions. Profiles, attachments and replays have recovered.
Dec 10, 20:10 UTC
Update - Ingestion has resumed and we are continuing to monitor and restore full service.
Dec 10, 19:51 UTC
Identified - We have identified the source of the issue and are scaling up infrastructure to restore service
Dec 10, 19:22 UTC
Update - We're investigating an unavailable system in our ingestion pipelines.
Dec 10, 19:18 UTC
Investigating - We are currently investigating ingestion delays for errors, spans, attachments, profiles and replays in US.
Dec 10, 22:38 UTC
Resolved - All backlogged errors and transactions have been processed, and ingestion is fully functional.
Dec 4, 01:19 UTC
Resolved - The issue has been resolved.
Dec 4, 01:06 UTC
Monitoring - The fix has been deployed and systems are returning to health. We are continuing to monitor the recovery.
Dec 4, 01:00 UTC
Identified - We have identified an issue related to networking configuration and are currently deploying a fix.
Dec 4, 00:27 UTC
Investigating - We are investigating an issue with the unavailability of the Sentry UI, particularly in the EU region.
Dec 3, 20:57 UTC
Resolved - There was an outage of the issues page and discover feature between approximately 12:30 to 12:40pm PST. The issue has been resolved.
Nov 21, 08:25 EST
Resolved - This incident has been resolved.
Nov 21, 06:00 EST
Update - All affected systems are up and running. We are monitoring associated systems.
Nov 21, 05:59 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 21, 05:15 EST
Identified - Our data processing is running behind due to an issue on GitHub’s side. No data has been lost, and the system should catch up shortly.
Nov 2, 09:31 EST
Resolved - This incident has been resolved.
Nov 2, 09:19 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 2, 08:58 EST
Update - We are continuing to investigate this issue.
Nov 2, 08:58 EST
Investigating - We are currently investigating reports of performance issue with Jobs related functionality
Oct 28, 19:55 EDT
Resolved - This incident has been resolved.
Oct 28, 16:59 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 28, 16:44 EDT
Investigating - We’re experiencing a higher rate of TM Management API errors and are actively investigating the issue.
Oct 24, 17:18 EDT
Resolved - This incident has been resolved.
Oct 24, 13:57 EDT
Update - We are continuing to monitor for any further issues.
Oct 24, 13:57 EDT
Monitoring - A fix has been implemented and we are monitoring the results.
Oct 24, 13:07 EDT
Identified - The issue has been identified and a fix is being implemented.
Oct 24, 12:59 EDT
Investigating - We are currently investigating delays in data processing. Our team is actively working on resolving the issue. We will provide more information as it becomes available. Global Delivery Network services remain operational.
Oct 21, 07:32 EDT
Resolved - This incident has been resolved.
Oct 21, 04:51 EDT
Update - Our feature flags provider has reported that their service has been restored to healthy levels following a load balancer upgrade and capacity increase.
We are seeing signs of recovery and continue to monitor our systems closely.
Oct 21, 00:35 EDT
Update - We continue to experience an issue with our feature flags provider, which may affect some integrations and vendor-related functionality.
Our team is actively monitoring the situation and will share updates as they become available.
Oct 20, 05:50 EDT
Update - We are continuing to monitor for any further issues.
Oct 20, 05:50 EDT
Monitoring - Our Engineering team is currently investigating intermittent performance degradations to the Smartling translation platform and API due to an ongoing AWS outage in the US-EAST-1 region (affecting most of the AWS services), some of our features are experiencing intermittent delays or errors. We will provide more information as it becomes available. Global Delivery Network services remain operational.
Incident has been resolved.
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Cost Tracker (Operational)
- Tempo for Slack (Operational)
AWS have resolved the incident on their end, and Atlassian reported that they are not seeing problems in their systems anymore.
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Cost Tracker (Operational)
- JIRA (Operational)
- Tempo for Slack (Operational)
- Tempo for Jira Cloud Help Center (Operational)
This incident has been resolved.
Affected components
- Timesheets (Operational)
- Cost Tracker (Operational)
- JIRA (Operational)
- Tempo for Slack (Operational)
- Tempo for Jira Cloud Help Center (Operational)
- Capacity Planner (Operational)
This incident was resolved
Affected components
- Cost Tracker (Operational)
- Capacity Planner (Operational)
- Timesheets (Operational)
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.
Dec 5, 09:18 UTC
Resolved - This incident has been resolved.
Dec 5, 09:03 UTC
Investigating - Upstream provider confirmed an incident. We are investigating the impact and potential resolutions.
Dec 1, 07:00 UTC
Resolved - We identified and fixed a bug that could cause messages with Flow Control enabled to be delayed longer than their configured delay, resulting in unexpectedly long pending times.
The fix is in place and the issue should not recur. If you’re still seeing unusually long-delayed messages, please contact [email protected] and we can help with remediation.
Oct 20, 18:50 UTC
Resolved - A fix has been deployed as a workaround so that our systems are not affected from the ongoing incident of the cloud provider
Oct 20, 18:07 UTC
Update - Developer API (api.upstash.com) is having availability issues alongside Upstash Console. While we are monitoring the underlying cloud provider's status updates, we are also working on a remediation.
Oct 20, 15:05 UTC
Monitoring - Console is back to normal again. We are currently monitoring.
Oct 20, 14:52 UTC
Investigating - We are currently experiencing errors in the Upstash Console due to issues with one of our upstream providers. This may affect access to the dashboard and related operations.
Our team is actively monitoring the situation and working to mitigate the impact. We will provide updates as soon as more information becomes available.
Dec 12, 15:34 UTC
Resolved - This incident has been resolved.
Dec 12, 14:45 UTC
Monitoring - We've identified the issue, and we are working on a fix. Vercel customers should be able to create cases normally while we monitor case operation metrics closely.
Dec 12, 13:12 UTC
Investigating - We are investigating an issue with creating new Support Center cases.
For affected Enterprise customers, please escalate out to Vercel contacts via Slack or email for support. For Pro and Hobby customers, please use the Vercel Community: https://community.vercel.com/
Dec 12, 11:47 UTC
Resolved - This incident has been resolved.
Dec 12, 11:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 12, 11:16 UTC
Identified - The issue has been identified and a fix is being implemented.
Dec 12, 10:17 UTC
Investigating - On some projects, traffic is miscategorised and not recorded on Speed Insights and Web Analytics
Dec 10, 06:22 UTC
Resolved - Vercel API errors have been resolved and dashboard access is restored across all regions.
Queued deployments are recovering automatically, but failed deployments may need to be redeployed manually.
Dec 10, 06:16 UTC
Update - We are continuing to investigate this issue.
Dec 10, 06:16 UTC
Investigating - We are currently investigating reports of elevated errors for new deployments, Vercel API, and Vercel dashboard. Existing deployments and live traffic are not affected by this issue. We will share updates as they become available.
Dec 9, 05:51 UTC
Resolved - This incident has been resolved.
Dec 9, 04:15 UTC
Update - Deployments using the Supabase integration are now working as expected. We are continuing to work on `Resource provisioning timed out` errors related to the Neon integration.
Dec 9, 03:29 UTC
Identified - We've identified a potential root cause in our webhook service affecting the build process. We will continue to provide further updates as we learn more.
Dec 9, 00:31 UTC
Investigating - We are currently investigating intermittent `Resource provisioning timed out` errors that occur when creating new deployments with the Neon or Supabase integration. Existing deployments are not affected.
Dec 15, 12:51 PST
Monitoring - We have mitigated the issue affecting the Zoom Room Health dashboard. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Dec 15, 09:00 PST
Investigating - We are currently investigating a service degradation affecting subset of users ability to access Zoom Rooms Dashboard in US 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.
Dec 15, 09:39 PST
Resolved - This incident has been resolved and the affected services have been restored.
Dec 15, 08:49 PST
Update - Our team will continue to monitor the situation closely and keep you informed of any further developments.
Dec 15, 08:31 PST
Monitoring - The service degradation affecting Inbound calls in Zoom Contact Center has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Dec 15, 05:27 PST
Resolved - This incident has been resolved and the affected services have been restored.
Dec 15, 04:09 PST
Monitoring - We have resolved the issue affecting ZVA Voice Agent for Non-English languages. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Dec 15, 02:06 PST
Update - We continue to work on a fix for this issue and will provide updates as soon as there is more information to share.
Dec 15, 00:40 PST
Update - We continue to work on a fix for this issue and will provide updates as soon as there is more information to share.
Dec 14, 23:27 PST
Identified - We have successfully identified the root cause affecting ZVA Voice Agent for Non-English languages.
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.
Dec 10, 02:59 PST
Resolved - This incident has been resolved.
Dec 10, 02:45 PST
Monitoring - On 12/10/2025 between 05:31 UTC to 07:49 UTC - A subset of users experienced issues with sign-in option with SSO Services. Our engineers have mitigated the issue, this incident has been resolved.
Dec 7, 21:36 PST
Resolved - This incident has been resolved and the affected services have been restored.
Dec 7, 21:10 PST
Monitoring - The issue affecting Quality Management interaction services has been successfully resolved. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Dec 7, 20:55 PST
Identified - We have successfully identified the root cause affecting Quality Management interaction services. 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.
Dec 7, 20:40 PST
Update - We are continuing to investigate this issue and will provide updates as soon as there is more information to share.
Dec 7, 20:04 PST
Investigating - We are currently investigating a service degradation affecting Quality Management interaction services. 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.