Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Packagecloud outage history

    26 recorded Packagecloud incidents since December 2014, with official updates, affected components, duration and resolution information.

    Back to current status

    Intermittent errors on package uploads

    Started November 26, 2025 at 1:00 PM UTC · 0m

    IssuesMinor incident
    1. December 5, 2025 at 4:38 AM UTCresolved

      On November 26th, 2025, from approximately 03:00AM UTC until 20:19PM UTC, our package upload service experienced intermittent failures affecting file uploads. Customers attempting to upload Maven, RPM, and Debian packages encountered HTTP 500 errors. Retrying occasionally resulted in a successful upload, but overall reliability was significantly reduced during this period.

    2. December 5, 2025 at 4:39 AM UTCpostmortem

      # Summary At 09:52AM UTC, we received the first customer report indicating HTTP 500 errors during Debian package uploads. Additional reports followed throughout the day, confirming that multiple package types and customers were affected. After an internal investigation, the issue was declared an incident at 18:19PM UTC. The underlying cause was found to be insufficient disk space on a subset of ECS tasks responsible for handling file uploads. These tasks had reached their disk capacity, preventing them from completing upload operations. Because the tasks were running at maximum disk usage, they also could not be automatically cycled out by ECS, allowing the problem to persist. During the investigation we observed an increase in device maximum capacity errors, and inspection of the ECS cluster revealed tasks of varying ages. This correlated with the accumulation of temporary files generated during package extraction and processing. Although temporary file cleanup mechanisms exist, they did not adequately prevent disk saturation. As a short-term remediation, a deploy was triggered to refresh all ECS tasks, which replaced the existing tasks with new ones. Following this deployment, upload functionality stabilized and no further customer impacting errors were observed. The issue was considered mitigated at 20:19PM UTC. Subsequent analysis confirmed that temporary file usage was a significant contributor to disk exhaustion. Additional improvements were implemented to ensure temporary files are consistently closed and cleaned up, regardless of whether errors occur during processing. ## Changes we’re making: To reduce the likelihood of similar incidents in the future, we are implementing the following long-term improvements: * Strengthening disk usage observability: Enhanced monitoring now provides realtime insight into ECS task disk consumption, enabling earlier detection of abnormal usage. * Improving temporary file lifecycle management: Further audit and cleanup of temporary file handling across the codebase is underway to minimize unnecessary disk usage. * Refining ECS task lifecycle practices: We are reviewing our deployment and recycling strategy to ensure tasks do not remain active long enough to accumulate excessive temporary data. * Enhancing health checks: We are evaluating load balancer health check behavior to ensure that resource-degraded tasks \(including those with insufficient disk\) are identified and replaced more promptly.

    Increased 403 Errors on package access

    Started October 24, 2025 at 4:12 AM UTC · 29m

    OutageMajor incident
    Affected components
    DNSAPIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. October 24, 2025 at 4:12 AM UTCinvestigating

      We are currently investigating an increase in 403 (Forbidden) errors affecting some Packagecloud repositories. Users may experience access denied errors when attempting to read packages. Our team is actively investigating the root cause and will provide updates as more information becomes available.

    2. October 24, 2025 at 4:24 AM UTCinvestigating

      We have confirmed it does not affect PyPI and are continuing to investigate the issue.

    3. October 24, 2025 at 4:38 AM UTCinvestigating

      This incident has been resolved - we've reverted the change that was causing the issue.

    4. October 24, 2025 at 4:40 AM UTCresolved

      This incident has been resolved.

    5. November 7, 2025 at 3:08 AM UTCpostmortem

      ## Service Impact On October 24th, 2025 from approximately 01:53AM UTC until 04:24AM UTC our package download service experienced an outage affecting customer access. This was confirmed to have impacted Debian and RubyGems. ## Incident Summary At 01:13AM UTC we updated the S3 Bucket Policy for an S3 bucket containing customer packages via Terraform as part of a larger re-architecting project. We received customer reports about Debian package download issues from 01:53AM UTC and started doing isolated, per-customer investigations. At 03:40AM UTC we concluded that the issues were not isolated and declared the incident. More members from our team were called to help investigate the problem, where we found that service for pulling RubyGems had also been impacted. Around 04:00 UTC, the new bucket policy deployed at 01:13AM UTC was identified as a main factor to the access failure and was removed. At 04:19AM UTC our team identified that updating the IAM policy via Terraform did not have the expected result of merging with the pre-existing policy, but rather inadvertently overwrote the pre-existing access policies, causing the loss of access permissions necessary for package downloads. Afterwards it became apparent to our team making these changes that this particular behavior is a [known issue](https://github.com/hashicorp/terraform-provider-aws/issues/6334) with the Terraform AWS provider, which contributed to the difficulty of detection and prevention, thereby increasing the likelihood of the incident occurring for those unaware. After redeploying the pre-existing S3 bucket IAM policy, we confirmed service functionality for Debian package downloads was restored at 04:24 AM UTC. The team subsequently verified that pulling RubyGems and other supported package types were also functioning as expected, and the incident was closed at 04:47 AM UTC. ## Changes we're making We are revising our monitoring approaches to identify and address service disruptions proactively, while also improving our communication processes to ensure timely and accurate customer updates.

    Website unavailable

    Started January 31, 2024 at 9:36 PM UTC · 2h 16m

    IssuesMinor incident
    Affected components
    Frontend
    1. January 31, 2024 at 9:36 PM UTCinvestigating

      Our marketing website is currently unavailable and we are investigating. The product is unaffected — the management dashboard and all package management functions are fully available.

    2. January 31, 2024 at 11:35 PM UTCmonitoring

      Website has been restored, but we're keeping an eye on things.

    3. January 31, 2024 at 11:51 PM UTCresolved

      The website continues to be available, and we're confident the root cause has been addressed.

    Intermittent 50X Errors

    Started January 31, 2024 at 3:45 AM UTC · 1h 9m

    IssuesMinor incident
    Affected components
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. January 31, 2024 at 4:09 AM UTCinvestigating

      We have seen some intermittent 50X errors, which we think may be related to the change in traffic profile that we're seeing. We will update once we have more details. Thank you for your understanding.

    2. January 31, 2024 at 4:22 AM UTCmonitoring

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

    3. January 31, 2024 at 4:54 AM UTCresolved

      This incident has been resolved.

    Unable to upload and delete packages via the user interface.

    Started December 21, 2023 at 8:19 PM UTC · 20m

    Pending
    Affected components
    Frontend
    1. December 21, 2023 at 8:19 PM UTCinvestigating

      We are currently facing issues with uploading and deleting packages via the user interface. We are actively investigating this issue.

    2. December 21, 2023 at 8:39 PM UTCresolved

      The incident has been resolved.

    Extended indexing times

    Started November 14, 2023 at 11:43 PM UTC · 2h 28m

    Pending
    Affected components
    Deb/Apt RepositoriesPyPI RepositoriesRPM/yum Repositories
    1. November 14, 2023 at 11:43 PM UTCinvestigating

      We are aware of extended indexing time of repos and are actively investigating the issue.

    2. November 15, 2023 at 2:11 AM UTCresolved

      This incident has been resolved.

    Duplicate entry for certain package uploads

    Started December 19, 2022 at 10:14 AM UTC · 6h 50m

    OutageMajor incident
    Affected components
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. December 19, 2022 at 10:14 AM UTCinvestigating

      Some customers have reported issue with uploading packages, suspected to be previously uploaded and deleted. Some customers have also reported repo install scripts not working as expected as it cannot pull down the repo config for the system where packages are to be installed.

    2. December 19, 2022 at 12:19 PM UTCidentified

      We have identified the issue to be related to the identifier limits in our database. We're in the process of releasing a fix within the next hour 1400 UTC.

    3. December 19, 2022 at 1:21 PM UTCmonitoring

      We have released a fix to bypass the issue of repo install scripts not working as expected. We're monitoring customer feedback and report for that. We have started working on a bypass for duplicate entry for package upload, with the ETA still expected to be 1400 UTC.

    4. December 19, 2022 at 4:07 PM UTCmonitoring

      We've released a fix to address the 'Duplicate Error, Aborting' issue encountered by users trying to upload packages. We're now monitoring customer reports and feedback.

    5. December 19, 2022 at 5:04 PM UTCresolved

      The workaround has resolve the issue of 'Duplicate Error' and repo install script issue that affected private repositories. We will work on expanding the namespace limits for private read tokens to ensure future scalability.

    Packages uploaders not available to handle upload

    Started December 15, 2022 at 2:21 AM UTC · 2h 8m

    OutageMajor incident
    Affected components
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. December 15, 2022 at 2:21 AM UTCidentified

      We've identified the issue as the uploader services not being able to load the docker images required to start the uploader services.

    2. December 15, 2022 at 3:18 AM UTCmonitoring

      The base image required by our uploaders has been rebuilt and redeployed. All package uploads should be working. We're monitoring the situation.

    3. December 15, 2022 at 4:29 AM UTCresolved

      This incident has been resolved.

    AWS us-west-1 connectivity issues may impact packagecloud.io

    Started December 15, 2021 at 3:58 PM UTC · 18m

    IssuesMinor incident
    Affected components
    APIDeb/Apt RepositoriesPyPI RepositoriesDatacenterRPM/yum RepositoriesGem RepositoriesFrontend
    1. December 15, 2021 at 3:58 PM UTCmonitoring

      AWS us-west-1 is having connectivity issues that may cause intermittent connectivity issues to packagecloud.io services. For more details please also refer to: https://status.aws.amazon.com/

    2. December 15, 2021 at 4:16 PM UTCresolved

      AWS us-west-1 has fully recovered connectivity and any connectivity issues to packagecloud.io services is fully restored. For more details please also refer to: https://status.aws.amazon.com/

    Intermittent 50X Errors

    Started October 27, 2021 at 9:15 PM UTC · 15h 4m

    IssuesMinor incident
    Affected components
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. October 27, 2021 at 9:15 PM UTCinvestigating

      We have seen some intermittent 50X errors, which we think may be related to the change in traffic profile that we're seeing. We will update once we have more details. Thank you for your understanding.

    2. October 28, 2021 at 12:20 PM UTCresolved

      There has not been any 50Xs occurrence alerts nor any customer report in the last 10 hours. We removed one stat that was showing total downloads, which is a bit compute intensive as precaution.

    Fallout from Maintenance Window

    Started January 25, 2019 at 11:04 PM UTC · 2h 56m

    IssuesMinor incident
    Affected components
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesDatacenterRPM/yum RepositoriesGem RepositoriesFrontend
    1. January 25, 2019 at 11:04 PM UTCmonitoring

      We are still dealing with some fallout from our scheduled maintenance. The issue has been identified and all required parties are working on it.

    2. January 26, 2019 at 1:09 AM UTCidentified

      We have started an alternative contingency plan in order to restore website functionality, it should finish soon. Thanks again for your patience while we work to resolve this issue.

    3. January 26, 2019 at 1:30 AM UTCmonitoring

      The site appears to be fully restored, however we will be closely monitoring the situation to make sure it remains operational before resolving this incident.

    4. January 26, 2019 at 2:00 AM UTCresolved

      Still monitoring site health as usual, but marking this particular incident as resolved.

    Increased Error Rates

    Started October 19, 2018 at 6:13 PM UTC · 10m

    IssuesMinor incident
    Affected components
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesRPM/yum RepositoriesGem Repositories
    1. October 19, 2018 at 6:13 PM UTCinvestigating

      We're experiencing increased error rates for Amazon S3 requests in the US-WEST-1 Region.

    2. October 19, 2018 at 6:23 PM UTCresolved

      The issue has been resolved and the service is operating normally.

    Database Incident

    Started July 24, 2018 at 6:26 PM UTC · 56m

    OutageCritical incident
    Affected components
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. July 24, 2018 at 6:26 PM UTCidentified

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

    2. July 24, 2018 at 7:18 PM UTCmonitoring

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

    3. July 24, 2018 at 7:22 PM UTCresolved

      This incident has been resolved.

    Degraded Performance

    Started November 23, 2017 at 4:22 PM UTC · 0m

    Pending
    1. November 23, 2017 at 4:22 PM UTCresolved

      Increased capacity to help with load issues/degraded performance

    Increased Load/Timeouts

    Started September 29, 2017 at 3:17 AM UTC · 36m

    IssuesMinor incident
    1. September 29, 2017 at 3:17 AM UTCidentified

      Increased load is causing issues

    2. September 29, 2017 at 3:53 AM UTCresolved

      Capacity has been increased, resolved

    Corrupted Deployment

    Started September 1, 2017 at 6:11 PM UTC · 1m

    OutageMajor incident
    1. September 1, 2017 at 6:11 PM UTCidentified

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

    2. September 1, 2017 at 6:12 PM UTCresolved

      This incident has been resolved.

    Host Down/Unresponsive

    Started July 13, 2017 at 3:20 PM UTC · 15h 9m

    IssuesMinor incident
    1. July 13, 2017 at 3:20 PM UTCidentified

      Failing over

    2. July 13, 2017 at 4:10 PM UTCmonitoring

      Fully failed over, catching up on unprocessed jobs

    3. July 14, 2017 at 6:29 AM UTCresolved

      Everything is back to normal

    Degraded S3 Uploads

    Started January 10, 2017 at 8:56 PM UTC · 1h 22m

    IssuesMinor incident
    1. January 10, 2017 at 8:56 PM UTCinvestigating

      Amazon S3 is throwing intermittent 500 Internal Server Errors on upload.

    2. January 10, 2017 at 9:09 PM UTCinvestigating

      In contact with AWS support to identify and resolve issue.

    3. January 10, 2017 at 9:20 PM UTCidentified

      AWS has confirmed that the issue is internal to AWS and they are working on deploying a fix.

    4. January 10, 2017 at 10:09 PM UTCmonitoring

      AWS has rolled out a fix and all affected repositories are being reindexed.

    5. January 10, 2017 at 10:18 PM UTCresolved

      All affected repositories have been reindexed and uploads appear to be working normally.

    Hardware Failure

    Started July 21, 2016 at 6:32 PM UTC · 13m

    OutageCritical incident
    1. July 21, 2016 at 6:32 PM UTCidentified

      Currently failing over.

    2. July 21, 2016 at 6:40 PM UTCmonitoring

      Failover complete.

    3. July 21, 2016 at 6:46 PM UTCresolved

      Everything is up and running normally

    Looking into increased connection timeouts

    Started July 6, 2016 at 7:21 PM UTC · 11m

    OutageCritical incident
    1. July 6, 2016 at 7:21 PM UTCinvestigating

      We are currently investigating this issue.

    2. July 6, 2016 at 7:32 PM UTCresolved

      This incident has been resolved.