https://approjects-vendor-status-watch.static.hf.space/v/uploadcare.htmlIncidents from Uploadcare's public status page, polled daily.Wed, 16 Sep 2026 12:28:20 +0000https://stspg.io/2vjt1qhhv8hxuploadcare:2026-07-16T08:42:22.909ZThu, 16 Jul 2026 08:42:22 +0000On July 16, 2026, between 07:55 UTC and 11:15 UTC \(approximately 3 hours and 20 minutes\), Uploadcare’s website and customer portal were partially unavailable. During this window, affected requests could fail at our CloudFront distributions with 504 Gateway Timeout errors and never reached our backend services. The disruption was caused by a global Amazon Web Services \(AWS\) CloudFront outage affecting VPC Origins, the origin type we rely on for website and customer portal. Requests routed through VPC Origins failed, while CloudFront distributions using other origin types were unaffected. AWS later attributed the outage to an internal capacity constraint in the fleet that manages connections to private VPC origins, which caused routing configuration to be distributed incorrectly to its https://stspg.io/y8w5p0v3jvrruploadcare:2025-12-19T15:23:08.000ZFri, 19 Dec 2025 15:23:08 +0000Although 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.https://stspg.io/qw8n7yg8gh7quploadcare:2025-12-15T18:05:53.656ZMon, 15 Dec 2025 18:05:53 +0000# **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 wihttps://stspg.io/5btg2lfsxc5luploadcare:2025-10-20T00:30:00.000ZMon, 20 Oct 2025 00:30:00 +0000On 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