Feb 20, 20:17 UTC
Resolved - This incident has been resolved.
Feb 20, 20:10 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 20, 19:42 UTC
Investigating - We are currently investigating this issue.
Feb 20, 15:37 UTC
Resolved - This incident has been resolved.
Feb 20, 15:21 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 20, 14:47 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 20, 14:37 UTC
Investigating - We are currently investigating this issue.
Feb 19, 16:03 UTC
Resolved - This incident has been resolved.
Feb 19, 15:36 UTC
Update - We are continuing to investigate this issue.
Feb 19, 15:30 UTC
Investigating - We are currently investigating this issue.
Feb 18, 18:28 UTC
Resolved - This incident has been resolved.
Feb 18, 15:59 UTC
Update - We are continuing to monitor for any further issues.
Feb 18, 15:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 18, 15:36 UTC
Investigating - We are currently investigating this issue.
Feb 20, 17:44 UTC
Resolved - This incident has been resolved. Between approximately 16:00 UTC and 17:10 UTC, users may have experienced slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered.
Jobs and builds were not impacted during this time.
We apologize for the disruption and thank you for your patience.
Feb 20, 17:31 UTC
Monitoring - We have deployed a fix to stabilize internal services that were experiencing elevated load. Affected components are recovering and we are closely monitoring to confirm full resolution.
Users may still experience some residual slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to catch up and stabilize.
Jobs and builds remain unaffected and continue to run as expected.
We thank you for your patience while our engineers worked to stabilize the affected services. We will provide an update within 30 minutes or earlier.
Feb 20, 17:19 UTC
Identified - We have deployed a fix to stabilize internal services that were experiencing elevated load since approximately 16:00 UTC. Affected components appear to be recovering and we are closely monitoring the situation.
Users may still experience some slow load times on the Pipelines page, errors when viewing pipeline and workflow history, and delays in GitHub commit status checks being delivered as systems continue to stabilize.
Jobs and builds remain unaffected and continue to run as expected.
We will provide our next update within 30 minutes or sooner if things change. We thank you for your patience while we continue to work to resolve this issue.
Feb 20, 16:56 UTC
Update - At approximately 16:00 UTC, we began seeing elevated load on internal data systems that serve read operations across CircleCI. This has resulted in degraded performance on the Pipelines page, difficulty loading historical workflow and pipeline data, and delays in GitHub commit status checks being posted.
Write operations and job execution are unaffected — builds are queuing and running as expected. We are actively working to stabilize affected internal services and restore full read performance across the platform.
We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue
Feb 20, 16:25 UTC
Investigating - We are currently investigating two issues affecting CircleCI services. Users may experience slow load times on the Pipelines page and errors when attempting to view workflow details. Additionally, GitHub commit status checks may not be updating as expected for some users.
Builds and jobs are continuing to run and are not impacted at this time.
We will provide an update within 30 minutes. Thank you for your patience while we work to investigate this issue
Feb 17, 10:30 UTC
Resolved - From 11:48 to 17:16UTC some Bitbucket users may have experienced their organization not present in the CircleCI UI. Additionally some users may have encountered an issue when using `circleci config validate`. We identified the root cause of this issue and have since reverted the change. All systems for Bitbucket users are fully operational as of 17:16 UTC.
Feb 10, 16:13 UTC
Resolved - This incident has been resolved.
Feb 10, 15:54 UTC
Monitoring - We're recovered and are clearing up the backlog.
Feb 10, 15:42 UTC
Update - The issue has been identified and we are pushing out a fix. Thank you for your patience.
Feb 10, 15:41 UTC
Identified - The issue has been identified and we are pushing out a fix. Thank you for your patience.
Feb 10, 15:32 UTC
Update - We are continuing to investigate this issue.
Feb 10, 15:26 UTC
Update - We are continuing to investigate this issue.
Feb 10, 15:21 UTC
Investigating - We are investigating delays of jobs.
We will continue to update while investigating this.
Feb 9, 20:25 UTC
Resolved - Following GitHub's service recovery, all CircleCI functionality has returned to normal operation. Jobs are processing as expected across all resource classes.
Feb 9, 20:13 UTC
Update - Customers using Github may continue to experience delays in Pipelines & UI.
Feb 9, 20:05 UTC
Monitoring - We are starting to see some recovery and jobs are beginning to be triggered by Github again.
Feb 9, 19:59 UTC
Update - We are currently impacted by an ongoing Github outage. We will update once we have more information.
Feb 9, 19:48 UTC
Investigating - We will update as soon as we have more information
Feb 3, 18:58 UTC
Resolved - This incident has been resolved. Thank you for your patience.
Feb 3, 18:19 UTC
Monitoring - The capacity constraints affecting Linux and Remote Docker job execution have been mitigated. Jobs are now starting within expected timeframes. We continue to monitor the situation to ensure stability.
- What's impacted: Linux and Remote Docker job execution - working within normal parameters
- What's happening: Service levels have returned to normal after implementing mitigation measures
We will provide an update within 15 minutes or sooner if conditions change. Thank you for your patience while our engineers worked to resolve this issue.
Feb 3, 17:46 UTC
Update - We are continuing to work on a fix for this issue.
Feb 3, 17:46 UTC
Identified - We have identified delays affecting Linux and Remote Docker job execution. Customers are currently experiencing approximately 3-6 minute delays for these jobs to start due to capacity constraints in our infrastructure provider. All other compute resource classes are operating normally.
We are actively mitigating this issue by routing a portion of traffic to an alternate region and continue working to restore normal service levels.
- What's impacted: Linux and Remote Docker job execution
- What's happening: Jobs are experiencing 3-6 minute delays starting execution due to upstream capacity constraints
We will provide an update with 30 minutes. Thank you for your patience while we work to reduce these delays.
Feb 20, 20:50 UTC
Update - Cloudflare is continuing to restore prefixes to their previous state. Any customer who withdrew their IPs as a result of this incident will see their IPs withdrawn upon full impact mitigation.
Customers are still able to restore service from the dashboard by readvertising their IPs.
Cloudflare is aware that some customers are unable to reload their IPs through the dashboard and are working on a fix.
Feb 20, 20:35 UTC
Update - Cloudflare is continuing to restore prefixes to their previous state.
Customers are still able to restore service from the dashboard by readvertising their IPs. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix
Cloudflare is aware that some customers are unable to reload their IPs through the dashboard and are working on a fix.
Feb 20, 19:45 UTC
Update - Cloudflare is continuing to work on restoring service for impacted customers to what it was before the outage. Customers can self-mitigate by readvertising their prefixes in the dashboard. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix for details on how to advertise a prefix.
Feb 20, 19:20 UTC
Update - Cloudflare is continuing to restore service to customers. Cloudflare has also identified a way for impacted customers to self-resolve impact by readvertising prefixes via the Cloudflare dashboard. Refer to: https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/#advertise-or-withdraw-a-bgp-prefix for details on how to advertise a prefix.
Feb 20, 19:09 UTC
Identified - Cloudflare has identified impact to a subset of BYOIP prefixes. Cloudflare has identified and mitigated the underlying issue and is working to restore availability to impacted advertisements.
Feb 20, 18:45 UTC
Investigating - Cloudflare is investigating issues with our services and/or network. Users may experience errors or timeouts reaching Cloudflare’s network or services. We will update this status page to clarify the scope of impact as we continue the investigation.
Feb 20, 18:56 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 20, 18:47 UTC
Investigating - Customers are experiencing elevated 403 errors on 1.1.1.1 landing page. DNS resolution using Public DNS resolver 1.1.1.1 is not impacted. Cache purge and Debugging page is impacted.
Feb 13, 07:16 UTC
Resolved - The issue has been resolved. Please contact our support if you continue to experience any related issues.
Feb 12, 22:47 UTC
Monitoring - Storage service is stable and fully restored. Our team continues to monitor system performance.
Feb 12, 14:48 UTC
Update - We are continuing to investigate this issue.
Feb 12, 14:43 UTC
Investigating - Some Cloudways Autonomous applications hosted in the London region may experience temporary connectivity issues due to a partial disruption in the underlying storage service. Our team is actively working with the infrastructure provider to restore full stability as quickly as possible.
Jan 28, 15:34 UTC
Resolved - This incident has been resolved.
Jan 28, 13:04 UTC
Investigating - Our upstream provider Vultr is currently experiencing a partial outage in their Singapore region. Their engineering team is actively working to resolve the issue as soon as possible. We regret any inconvenience this may cause.
Jan 21, 08:20 UTC
Resolved - This incident has been resolved.
Jan 20, 10:51 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 19, 10:07 UTC
Investigating - Our SMTP Add-on Service (Elastic Email) is currently experiencing performance issues, leading to delayed outbound emails for some accounts. We are in active communication with the Elastic Email team to investigate and resolve the root cause. We appreciate your patience and will keep this page updated with our progress.
Jan 19, 10:01 UTC
Resolved - This incident has been resolved.
Jan 19, 09:12 UTC
Investigating - We are currently investigating an issue where users are experiencing significant delays in receiving two-factor authentication (2FA) codes via email.
This issue has been traced to a service degradation with one of our upstream email delivery providers. We are in contact with their support team to monitor their progress on a fix. We apologize for the delay and will provide an update as soon as the provider shares more information.
Jan 9, 20:54 UTC
Resolved - This incident has been resolved.
Jan 9, 19:48 UTC
Identified - We have identified an issue with our support chat tool that is affecting communication with our customers. As a result, there may be delays when reporting support issues via chat during this period.
For immediate assistance, please reach out to us by submitting a support ticket.
We greatly appreciate your patience and understanding as we work to resolve this issue as quickly as possible. Thank you for your continued support.
Feb 17, 22:16 UTC
Resolved - The issue has been resolved.
Feb 17, 22:07 UTC
Monitoring - We have resolved the issue and are monitoring the situation.
Feb 17, 21:54 UTC
Identified - We are still observing issues for some customers and are working on a resolution.
Feb 17, 21:33 UTC
Monitoring - We addressed the issue and are monitoring the situation.
Feb 17, 20:55 UTC
Identified - Some customers will find certain features like e.g. Studio disabled. We have identified the issue and are working on a fix.
Feb 9, 20:54 UTC
Resolved - This issue has been resolved.
Feb 9, 20:21 UTC
Monitoring - We were able to mitigate the issue and have re-enabled the regular file uploader.
Feb 9, 13:20 UTC
Update - We have enabled a simpler fallback uploader that provides less functionality while we investigate the issue (XML-like file types, e.g. SVG, are working again though). Customers will need to reload the Contentful WebApp to use the fallback uploader.
Feb 9, 12:48 UTC
Identified - Uploads of XML-like file types, e.g. SVG, are failing. We are working on a resolution.
Feb 9, 12:31 UTC
Investigating - Customers are experiencing issues with uploading assets, specifically SVGs. We are investigating.
Feb 6, 17:19 UTC
Resolved - The issue is now resolved.
Feb 6, 16:46 UTC
Update - We think the impact from the issue is over.
Feb 6, 14:25 UTC
Monitoring - We have deployed a fix which has resolved the issue. We will continue to monitor.
Feb 6, 14:09 UTC
Update - We are still working to mitigate the issue and expect to have a fix in place within the next 30 minutes
Feb 6, 11:35 UTC
Identified - We have identified the cause of the issue and are working on a fix
Feb 6, 11:03 UTC
Investigating - We are investigating an issue where cache purges are not being processed (which may result in customers seeing stale data).
Feb 6, 10:44 UTC
Resolved - The issue is now resolved.
Feb 6, 10:38 UTC
Update - We are continuing to monitor for any further issues.
Feb 6, 10:37 UTC
Monitoring - We have put a fix in place and the Typeform app should now be functional again.
Feb 6, 09:34 UTC
Investigating - Customers are experiencing issues loading the typeform app, we are investigating.
Jan 27, 16:28 UTC
Resolved - This issue has been resolved.
Jan 27, 16:06 UTC
Monitoring - We have deployed a fix which has mitigated the issue for customers. We are continuing to monitor the situation.
Jan 27, 15:41 UTC
Investigating - We are investigating an issue where some customers are experiencing errors containing “COLLIDING_TYPE_NAMES” when using Contentful GraphQL API. This is occurring in particular when customers have content types named “Pages”. We are working on a fix for this issue.
Feb 12, 15:22 EST
Resolved - This incident has been resolved.
Feb 12, 14:55 EST
Monitoring - A fix has been implemented. Existing authorizations should now function as expected. If you’re still seeing an error, please re-authenticate the connector.
Feb 12, 14:10 EST
Investigating - We are currently investigating an issue impacting Microsoft Excel and Sharepoint connectors on the platform.
At this time, customers who encounter connector errors are unable to successfully reconnect to Microsoft. Once the error appears, reconnection attempts are failing, and affected connectors remain blocked.
Our team is actively working to identify the root cause and restore reconnection functionality as quickly as possible.
We will provide updates here as soon as more information becomes available.
Feb 4, 15:27 EST
Resolved - The fix for this issue has been deployed. We are currently monitoring to ensure normal behavior has been fully restored.
Feb 2, 15:58 EST
Identified - We have identified the cause of the issue impacting form submission redirects.
Our engineering team is actively working on a fix, which will be implemented as soon as possible. We will continue to provide updates here as progress is made.
Feb 2, 15:27 EST
Investigating - We are currently investigating an issue where some form submissions are not redirecting respondents as expected after submission.
Under normal circumstances, respondents are redirected back to the form if there is a validation or connector error, allowing them to correct their information and resubmit. If no errors occur, respondents are redirected to the configured thank-you page or redirect URL.
Some submissions may remain on the response processing page and display a default confirmation message instead of submissions displaying potential errors.
Our team is actively investigating the root cause of this issue. We will continue to post updates here as more information becomes available.
Jan 29, 09:51 EST
Resolved - We experienced processing delays with Salesforce connectors in the London region due to increased system load. Our team has upgraded system capacity and the issue is now resolved. All connectors are operating normally.
Jan 23, 14:11 EST
Resolved - This incident has been resolved. Please reach out to [email protected] if you run into any further issues.
Jan 22, 10:00 EST
Identified - We confirmed a secondary issue related to yeseterday's SAML concern where SAML authenticated forms are not preserving URL query parameters after authentication. The team has identified the root cause and is working to resolve the issue. Additional details will be provided here as they become available.
Jan 21, 18:02 EST
Resolved - The issue impacting SAML authentication has been fully resolved. Respondents can now access SAML-authenticated forms as expected, and SAML-based login is functioning normally.
Our team has confirmed service restoration and is continuing to monitor the system to ensure stability. Thank you for your patience while we worked to resolve this issue.
Jan 21, 16:52 EST
Identified - The issue impacting SAML authentication has been identified, and a fix is currently being implemented. Some respondents may still be unable to access SAML-authenticated forms, and SAML-based login may continue to be affected during this time.
Our engineering team is actively deploying the fix and monitoring the situation closely. We will provide another update once the fix has been fully applied and we’ve confirmed service restoration.
Jan 21, 15:40 EST
Investigating - We are currently investigating an issue that is impacting SAML authentication. At this time, some respondents are unable to access SAML-authenticated forms. This issue may also affect SAML-based login.
Our engineering team is actively working to identify the root cause and implement a fix. We will provide updates as more information becomes available.
Feb 20, 20:41 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.
Feb 20, 20:36 UTC
Update - The team continues to investigate issues with some larger runner jobs being queued for a long time. We are though seeing improvement in the queue times. We will continue providing updates on the progress towards mitigation.
Feb 20, 20:01 UTC
Update - We are investigating reports of degraded performance for Larger Hosted Runners
Feb 20, 20:00 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 20, 11:41 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.
Feb 20, 11:19 UTC
Update - The issues with our upstream model provider have been resolved, and GPT 5.1 Codex is once again available in Copilot Chat and across IDE integrations [VSCode, Visual Studio, JetBrains].
We will continue monitoring to ensure stability, but mitigation is complete.
Feb 20, 10:36 UTC
Update - We are still experiencing degraded availability for the GPT 5.1 Codex 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.
Feb 20, 10:02 UTC
Update - We are experiencing degraded availability for the GPT 5.1 Codex 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.
Feb 20, 10:02 UTC
Investigating - We are investigating reports of degraded performance for Copilot
Feb 18, 19:20 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.
Feb 18, 19:18 UTC
Update - We have seen significant recovery in merge queue we are continuing to monitor for any other degraded services.
Feb 18, 18:27 UTC
Update - We are investigating reports of issues with merge queue. We will continue to keep users updated on progress towards mitigation.
Feb 18, 18:26 UTC
Update - Pull Requests is experiencing degraded performance. We are continuing to investigate.
Feb 18, 18:25 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 17, 19:06 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.
Feb 17, 18:55 UTC
Update - We are continuing to monitor the mitigation and continuing to see signs of recovery.
Feb 17, 18:18 UTC
Update - We have rolled out a mitigation and are seeing signs of recovery and are continuing to monitor.
Feb 17, 17:46 UTC
Update - We have identified a low rate of authentication failures affecting GitHub App server to server tokens, GitHub Actions authentication tokens, and git operations. Some customers may experience intermittent API request failures when using these tokens. We believe we've identified the cause and are working to mitigate impact.
Feb 17, 17:46 UTC
Investigating - We are investigating reports of degraded performance for Actions and Git Operations
Feb 13, 22:58 UTC
Resolved - On February 13, 2026, between 21:46 UTC and 22:58 UTC (72 minutes), the GitHub file upload service was degraded and users uploading from a web browser on GitHub.com were unable to upload files to repositories, create release assets, or upload manifest files. During the incident, successful upload completions dropped by ~85% from baseline levels. This was due to a code change that inadvertently modified browser request behavior and violated CORS (Cross-Origin Resource Sharing) policy requirements, causing upload requests to be blocked before reaching the upload service.
We mitigated the incident by reverting the code change that introduced the issue.
We are working to improve automated testing for browser-side request changes and to add monitoring/automated safeguards for upload flows to reduce our time to detection and mitigation of similar issues in the future.
Feb 13, 22:30 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services.
Feb 19, 13:54 EST
Resolved - CRM record creation is now fully accessible. We've identified and addressed the root cause of the issue. The incident has been fully resolved and CRM record creation should be working properly. No data was lost.
Feb 19, 13:53 EST
Monitoring - We've addressed the issue that caused CRM record creation to be unavailable since 1:11 PM EST (UTC -05:00) on Feb 19, 2026. We're monitoring performance closely to ensure the tools recover properly. We will be back with an update within 15 minutes.
Feb 18, 07:24 EST
Resolved - Between 08:48 AM (UTC +00:00) and 12:20 AM (UTC +00:00), many customers in all affected regions experienced issues with session invalidation. This was caused by a load balancer impairment. As of 12:20 AM (UTC +00:00), our session invalidation 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.
Feb 18, 06:19 EST
Monitoring - We've addressed the issue that caused sessions to be invalidated in North America, Europe, the Asian Pacific since 08:48 AM (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.
Feb 18, 06:01 EST
Investigating - We are investigating an issue impacting session expirations and disconnections. 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.
Feb 10, 06:42 EST
Resolved - Between 10:30 AM (UTC +01:00) and 12:20 PM (UTC +01:00), some customers in all affected regions experienced issues with our Google Meet integration. This was caused by a rollout issue. As of 12:20 PM (UTC +01:00), our our Google Meet integration 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.
Feb 10, 06:21 EST
Update - The choice to add "Google Meet" links in meetings isn't available right now for some customers . We're investigating what's causing this issue and will update this page when we have more information. Only customers hosted in North America and Europe are currently impacted. We will be back with an update within 30 minutes.
Feb 10, 06:16 EST
Investigating - Scheduling meetings with Google Meet isn't available right now. We're investigating what's causing this issue and will update this page when we have more information. Only customers hosted in North America and Europe are currently impacted. We will be back with an update within 30 minutes.
Feb 5, 16:41 EST
Resolved - Help desk WhatsApp thread links are now fully accessible. We've identified and addressed the root cause of the issue. The incident has been fully resolved and Help desk WhatsApp thread links should be working properly. No data was lost.
Feb 5, 16:15 EST
Monitoring - We've addressed the issue that caused Help desk WhatsApp thread links to be broken since 2:53 PM EST (UTC -05:00) on Feb 4, 2026. We're monitoring performance closely to ensure the tools recover properly. We will be back with an update within an hour.
Feb 5, 15:08 EST
Identified - We have identified the issue causing Help desk WhatsApp thread links to redirect to a blank help desk thread when clicking "Show conversation". We are working on a fix. We will provide an update when we have more information. We will be back with an update within an hour.
Feb 5, 11:22 EST
Investigating - We are investigating the issue causing Help desk WhatsApp threads to redirect to a blank Help desk thread when clicking "Show conversation" for some customers. 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.
Feb 5, 16:36 EST
Resolved - Between 03:25 PM (UTC -05:00) and 03:59 PM (UTC -05:00), many customers in all affected regions experienced issues with helpdesk, inbox. This was caused by a database impairment. As of 03:59 PM (UTC -05:00), our helpdesk, inbox 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.
Feb 5, 16:20 EST
Monitoring - We've addressed the issue that caused HelpDesk to be partially unavailable in North America, Europe, the Asian Pacific since 02:23 PM (UTC -05: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.
Feb 5, 16:06 EST
Identified - We estimate that we will restore service in the next half an hour.
We are mitigating impact from a database impairment which we believe is caused by a traffic surge. We are scaling the system and pausing non-critical tasks to reduce load.
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.
Feb 20, 12:26 UTC
Resolved - This issue has been resolved and all services are functional.
Feb 20, 12:26 UTC
Update - We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 07:13 UTC
Update - We understand that customers using Customer Service Management, Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours or sooner based on significant progress.
Feb 20, 04:14 UTC
Update - Customers using Jira, Jira Service Management and Confluence may be experiencing difficulties with user and team selection in certain system and custom fields.
We are continuing to work towards mitigating this issue for all users and products.
We anticipate our next update to be posted within 6 hours as we continue our investigation.
Feb 20, 02:52 UTC
Identified - Our team has identified components of Jira Service Management that are also impacted by this incident and we have updated our notifications here appropriately.
We anticipate our next update to be posted within 8 hours, as our team continues working with urgency towards mitigation of this issue.
Feb 20, 2026 - 02:52 UTC
Please see prior notifications relating to this incident below:
Update - Several regions have fully recovered, and the team continues to diligently work on full mitigation. Some affected users may experience inability to select users and teams in specified fields on certain sites.
We anticipate next update to be posted in approximately 8 hours.
Feb 19, 2026 - 21:04 UTC
Update - We continue to make progress on full mitigation, and more users should see experience returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
We will continue to share additional updates here as more information is available.
Feb 19, 2026 - 18:56 UTC
Identified - Mitigation is progressing, and user experience is returning to normal. Some affected users may experience inability to select users and teams in specified fields on certain sites.
Feb 19, 2026 - 17:34 UTC
Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Affected users may experience inability to select users and teams in specified fields on certain sites.
We will continue to share additional updates here as more information is available.
Feb 19, 2026 - 17:14 UTC
Investigating - We are actively investigating reports of performance degradation affecting the ability to select users and teams in specified fields on certain sites.
We will share updates here as more information is available.
Feb 19, 2026 - 16:44 UTC
Feb 7, 05:38 UTC
Resolved - On February 6, 2026, JIRA and JSM experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Feb 7, 05:28 UTC
Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Feb 7, 03:43 UTC
Update - Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
Feb 7, 02:22 UTC
Update - Our teams are in final stages of mitigation. During this time, some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additional updates here as more information is available.
Feb 6, 22:33 UTC
Update - Our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access JIRA and JSM. We will continue to share additioanl updates here as more information is available.
Feb 6, 20:26 UTC
Update - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Feb 6, 20:24 UTC
Update - Impact
The incident is affecting users of the Jira product, resulting in connection failures in specific impacted areas. Customers might be experiencing difficulties accessing or operating certain features within Jira due to this disruption.
Current Status
Our teams are actively addressing the situation, with restoration activities underway. Key efforts include initiating a point-in-time recovery to restore service as efficiently as possible.
Next Steps
The incident response team is focusing on the recovery process to resolve the issue. Further communication will be provided in 30 minutes.
Feb 6, 20:24 UTC
Identified - We have identified the likely cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region may not be able to access Jira and JSM.
We will continue to share additional updates here as more information is available.
Feb 6, 20:01 UTC
Resolved - The team has verified that the fix has successfully propagated to all accounts. Impacted customers will receive an email follow-up containing additional information.
Feb 6, 14:41 UTC
Monitoring - The team has corrected entitlements for impacted customers and reverted plans to Service Collection Free.
We are now monitoring the rollout to confirm the fix has successfully propagated to all accounts.
Feb 6, 10:25 UTC
Update - Our team has identified the steps required to restore the affected sites and is actively working to restore original entitlements.
We will provide our next update in four hours, or sooner if we have meaningful progress to share.
Feb 6, 07:52 UTC
Update - Our team continues active testing of the fix to restore customer accounts affected by this incident.
We will provide further update within two hours or sooner.
Feb 6, 05:57 UTC
Update - Our team is now actively testing the fix required to properly restore customer accounts impacted by this incident.
We will provide further update within two hours to provide guidance on our expected timeline for the resolution to be fully completed.
Feb 6, 03:02 UTC
Identified - During an update designed to enable Service Collection for our Jira Service Management Free customers, some of these customers were incorrectly updated to a Standard Service Collection no-cost trial, and received a notification that they would now need to pay for this service at the end of their trial period.
Please rest assured that requiring payment was not an intended change for these Free customers, and we are working to restore these accounts back to their Free status.
We will provide further update within two hours or earlier if there is important information to share.
Feb 6, 01:47 UTC
Investigating - We are aware of reports that Free JSM customers received emails stating that their plans have been adjusted to Standard Trial Service Collection accounts.
Our team is working urgently to address this issue and we plan to revert the change for all customers that are impacted, to reinstate their Free plan status.
Please note that if your plan has been incorrectly updated, you will be placed into a no-cost trial status.
There is currently no action required from those customers that have incorrectly received these emails.
We will provide further update within an hour as our effort continues.
Feb 5, 21:38 UTC
Resolved - On February 5, 2026, JIRA and JIRA Service Management experienced a disruption, and services were unavailable to affected users. The issue has now been resolved, and the service is operating normally for all affected customers.
Feb 5, 21:09 UTC
Monitoring - The issue has now been resolved, and services are operating normally for all affected customers. We will continue to monitor closely to confirm stability.
Feb 5, 19:22 UTC
Update - Our teams have restored access for most users in us-east-1 region, and continue to work diligently towards full mitigation.
We will continue to share additional updates here as more information is available.
Feb 5, 17:35 UTC
Update - Our team is diligently working on a mitigation, with access being restored for some users in us-east-1 region.
We will continue to share additional updates here as more information is available.
Feb 5, 15:39 UTC
Update - We have identified the cause of the issue, and our teams are diligently working on a mitigation. Some users in us-east-1 region might not be able to access JIRA and JSM.
We will continue to share additional updates here as more information is available.
Feb 5, 14:40 UTC
Identified - Some users in the us-east-1 region cannot access Jira and JSM.
We have identified the cause and placed Jira and JSM in maintenance mode for the affected sites to expedite resolution.
We will provide update on the progress in next 60 minutes or sooner.
Feb 5, 14:13 UTC
Investigating - Some users in us-east-1 region might not be able to access Jira and JSM.
We are aware of this issue and are actively investigating the same.
We will provide update on the progress in next 60 minutes or sooner.
Jan 28, 19:42 UTC
Resolved - On Jan 28, 2026, Jira, Jira Product Discovery, and Jira Service Management users in eu-west-1 region may have experienced delays in viewing recently submitted updates on the web page and/or mobile apps. Updates continued to process successfully during the incident. There are no actions needed from customers. The issue has now been resolved, and the service is operating normally for all affected customers.
Jan 28, 18:50 UTC
Update - We are continuing to investigate an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.
Jan 28, 18:12 UTC
Identified - We are actively investigating an issue affecting Jira, Jira Product Discovery, and Jira Service Management. Affected users may experience delayed issue data in some experiences, such as issue view. We will share updates here in one hour or as more information becomes available.
Feb 18, 14:29 UTC
Resolved - This incident has been resolved.
Feb 18, 03:21 UTC
Update - We are continuing to investigate this issue.
Feb 17, 22:22 UTC
Update - We are continuing to investigate this issue.
Feb 17, 21:09 UTC
Investigating - We are aware of an issue where some customers are not receiving login verification emails required for verification. As a result, impacted users may be unable to complete the login process.
If you are affected, please contact Support using the Request Help Logging in button from this article: https://support.lastpass.com/s/document-item?language=en_US&bundleId=lastpass&topicId=LastPass/having-trouble-logging-in-faq.html&_LANG=enus for assistance, and our team will help verify your identity and restore access.
We will provide updates as the team continues the investigation.
Feb 3, 17:49 UTC
Resolved - We have confirmed that the issue has been resolved completely and all systems are 100% operational at this time. Affected users may need to log out and log back in.
We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.
Feb 3, 16:24 UTC
Monitoring - Our engineering team has identified the underlying issue and completed a rollback, which has mitigated the issue. Affected users may need to log out and log back in to resolve the issue.
We will provide an additional update shortly.
Feb 3, 16:01 UTC
Investigating - We are actively investigating reports that some LastPass users may be experiencing issues launching saved sites from their vault. Access to Vaults is not affected. Engineers continue to troubleshoot the situation and we will update once resolved.
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.
Feb 17, 20:49 UTC
Resolved - We experienced increased latency on app.netlify.com between 20:04 and 20:40 UTC. This incident is resolved.
Feb 11, 12:44 UTC
Resolved - Between 12:00 UTC and 12:28 UTC our Origin showed query contention that caused higher latencies and elevated error rates impacting different components like Origin Servers, Build Pipleine, API and UI utilization.
Feb 11, 12:36 UTC
Update - We are continuing to monitor for any further issues.
Feb 11, 12:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 11, 12:15 UTC
Investigating - We are currently investigating this issue.
Feb 10, 12:56 UTC
Resolved - This incident has been resolved.
Feb 10, 12:52 UTC
Investigating - We're currently investigating an issue with Live Tunnel.
Feb 9, 20:18 UTC
Resolved - This incident has been resolved.
Feb 9, 19:20 UTC
Monitoring - We are seeing some improvement, and we're continuing to monitor this issue.
Feb 9, 19:02 UTC
Investigating - We're currently experiencing an elevated rate of deploy failures. We are investigating this issue.
Feb 9, 17:58 UTC
Resolved - This incident has been resolved.
Feb 9, 17:42 UTC
Monitoring - We are continuing to monitor this issue.
Feb 9, 16:53 UTC
Update - We are continuing to investigate this issue.
Feb 9, 16:46 UTC
Investigating - We're currently experiencing an increase in deploy failures due to an issue affecting an upstream provider.
Feb 17, 22:28 UTC
Resolved - This incident has been resolved.
Feb 17, 21:17 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 17, 20:01 UTC
Investigating - We are currently investigating this issue.
Jan 29, 20:49 UTC
Resolved - This incident has been resolved.
Jan 29, 20:18 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 29, 20:04 UTC
Investigating - We are 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.
All impacted services have now fully recovered.
Affected components
- Video generation (Operational)
All impacted services have now fully recovered.
Affected components
- Search (Operational)
All impacted services have now fully recovered.
Affected components
- Codex (Operational)
All impacted services have now fully recovered.
Feb 12, 10:36 PST
Resolved - Our engineers have monitored the fix and confirmed the issue with Advanced Statistics has been resolved. All services are now operating normally at this time.
Feb 12, 06:42 PST
Update - Our engineering team has identified the root cause of the issue and is continuing to work on implementing a fix. We will provide the next update in four hours or as soon as additional information becomes available.
Feb 12, 03:02 PST
Update - Our engineering team has identified the root cause of the issue and is actively working on implementing a fix. We will provide the next update within four hours or sooner if additional information becomes available.
Feb 11, 22:56 PST
Update - Our engineers have identified the issue and are currently implementing a fix. We will provide another update in next four hours or as soon as more information becomes available.
Feb 11, 20:19 PST
Update - Our engineers have identified the issue and are currently implementing a fix. We will provide another update as soon as more information becomes available.
Feb 11, 16:50 PST
Identified - Our engineers have identified the issue and are currently implementing a fix. We will provide another update in next two hour or as soon as more information becomes available.
Feb 11, 14:47 PST
Update - We are continuing to investigate this issue and will provide an update in the next four hours or as soon as more information becomes available.
Feb 11, 12:47 PST
Update - We are continuing to investigate this issue and will provide an update in the next two hours or as soon as more information becomes available.
Feb 11, 11:46 PST
Update - We are continuing to investigate this issue and will provide an update in the next hour or as soon as more information becomes available.
Feb 11, 10:46 PST
Investigating - Starting around 1pm PST on February 7th, our engineers began investigating an issue with Advanced Statistics (Geographical, Mailbox Provider, Browser, etc.). Customer may experience Incomplete Advanced Statistics for the following date and time frames: 1pm - 5pm PST and 7pm - 9pm PST on 02/07/2026. This does not impact mail send. We will provide another update in an hour or as soon as more information becomes available.
Feb 11, 12:33 PST
Resolved - Our engineers have monitored the fix and confirmed the issue with Ticket Creation within the SendGrid Help Center has been resolved. All services are now operating normally at this time.
Feb 11, 11:35 PST
Update - We are continuing to monitor for any issues. We will provide another update in an hour or as soon as more information becomes available.
Feb 11, 10:43 PST
Update - We are continuing to monitor for any issues. We will provide another update in an hour or as soon as more information becomes available.
Feb 11, 09:37 PST
Monitoring - Our engineers have implemented a fix and are monitoring system performance. Customer should be able to submit a support ticket through the SendGrid Help Center now. We will provide another update in an hour or as soon as more information becomes available.
Feb 11, 08:52 PST
Investigating - Starting around 8:15 am PST on February 11th, our engineers began investigating an issue with the SendGrid Help Center and the Ticket Creation process. Customer may experience errors when creating a support ticket request within the SendGrid Help Center. This does not impact mail send. We will provide another update in an hour or as soon as more information becomes available.
Feb 4, 10:56 PST
Resolved - Our engineers have monitored the fix and confirmed the issue with Sender Authentication has been resolved. All services are now operating normally at this time.
Feb 4, 10:40 PST
Monitoring - Our engineers have implemented a fix and are monitoring system performance. Due to a third-party provider, we were experiencing issues with verifying records within Sender Authentication. We will provide another update in 1 hour or as soon as more information becomes available.
Feb 4, 10:25 PST
Identified - Our engineers have identified the issue and are working toward a fix. We will provide another update in 1 hour or as soon as more information becomes available.
Feb 4, 10:12 PST
Investigating - Starting around 10am on February 4, 2026, our engineers began investigating an issue with Sender Authentication. Users may experience newly created records within the Sender Authentication page not verifying which includes Domain Authentication and Link Branding records that were created after 8:45am PST. This does not impact mail send. We will provide another update in 1 hour or as soon as more information becomes available.
Feb 3, 11:38 PST
Resolved - Our engineering team identified a processing gap which occurred within the Advanced Stats dataset on January 27, 2026, between 07:00 AM PT and 09:00 AM PT. During this two-hour window, data may be incomplete. Impacted reports may show inaccuracies of approximately 8.3% for daily, 1.2% for weekly, and 0.3% for monthly stats.
Our engineering team has confirmed that the Advanced Stats API is fully operational.
Feb 3, 07:02 PST
Update - Our engineering team is actively investigating this issue, and we will provide an update as soon as more information becomes available.
Feb 2, 23:14 PST
Update - Our engineering team is currently investigating this issue. Since the team is still working to identify the root cause, it may take some additional time to resolve. We will provide the next update in 8 hours or so.
Feb 2, 19:45 PST
Update - Our engineering team is actively investigating this issue and we will provide an update as soon as more information becomes available.
Feb 2, 15:56 PST
Update - Our engineering team is actively investigating this issue and we will provide an update as soon as more information becomes available.
Feb 2, 13:51 PST
Investigating - Our engineering team is actively investigating this issue and we will provide another update as soon as more information becomes available.
Feb 2, 13:28 PST
Identified - Our engineers have identified the issue and are working toward and testing a fix. We will provide another update in hour or as soon as more information becomes available.
Feb 2, 12:30 PST
Update - Our engineering team is actively investigating this issue and we will provide another update in one hour or as soon as more information becomes available.
Feb 2, 11:29 PST
Investigating - Starting around 11:00 AM PST, February 2nd, 2026, our engineers began investigating an issue affecting Advanced stats.
Our engineers have identified that a processing delay prevented about two hours of Advanced Stats data from January 27, 2026 from being included. As a result, customers may see incomplete Advanced Stats results when querying reports that include that time window. The Advanced Stats API remains available, but the data returned may be missing information for that period. This is currently being investigated and our team is working on a fix.
Email sending is not affected.
We’ll share another update within the next hour, or sooner as we learn more.
Feb 3, 10:49 PST
Resolved - On February 3, 2026 between 10:08 and 10:26AM PT, our engineering team investigated a service disruption that impacted Marketing Campaigns creating Single Sends, Automations, Contact uploads, and API configuration requests. Customers would have experienced 500 errors. Mail send was not impacted and Legacy Marketing Campaigns were not impacted. Our engineering teams have identified the root cause and restored full functionality. No mail was lost. Services are now operational. We apologize for any inconvenience.
Feb 13, 00:57 UTC
Resolved - We have resolved the issue, and our system is now working as expected
Feb 13, 00:38 UTC
Update - Ingestion is back to normal, alerts may still be delayed. We will continue to monitor the recovery.
Feb 12, 23:44 UTC
Update - We are still continuing to process the backlog and are still monitoring the recovery.
Feb 12, 21:35 UTC
Update - We are still continuing to process the backlog and are still monitoring the recovery.
Feb 12, 19:17 UTC
Update - We are still continuing to process the backlog and are still monitoring the recovery.
Feb 12, 16:54 UTC
Update - We are continuing to process the backlog and are still monitoring the recovery.
Feb 12, 15:00 UTC
Monitoring - We've identified and fixed the issue. We are burning the backlog and actively monitoring the progress.
Feb 12, 09:43 UTC
Investigating - We are investigating the resurfaced Zookeeper issue
Feb 12, 08:34 UTC
Identified - We identified a problem with our Zookeeper cluster and fixed it. We now need to ingest the backlog.
Feb 12, 05:34 UTC
Investigating - We are currently investigating the issue
Feb 9, 19:39 UTC
Resolved - The incident has been resolved
Feb 9, 19:33 UTC
Investigating - We are currently investigating
Jan 29, 23:43 UTC
Resolved - We have resolved the issue and all systems are working as expected.
Jan 29, 23:24 UTC
Monitoring - We have identified an issue related to database contention and have issued a fix. We are continuing to monitor the system as it returns to health.
Jan 29, 23:05 UTC
Update - We are investigating an issue where the Sentry Dashboard may be slow to load.
Jan 29, 23:02 UTC
Investigating - We are currently investigating this issue.
Jan 27, 18:56 UTC
Resolved - Ingestion has recovered.
Jan 27, 18:03 UTC
Identified - The issue has been identified and a fix is being implemented.
Jan 27, 14:51 UTC
Investigating - We are investigating a delay in ingesting spans in the US region.
Jan 24, 00:27 UTC
Resolved - Backlog has been processed and crons should be running as normal
Jan 23, 21:46 UTC
Identified - The issue has been identified and we working through backlogs.
Jan 23, 18:38 UTC
Investigating - We are currently investigating this issue.
Feb 19, 12:53 EST
Resolved - This incident has been resolved.
Feb 19, 12:16 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 19, 11:18 EST
Identified - The issue has been identified and a fix is being implemented.
Feb 19, 10:45 EST
Investigating - We are currently investigating delays in processing file published callbacks and webhooks.
Feb 17, 18:10 EST
Resolved - This incident has been resolved.
Feb 17, 17:26 EST
Monitoring - Fix is applied, we're monitoring queue processing
Feb 17, 08:03 EST
Investigating - We are currently investigating possible delays in jobs authorizaiton and processing
Feb 10, 19:46 EST
Resolved - This incident has been resolved.
Feb 10, 17:41 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 10, 16:36 EST
Investigating - We are currently investigating reports of users experiencing difficulty accessing the Translation Workbench.
Feb 9, 22:41 EST
Resolved - This incident has been resolved.
Feb 9, 18:45 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 9, 11:46 EST
Identified - Due to a disruption on GitHub’s side, the GitHub Connector may experience increased latency in deliveries and request processing. Dashboard, Smartling API, Global Delivery Network services remain operational.
Jan 14, 12:04 EST
Resolved - This incident has been resolved.
Jan 14, 11:34 EST
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 14, 10:54 EST
Investigating - We are currently investigating reports of delays in jobs authorizaiton and processing
The disruption has now been resolved.
Affected components
- Jira (Operational)
- Tempo for Slack (Operational)
- Tempo for Jira Cloud Help Center (Operational)
- Adaptive Planner (Operational)
- Time Tracker (Operational)
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
Resolved
Affected components
- Capacity Planner (Operational)
- Timesheets (Operational)
- Financial Manager (Operational)
- Jira (Operational)
- Tempo for Slack (Operational)
- Tempo for Jira Cloud Help Center (Operational)
- Adaptive Planner (Operational)
Jan 23, 15:30 UTC
Resolved - We identified the cause of elevated latency impacting some databases in us-east-1 region between 15:30–15:35 UTC as a sudden surge of connection attempts that hit OS-level connection limits on our proxy layer. This resulted in slower new connection establishment and increased latency for some requests. Databases were not impacted. We are implementing additional proxy-level metrics and safeguards to detect and manage similar edge cases earlier.
Dec 10, 12:08 UTC
Resolved - Issue has been identified and replicas were successfully reconnected.
Dec 10, 11:50 UTC
Investigating - We identified an issue in Regional Databases in US-East-1 where database replicase have connectivity issues with each other.
Other regions are not impacted. Global databases are not impacted.
We are working on the issue.
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.
Feb 13, 02:56 UTC
Resolved - The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC.
Feb 13, 01:52 UTC
Update - The cause of this issue has been resolved. We are working to recover data on a subset of requests from 21:58-22:50 UTC.
Feb 12, 22:59 UTC
Monitoring - The issue with delayed firewall observability data has been identified. New data has recovered and old data may be delayed.
Feb 12, 22:41 UTC
Investigating - We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
Feb 11, 15:00 UTC
Resolved - On February 11, 2026, between 15:00 and 19:26 UTC, AI Gateway experienced elevated error rates due to an issue affecting Vercel Functions infrastructure in the cle1 and fra1 Vercel Regions. Requests routed to these regions, including requests originating from other regions, may have experienced failed requests or timeouts during this time. We have resolved the issue, and the service is now operating normally. We apologize for the disruption.
Feb 7, 11:18 UTC
Resolved - This incident has been resolved.
Feb 7, 10:23 UTC
Monitoring - We have applied a fix and are seeing recovery across builds and dashboard. We are continuing to monitor.
Feb 7, 09:35 UTC
Identified - We have identified the issue and begun applying a fix. We are beginning to see partial recovery across builds and parts of the dashboard. We will provide additional updates as they become available.
Feb 7, 08:38 UTC
Investigating - We are investigating elevated dashboard load times and error rates on builds. We will provide updates as they become available.
Feb 5, 20:51 UTC
Resolved - This incident has been resolved.
Feb 5, 19:35 UTC
Monitoring - A fix has been implemented and we are beginning to see gradual recovery. We are actively monitoring results and will share more updates as they become available.
Feb 5, 18:28 UTC
Update - We are continuing to implement a fix for delays in data appearing in the dashboard for firewall, billing, and observability. We will share additional updates as they become available.
Feb 5, 16:53 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 5, 16:11 UTC
Investigating - We are investigating delays in firewall observability appearing on the dashboard. We will provide additional updates as they become available.
Feb 3, 21:54 UTC
Resolved - This issue has been resolved and sandboxes are creating normally.
Feb 3, 20:14 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 3, 19:51 UTC
Update - We are releasing a fix and are continuing to work on stabilizing sandbox creation.
Feb 3, 18:49 UTC
Update - We are continuing to work on a fix for this issue.
Feb 3, 18:38 UTC
Identified - We have identified an issue while creating new sandboxes. We are working on a fix for the issue.
Feb 20, 12:02 PST
Resolved - This incident has been resolved and the affected services have been restored.
Feb 20, 11:46 PST
Monitoring - The service degradation affecting Zoom Services in Sao Paulo has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Feb 20, 11:10 PST
Identified - We have successfully identified the root cause affecting Zoom Services in Sao Paulo.
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.
Feb 20, 10:36 PST
Update - We are currently investigating a service degradation affecting Zoom Services in Soa Paulo.
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.
Feb 20, 10:31 PST
Investigating - We are currently investigating a service degradation affecting Zoom Services in Sao Paulo.
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.
Feb 16, 14:41 PST
Resolved - This incident has been resolved and the affected services have been restored.
Feb 16, 14:30 PST
Monitoring - Our third party vendor has successfully resolved the issue which affected AIC Web Search for a subset of users in the US Region.
We will continue to monitor the situation closely and keep you informed of any further developments.
Thank you for your patience.
Feb 16, 14:02 PST
Identified - We have identified an issue with our third party vendor which is affecting AIC Web Search for a subset of users in the US Region. Our team is actively working on a resolution, and we will keep you informed with timely updates as progress is made.
Thank you for your patience.
Feb 13, 13:51 PST
Resolved - This incident has been resolved.
Feb 13, 13:46 PST
Monitoring - On 2/13/2026, between 14:32 UTC and 20:14 UTC we observed a service degradation that affected Zoom Virtual Agent in North America region which has been successfully resolved.
Our team will continue to monitor the situation closely and keep you informed of any further developments.
Feb 11, 16:24 PST
Resolved - This incident has been resolved and the affected services have been restored.
Feb 11, 15:49 PST
Monitoring - Between 02/11/2026 23:07 UTC and 23:15 UTC, a subset of users may have experienced issues with SMS Delivery from a subset of Twilio Long Codes to AT&T in US and Canada Region. Our team will continue to monitor the situation closely and keep you informed of any further developments.
Feb 10, 11:56 PST
Resolved - This incident has been resolved
Feb 10, 11:50 PST
Monitoring - On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.