Uploadcare 中断历史

1. 2026年7月16日 UTC 08:42investigating

   我们目前正在调查一个影响网站和Dashboard的问题。 用户可能遇到更多的错误。 我们的小组正在努力查明根源,一旦获得更多信息,我们将提供最新情况。 我们为任何不便表示歉意并感谢你的耐心.

2. 2026年7月16日 UTC 08:52identified

   我们的小组已查明影响网站和Dashboard的问题的原因,并正在积极努力执行永久解决办法。 在此期间,一些用户可能仍会遇到连通性问题. 随着我们在全面解决方面取得进展,我们将继续分享最新情况。 谢谢你的耐心.

3. 2026年7月16日 UTC 11:11identified

   我们的团队正在努力执行一项永久解决办法。 在此期间,一些用户可能仍会遇到连通性问题. 随着我们在全面解决方面取得进展,我们将继续分享最新情况.

4. 2026年7月16日 UTC 12:51resolved

   影响网站和Dashboard的问题已于协调世界时11:30解决. 用户不应再经历这个问题。 我们的小组正在继续监测执行情况,以确保稳定。 我们为这个问题可能造成的任何干扰而道歉,并感谢你的理解。 谢谢你的耐心 请伸出援手 如果你发现什么不寻常的事.

5. 2026年7月21日 UTC 10:50postmortem

   2026年7月16日,从协调世界时07:55到协调世界时11:15\(约3小时20分\),上传护理的网站和客户门户网站部分无法使用. 在这个窗口中,在我们的 CloudFront 分发中,遇到504个网关超时错误时,受影响的请求可能失败,并且从未到达我们的后端服务. 干扰是由全球亚马逊网络服务\(AWS\) CloudFront断电导致的, 影响VPC起源, 通过 VPC Origins 路由的请求失败,而使用其他来源类型的 CloudFront 分布则未受影响 。 AWS后将停电归结为机队内部能力制约,管理与私人VPC起源的连接,导致线路配置被错误地分配给了它的网络处理器. 重要的是,我们的核心平台服务——包括文件上传、储存、处理和交付已排入清单的文件——没有受到这一事件的影响,并在整个过程中继续正常运作。 我们的后继工作侧重于为这类AWS CloudFront故障保持一个经过验证的,随时待命的倒置. # ** 事件的时间线** 所有时间在协调世界时2026年7月16日. * **07:55 \\ CloudFront 度量衡开始显示我们的网站和网络客户端的出错率较高。 * **07:59 —** 我们的监测警告说,[uploadcare.com](http://uploadcare.com)是无法接触到的。 我们的工程组立即开始调查 * **08:02 * 我们确认[uploadcare.com]的504个错误(http://uploadcare.com),并观察到请求没有到达我们的后端. 其他的云纹的分布仍然健康 * ** 08:07 —** 基于出错模式和CloudFront生成的504出错页面,CloudFront成为了我们的主要疑似根源. 此时,AWS还没有发布任何通知,尽管更广泛的社区已经开始报告CloudFront问题. * **08:28 —** 我们确认这个问题正在影响我们的公共网站和客户门户网站。 * **08:42 * CloudFront 度量衡显示出错率约为30%. * **08:44 * AWS承认全球云纹断层与VPC起源有关——大约在我们撞击开始后49分钟. * **09:23 —** 我们开始实施一个倒计时:从 VPC 源头切换到互联网化的应用程序负载平衡器\(ALBs\). * **10:58 —** 倒计时器被部署到我们的集结环境进行验证. * **11:02 —** 倒计时通过验证 我们开始对生产进行同样的改变。 * **11:15 * AWS解决了潜在的断电. 我们的制作网站和客户门户网站完全恢复,出错率回零. 由于AWS首先恢复,因此生产回落不需要. 我们宣布事件得到解决。 # 进展顺利 # * 快速检测和诊断。 ** 我们的监测在几分钟内就发现了故障,我们的团队将故障与更广泛的AWS问题联系起来,并在AWS公开承认停产之前确定了可能的根本原因。 * 有效缓解。 ** 在事件中,我们设计、实施和验证了我们中间环境的倒置——将云纹原生地从VPC原生地转换成互联网化的ALB。 AWS在我们需要将其应用于生产之前就已经恢复了,但这现已证明是对未来VPC起源事件的一种缓解. * ** 持续影响。 ** 由于故障仅限于使用 VPC Origins 的发行,我们的核心平台——文件上传,存储,处理,和缓存交付——仍然全面运作. 发生了什么事 * ** 共同来源依赖。 ** 我们的公开网站和客户门户网站的发布都依赖于CloudFront VPC Origins,因此一个单一的AWS子系统故障同时影响到它们,没有故障. # ** 行动项目** *保持随时待命的云龙后退* 我们已经准备并验证了基础设施的改变,以便将受影响的分布从VPC起源转换为互联网化的ALB,因此,如果类似AWS断电事件再次发生,这种缓解可以被迅速应用. 我们对这次事件造成的干扰,以及拖延通过我们的状况网页进行通报表示诚挚的歉意。 虽然其根源是我们直接控制之外的AWS方面外出,但我们致力于减少我们面对这种失败的暴露,并在今后更迅速和更透明地沟通.

自动翻译自官方事件更新。

1. 2025年12月19日 UTC 15:23investigating

   We're seeing slow `from_url` uploads processing due to network performance issues at Cloudflare https://www.cloudflarestatus.com/ Since a lot of submitted URLs are hosted by Cloudflare, our `from_url` queue is processing slower than usual.

2. 2025年12月19日 UTC 15:37investigating

   `from_url` uploads are now processing normally. Our team monitors the situation.

3. 2025年12月19日 UTC 16:38monitoring

   `from_url` uploads are processing normally. We're continuing to monitor the situation.

4. 2025年12月19日 UTC 17:31resolved

   Although Cloudflare's issues persist and the files they distribute take longer to download via `from_url` than others, our systems remain stable. We are closing the incident but will continue to monitor the situation.

1. 2025年12月15日 UTC 18:05investigating

   We are currently investigating this issue.

2. 2025年12月15日 UTC 18:07investigating

   We're experiencing performance degradation for Upload API. Uploads are finished with significantly higher latency.

3. 2025年12月15日 UTC 18:50investigating

   We are continuing to investigate this issue.

4. 2025年12月15日 UTC 19:24identified

   The issue has been identified and a fix is being implemented.

5. 2025年12月15日 UTC 20:29identified

   We are continuing to work on a fix for this issue.

6. 2025年12月15日 UTC 20:55identified

   Currently there is a very big task queue accrued during initial production issue phase. We've fixed original issue and are working through this queue. All uploaded files should be accounted for eventually. For end users it still looks like uploads are not working. Affected endpoints: - `/from_url/` - `/base/`

7. 2025年12月15日 UTC 21:59monitoring

   A fix has been implemented and we are monitoring the results. The upload "finish" wait times are still outside of norm.

8. 2025年12月15日 UTC 22:45monitoring

   Extensive processing of Upload API backlog affects DB and therefore latency of REST API and Dashboard.

9. 2025年12月15日 UTC 23:15monitoring

   DB performance is recovered along with REST API and Dashboard.

10. 2025年12月16日 UTC 00:10monitoring

    We are continuing to monitor for any further issues.

11. 2025年12月16日 UTC 00:30monitoring

    The Upload API is still experiencing degradation. You may see longer-than-usual upload processing times, as well as intermittent 5XX responses. We’re actively working to resolve the underlying issue and will continue to share updates.

12. 2025年12月16日 UTC 01:11monitoring

    We experience more DB lateny issues.

13. 2025年12月16日 UTC 01:15investigating

    We experience more DB lateny issues. Investigating, looking for the source of the latency.

14. 2025年12月16日 UTC 03:06monitoring

    A fix has been implemented and we are monitoring the results.

15. 2025年12月16日 UTC 03:32resolved

    The incident is resolved.

16. 2025年12月17日 UTC 12:11postmortem

    # **Analysis of the December 15, 2025, Upload API Disruption** ## 1. Summary On December 15, 2025, the Uploadcare platform experienced a significant service disruption affecting the Upload API and REST API subsystems. The incident, spanning approximately ten hours, resulted in elevated error rates for file uploads, increased latency across API endpoints, and interruptions of Dashboard operations. ## 2. Root cause The root cause was a resource contention event on Amazon Elastic File System \(EFS\), aggravated by an observability side-effect. A monitoring agent, executing a metadata-heavy recursive file scan, monopolized the I/O capacity of the shared NFS mount points. This I/O saturation created a cascading failure due to a legacy architectural pattern where storage operations occur within active database transactions. Background Processing Workers, taking long time to read or write to the stalled filesystem, held open database transactions for a long time. This saturated the global connection pool \(PgBouncer\), causing a denial of service for Upload API HTTP Workers and other services attempting to run database queries, despite the underlying PostgreSQL engine remaining healthy. ## 3. Architectural context and system design The Uploadcare platform is designed for scale, but this incident exposed specific coupling risks between our storage, database, and monitoring layers. ### 3.1 Ingestion pipeline & worker roles The core of the affected system is the Upload API. It utilizes two distinct worker types: 1. Upload API HTTP workers. These synchronous workers handle incoming HTTP requests \(Direct uploads, Multipart, and `from_url` requests\). They ingest data and schedule tasks. 2. Background processing workers. These asynchronous workers pick up tasks from a queue to perform complex operations \(virus scanning, image validation, property extraction, etc\). Both worker types utilize a shared temporary staging area backed by Amazon EFS to maintain a POSIX-compliant shared state across the distributed fleet. ### 3.2 Observability stack To monitor the staging area's health, a Telegraf sidecar agent was configured to track file backlog depth. This was implemented via a standard Linux `find` command sequence. On a network filesystem \(NFS\), a recursive `find` forces a traversal of the directory tree over the network. As file counts grow, the cost of this operation increases linearly, generating a storm of `READDIRPLUS` and `GETATTR` RPC calls. ## 4. Timeline _All times are listed in Coordinated Universal Time \(UTC\)._ * **17:17:** System begins receiving a massive surge of `from_url` upload requests. This workload is write-heavy. * **17:17 – 17:23:** Upload API HTTP workers successfully ingest files and write them to EFS. However, Background processing workers \(responsible for processing and deleting files\) begin to slow down due to the increasing I/O load. The rate of file creation exceeds the rate of processing/deletion. The file count on the volume jumps from ~40 \(healthy\) to ~7,000. * **17:25:** The "Noisy Neighbor" effect begins. The Telegraf `find` command, attempting to scan 7,000\+ files, fails to complete within its 30-second timeout. We lose visibility of metrics related to the file staging area. * **17:30:** Multiple instances of the `find` command stack up. The resulting metadata storm heavily affects the NFS client's ability to process requests. Background processing workers become very ineffective. * **19:06:** PostgreSQL begins terminating client connections due to `idle-in-transaction` timeouts. This confirms workers are stuck holding connections. * **20:28 – 20:51:** Engineering attempts to horizontally scale the PgBouncers to absorb the held connections. This inadvertently pushes the upper layer PgBouncers toward their OS file descriptor limits. * **21:07:** Upper layer PgBouncer instances hit the Linux file descriptor limit \(`ulimit`\). New connections to this layer begin failing. * **21:28:** File descriptor limits are increased. Background processing workers begin to recover slowly as the pool stabilizes. * **23:30:** Background processing workers successfully process the backlog. The background task queue becomes empty. * **23:41:** Despite the background queue being empty, Upload API HTTP workers continue to exhibit "overload" behavior.  * **01:35 \(Dec 16\):** Engineering reconfigures Upload API HTTP workers to connect directly to the upper PgBouncer layer.  * **02:48:** EFS metrics reappear. * **02:58:** Engineers manually removed approximately 4,000 "orphaned" files that remained on the disk \(files where the background job failed during the crash and could not self-heal\). File manipulations on EFS become normal. * **02:59:** Database connection pressure vanished. Latency returned to nominal levels. Incident resolved. ## 5. Response Evaluation ### What went well * Proactive alerting. Our monitoring systems successfully triggered alerts for elevated wait times before customer reports of degradation began to surface, giving the team an early head start on triage. * Core database resilience. Despite the severe saturation of the connection poolers \(PgBouncer\), the underlying PostgreSQL database engine demonstrated remarkable stability. Resource utilization \(CPU/Memory\) on the database nodes remained nominal, preventing a total database meltdown. * URL API isolation. The URL API \(file processing and delivery\) remained fully operational throughout the incident. Its architectural isolation from the ingestion pipeline ensured that end-user access to previously uploaded files was never affected. ### What went wrong * Observability became the bottleneck. The monitoring agent \(`telegraf`\), designed to provide visibility, became the primary cause of the outage. The use of an active, heavy command like `find` on a network filesystem was a design flaw that turned a monitoring check into a Denial of Service attack on the NFS client. * Misleading initial signals. The initial flood of `idle-in-transaction` connections led the response team to focus on the database layer. It delayed the investigation into the storage layer. ## 5. Action Items * Eliminate "Noisy Neighbor" observability. Replace active, resource-intensive monitoring checks \(specifically the recursive `find` command\) with passive metrics. Transition to using AWS CloudWatch metrics or other side-channel indicators that do not consume client-side I/O credits or burden the EFS mount. * Enforce connection pool isolation. Reconfigure PgBouncer to implement strict resource bulkheading. Dedicate separate connection pools for the Upload API HTTP workers, REST API HTTP workers, and background workers. This ensures that a resource stall in the background worker fleet cannot starve the customer-facing APIs of database connections. * Decouple storage I/O from database state. Refactor the application logic to execute blocking file storage operations \(reading/writing to EFS\) _outside_ of atomic database transactions. This ensures that storage latency results only in slower worker throughput, rather than holding database connections open \(`idle-in-transaction`\) and exhausting the global pool. * Upgrade incident response tooling. Equip production containers and nodes with essential diagnostic capabilities and establish secure access protocols. This ensures engineers can diagnose kernel-level and network-level bottlenecks during active incidents. ## 6. Conclusion The December 15 disruption was a complex failure mode involving storage physics, monitoring side-effects, and database concurrency. By identifying the contention on the EFS mount \(caused by the monitoring agent\) as the root cause, rather than a hard AWS limit, we have a clear path to resolution. The removal of the invasive monitoring script and the decoupling of transactions will robustly insulate the Uploadcare platform from similar incidents in the future. We apologize for the disruption and appreciate the patience of our customers as we hardened our systems.

1. 2025年10月20日 UTC 09:48resolved

   On October 20, 2025, between 06:49 UTC and 09:27 UTC, a portion of our URL API service experienced a major disruption. The service responsible for real-time processing and transformation of uncached files was unavailable, resulting in failed requests for those specific operations. The delivery of already-cached files and all other Uploadcare services, including file uploading and management, were unaffected.

2. 2025年10月20日 UTC 09:53postmortem

   On October 20, 2025, between 07:50 UTC and 09:27 UTC, a portion of our URL API service experienced a major disruption. The service responsible for real-time processing and transformation of uncached files was unavailable, resulting in failed requests for those specific operations. The delivery of already-cached files and all other Uploadcare services, including file uploading and management, were unaffected. The direct root cause of this incident was a major service outage in the Amazon Web Services \(AWS\) `us-east-1` \(N. Virginia\) region, specifically impacting AWS DynamoDB. During the incident, we also identified a critical flaw in our incident communication process: we were unable to access our Atlassian-hosted status page to provide timely updates to our customers. It was affected by AWS services disruption, too. Our key follow-up actions will focus on improving the architectural resilience of our services to reduce single points of failure and establishing a more robust, independent system for incident communications. ## Timeline of events All times are in UTC on October 20, 2025. * **06:49:** Our internal monitoring systems begin to alert on a significant increase in error rates and latency for the URL API service, specifically for requests involving uncached files. Our engineering team begins an immediate investigation. * **07:03**: Our engineering team localizes issue with DynamoDB. * **07:37:** The team attempts to update our public status page \(`status.uploadcare.com`\) to inform customers but is unable to log in to the third-party provider \(Atlassian Statuspage\). * **07:46:** We get to conclusion that the issue is related to DNS of DynamoDB. * **07:51:** AWS posts its first notification acknowledging increased error rates and latencies for multiple services in the `us-east-1` region. Our team correlates our internal alerts with this broader AWS issue. * **08:26:** AWS confirms that the issue is centered on significant error rates for DynamoDB in `us-east-1`, confirming our initial diagnosis of the root cause affecting our service. * **09:01:** AWS reports they have identified a potential root cause related to DNS resolution for the DynamoDB API endpoint and are working on mitigations. * **09:27:** Our internal monitoring shows that error rates for the URL API have returned to normal levels. The service is fully recovered and operational. We declare the incident resolved internally. ## What went well * Our internal monitoring systems detected the service failure immediately, allowing for a rapid start to our investigation. * Our engineering team was able to quickly correlate the internal issue with the external AWS service outage, preventing wasted time on internal diagnostics. ## What went wrong * **Architectural single point of failure:** Our URL API for uncached files had a hard dependency on a single service \(DynamoDB\) within a single AWS region \(`us-east-1`\). The failure of this service led directly to the failure of ours, with no mechanism for graceful degradation or failover. * **Failure of incident communication:** Our designated channel for customer communication, the status page hosted at `status.uploadcare.com`, was inaccessible to our team during the outage. This failure prevented us from providing timely and transparent updates to our users, which is a critical part of our incident response protocol. ## Action items * **Establish a redundant status communication channel:** We will set up a secondary, fully independent channel for incident communication. This will ensure that if our primary status page provider is ever unavailable, we can still communicate effectively with our customers. * **Architect for resilience and decentralization:** Our engineering team will conduct a full architectural review of the URL API service. The primary goal is to re-architect the service to remove DynamoDB in `us-east-1` as a single point of failure. This may involve implementing multi-region failover capabilities or introducing a more resilient data caching layer. * **Audit critical services for single points of failure:** We will expand our review to other critical services across the Uploadcare platform to identify and mitigate other potential single points of failure related to external, regional dependencies. We sincerely apologize for the disruption this incident caused our customers and for our failure to communicate the issue in a timely manner. We are committed to learning from this event and implementing these changes to build a more resilient and reliable platform.

1. 2024年11月26日 UTC 14:56investigating

   We're experiencing an elevated level of URL API errors and are currently looking into the issue.

2. 2024年11月26日 UTC 15:16investigating

   Systems are back to normal

3. 2024年11月27日 UTC 09:14resolved

   This incident has been resolved.

4. 2024年11月27日 UTC 09:36postmortem

   ## Incident Summary On 26 November 2024, an issue with our URL API was identified, causing a partial outage of the service from 14:31 to 15:00 UTC. ## Timeline * **14:20 UTC** – A CDN configuration change was made to improve the Auto Format feature in the URL API. * **14:31 UTC** – Service degradation began as increased traffic overwhelmed our origin servers due to cache key changes. * **14:37 UTC** – Alert notifications were received by our team. * **14:58 UTC** – The CDN configuration was rolled back. * **15:00 UTC** – The incident was fully resolved, and service was restored. ## Root Cause The issue was caused by a CDN configuration change that altered cache key behavior, significantly increasing traffic to our origin servers. This overwhelmed our autoscaling groups, which hit their scaling limits, resulting in a service outage. ## Impact URL API degradation lasted for approximately 29 minutes. ## Challenges During Resolution This type of issue is difficult to catch in a staging environment because the traffic profile does not reflect production-level demand. Although the alert system worked as intended, delays in responding to the alert contributed to the resolution time. ## Resolution The configuration change was identified as the root cause and rolled back. The service stabilized immediately after the rollback, and full functionality was restored by 15:00 UTC. ## Action Items ### Short-term * Review and improve escalation processes for alert notifications to reduce resolution time. * Adjust staging environment testing to better simulate production traffic patterns for similar changes. ## Long-term * Assess autoscaling limits to ensure sufficient capacity for handling unexpected traffic spikes. We sincerely apologize for the disruption and are committed to learning from this incident to improve the reliability of our services. Thank you for your understanding and continued support.

1. 2024年11月27日 UTC 10:18resolved

   Issue has been resolved

2. 2024年11月27日 UTC 10:23postmortem

   ## Incident Summary On November 25, 2024, from 16:01 to 19:44 UTC, the “Uploading from 3rd Party Services” feature of our platform was unavailable. This feature allows users to upload files from social networks and storage services like Dropbox, Facebook, Google Drive, and Instagram. ## Timeline * **15:50 UTC** – A server configuration update was initiated to streamline deployments in our Kubernetes environment. * **16:01 UTC** – The outage began as requests to the “Uploading from 3rd Party Services” feature failed to be processed. * **19:00 UTC** – Investigation revealed that the application networking was incorrectly configured. * **19:15 UTC** – A fix was implemented to re-configure the application networking. * **19:44 UTC** – The incident was fully resolved, and service was restored. ## Root Cause The outage was caused by a synchronization issue between repositories during a server configuration update. This misalignment between repositories, compounded by a lack of explicit configuration, led to the service outage. ## Impact For approximately 3 hours and 43 minutes, users were unable to upload files from third-party services. ## Challenges During Resolution This type of issue is difficult to catch in a staging environment because the traffic profile does not reflect production-level demand. Although the alert system worked as intended, delays in responding to the alert contributed to the resolution time. ## Resolution The application configuration was updated and service functionality was fully restored at 19:44 UTC. ## Action Items ### Short-term * Improve feature status monitoring and alerting to detect outages faster. ## Long-term * Improve synchronization processes between repositories to avoid dependency misalignments. ‌ We sincerely apologize for the disruption this caused to our users. We take this incident seriously and are committed to implementing the above action items to prevent similar occurrences in the future. Thank you for your patience and continued trust in our platform. If you have any questions or need further details, please don’t hesitate to reach out.

1. 2024年9月25日 UTC 12:28investigating

   We're experiencing a slowdown in our Webhooks service.

2. 2024年9月25日 UTC 12:29resolved

   This incident has been resolved. We apologize for any inconvenience this may have caused.

3. 2024年9月26日 UTC 08:55postmortem

   ## Incident Summary On 25 September 2024, an issue with webhook delivery was identified, affecting clients between 10:07 and 12:19 UTC. The delay impacted webhook notifications, with no data loss but a significant delay in processing and delivery. ## Timeline * 10:07 UTC – A system configuration change was made, which inadvertently disrupted webhook processing. * 10:07 UTC – Webhook delivery issues began. * 12:05 UTC – The problem was identified and resolved, with backlogged webhooks being processed. * 12:12 UTC – The first webhook was successfully delivered after the fix. * 12:19 UTC – All queued events were processed, with delivery confirmed for all affected users. ## Root Cause The issue was caused by a configuration change that resulted in the webhook delivery system not processing events correctly. Despite initial signs of system health, the disruption went undetected due to gaps in the system’s monitoring tools. ## Impact * Webhook delivery was delayed for approximately 2 hours. * Customers experienced delays in receiving event notifications. * No data was lost, but delivery delays were significant due to a backlog in event processing. ## Challenges During Resolution * Monitoring systems indicated that components of the webhook system were healthy, which delayed identification of the underlying problem. ## Resolution * Webhook processing was restarted, and we verified that all queued events were delivered without any data loss. * The incident was fully resolved by 12:19 UTC, with all webhooks processed and delivered. ## Action Items ### Short-term * Improve the system’s monitoring and alerting to better detect issues with webhook processing. ## Long-term * Explore options to improve the resilience of our webhook delivery system, including scaling the infrastructure to better handle failures.

1. 2024年7月16日 UTC 14:34resolved

   2024-07-08 09:01:53 UTC REST API and Upload API became unavailable due to system misconfiguration. 2024-07-08 09:33:12 UTC We've identified the source of problems, deployed fixes. Service recovered. We are monitoring the situation.

2. 2024年7月16日 UTC 14:45postmortem

   ## REST and Upload API service degradation \(incident #wvjpwt1qtpkn\) **Date**: 2024-07-08 **Authors**: Arsenii Baranov **Status**: Complete **Summary**: From 09:01:53 to 09:33:12 UTC we've experienced higher latencies and in the end a complete outage of Upload and REST API. **Root Causes**: PostgreSQL performance degradation due to human-factor. **Trigger**: Misconfiguration. **Resolution**: Changed our DBA-related processes, fixed monitoring related issue. **Detection**: Our Customer Success team detected the issue and escalated to the Engineering team. **Action Items**: | Action Item | Type | Status | | --- | --- | --- | | Fix monitoring misconfiguration | mitigate | **DONE** | | Improve DBA maintenance approach | prevent | **DONE** | ## Lessons Learned **What went well** * Due to distributed nature of Uploadcare, this incident has no effect on most of our services. This degradation didn’t affect storage, processing and serving files that were already stored by Uploadcare CDN. * Our incident mitigation strategy was right and worked immediately. **What went wrong** * This incident was detected in non-automatic way due to alert misconfiguration. * We failed to process API request during the incident. ## Timeline 2024-07-08 _\(all times UTC\)_ * 08:00 Database maintenance started * 09:01 **SERVICE DEGRADATION BEGINS** * 09:23 Our customer success team escalates issue to Infrastructure team * 09:29 Issue localised and fixed * 09:33 **SERVICE DEGRADATION ENDS**

1. 2023年11月24日 UTC 06:46resolved

   2023-11-21 17:40 -/json/ and -/main_colors/ operations returning 400 status

2. 2023年11月24日 UTC 06:46postmortem

   # -/json/ and -/main\_colors/ operations returning 400 status **Date**: 2023-11-21 **Authors**: Alyosha Gusev **Status**: Complete, action items in progress **Summary**: From 2023-11-21 17:40 to 2023-11-22 18:40 -/json/ and -/main\_colors/ operations started to return 400 status **Root Causes**: HTTP rewrites misconfiguration **Trigger**: Deploy of the new functionality that enables our customers to save more money on traffic, and end users to experience lower load times \(improvements to automatic image optimisation\) **Resolution**: Bugfix deploy **Detection**: Our automatic tests detected the issue **Action Items**: | Action Item | Type | Status | | --- | --- | --- | | Fix rewrites | mitigate | **DONE** | | Improve visibility of failing tests notification | prevent | **DONE** | ‌ ## Lessons Learned **What went well** * Problem was detected by automatic tests * Bugfix was deployed immediately **What went wrong** * We didn’t found out that tests were failing immediately ## Timeline All times UTC * 2023-11-21 17:40: **SERVICE DEGRADATION BEGINS**. Deploy of the new functionality * 2023-11-22 16:18: Team notices failing tests * 2023-11-22 16:19: Issue localised, Incident response team is formed * 2023-11-22 16:19: Team starts bugfix implementation * 2023-11-22 17:40: Fix deployed to production * 2023-11-22 18:40: Last cached error response expired * 2023-11-22 18:40: **SERVICE DEGRADATION ENDS**

1. 2023年10月16日 UTC 09:29monitoring

   We've observed heightened latency and error rates for uncached requests to our CDN and image processing API from 6:00 to 6:45 UTC. This was primarily due to a surge in server load and a deviation in our capacity scaling mechanism. Currently we still experienced heightened load, while capacity scaling mechanism was fixed.

2. 2023年10月16日 UTC 09:34monitoring

   We are continuing to monitor for any further issues.

3. 2023年10月16日 UTC 09:34resolved

   This incident has been resolved.

1. 2023年10月2日 UTC 17:05resolved

   From 14:15 to 16:45 UTC we’ve experienced higher latencies of from_url uploads and with video processing. We’ve identified the source of the problem, eliminated it and are monitoring the situation. These services are fully functional now.

2. 2023年10月4日 UTC 06:38postmortem

   ## Upload API and Video processing services degradation \(incident #5r4zj8shr69c\) **Date**: 2023-10-02 **Authors**: Alyosha Gusev, Denis Bondar **Status**: Complete **Summary**: From 14:15 to 16:45 UTC we’ve experienced higher latencies of Upload API and with video processing due to very high interest in these services. **Root Causes**: Cascading failure due to combination of exceptionally high amount of requests to Upload API. **Trigger**: Latent bug triggered by sudden traffic spike. **Resolution**: Changed our throttling politics, increased resources for processing. **Detection**: Our Customer Success team detected the issue and escalated to the Engineering team. **Action Items**: | Action Item | Type | Status | | --- | --- | --- | | Test corresponding alerts for correctness | mitigate | **DONE** | | Improve our upload processing system to remove bottleneck that we found | prevent | **DONE** | | Fix service access issue for team members that form potential response teams | mitigate | **DONE** | ‌ ## Lessons Learned **What went well** * Due to distributed nature of Uploadcare, this incident has no effect on most of our services. This degradation didn’t affect storage, processing and serving files that were already stored by Uploadcare CDN. * Our incident mitigation strategy was right and worked immediately. **What went wrong** * This incident was detected in non-automatic way due to alert misconfiguration. * Due to hardening security standards in our organisation, not all of incident responders had access to Statuspage to update our customers in timely manner. ## Timeline 2023-10-02 _\(all times UTC\)_ * 14:15 Our upload processing queue start filling * 14:20 **SERVICE DEGRADATION BEGINS** * 15:23 Our customer success team escalates issue to Infrastructure team * 15:31 Issue localised * 15:41 Incident response team is formed * 15:51:13 Adjusted our throttling policies * 15:51:38 Increased number of processing instances * 16:40 **SERVICE DEGRADATION ENDS** Processing queues clear

1. 2023年8月7日 UTC 11:33resolved

   We have experienced a service degradation from 05:08 to 05:10 UTC. The source of the problem was identified and we are working on the fix for the future.

1. 2023年6月22日 UTC 11:41identified

   We’re experiencing higher latencies of from_url uploads. Direct uploads are fully functional. We’ve identified the source of the problem and are working on the fix.

2. 2023年6月22日 UTC 12:32monitoring

   A fix has been implemented and we are monitoring the results.

3. 2023年6月22日 UTC 13:20resolved

   This incident has been resolved.

1. 2023年6月19日 UTC 13:37investigating

   We’re experiencing service degradation of uploads from cloud services (e.g. Facebook, Google Drive). We're currently investigating the issue. Direct uploads are fully functional.

2. 2023年6月19日 UTC 13:42identified

   The issue has been identified and a fix is being implemented.

3. 2023年6月19日 UTC 14:36monitoring

   A fix has been implemented and we are monitoring the results.

4. 2023年6月19日 UTC 14:46resolved

   This incident has been resolved.

1. 2023年5月12日 UTC 14:01resolved

   From 12:29 to 13:31 UTC we’ve experienced higher latencies of from_url uploads. Direct uploads were fully functional. We’ve identified the source of the problem, eliminated it and are monitoring the situation. The service is fully functional now.

1. 2022年2月17日 UTC 15:03resolved

   Between 14:30-14:51 UTC customers may have experienced elevated levels of errors.

1. 2021年12月7日 UTC 17:28identified

   We are experiencing elevated error rates for Webhooks service. We have identified root cause and we are actively working towards recovery.

2. 2021年12月7日 UTC 23:47monitoring

   A fix has been implemented and we are monitoring the results.

3. 2021年12月8日 UTC 09:52resolved

   This incident has been resolved.

1. 2021年7月22日 UTC 16:06investigating

   We are currently investigating the issue with DNS resolving.

2. 2021年7月22日 UTC 16:42investigating

   We are continuing to investigate this issue.

3. 2021年7月22日 UTC 16:44monitoring

   The problems with DNS resolving recovered. We are still monitoring.

4. 2021年7月22日 UTC 18:13resolved

   This incident has been resolved.

1. 2021年6月10日 UTC 13:25investigating

   We are experiencing issues with DNS resolving of *.uploadcare.com

2. 2021年6月10日 UTC 14:04identified

   The issue has been identified and a fix is being implemented.

3. 2021年6月10日 UTC 14:12monitoring

   A fix has been implemented and we are monitoring the results.

4. 2021年6月12日 UTC 20:19resolved

   No more issues with DNS resolving were detected.

1. 2021年5月31日 UTC 18:25resolved

   Between 16:38-16:43 UTC customers may have experienced elevated levels of errors.