Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Störungsverlauf von Packagecloud

    26 Packagecloud incidents · Dezember 2014 — official updates, affected components, duration and resolution details.

    Zurück zum aktuellen Status

    Intermittent errors on package uploads

    Beginn 26. November 2025 um 13:00 UTC · 0m

    IssuesGeringfügiger Vorfall
    1. 5. Dezember 2025 um 04:38 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. 5. Dezember 2025 um 04:39 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

    Beginn 24. Oktober 2025 um 04:12 UTC · 29m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    DNSAPIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 24. Oktober 2025 um 04:12 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. 24. Oktober 2025 um 04:24 UTCinvestigating

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

    3. 24. Oktober 2025 um 04:38 UTCinvestigating

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

    4. 24. Oktober 2025 um 04:40 UTCresolved

      This incident has been resolved.

    5. 7. November 2025 um 03:08 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

    Beginn 31. Januar 2024 um 21:36 UTC · 2h 16m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    Frontend
    1. 31. Januar 2024 um 21:36 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. 31. Januar 2024 um 23:35 UTCmonitoring

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

    3. 31. Januar 2024 um 23:51 UTCresolved

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

    Intermittent 50X Errors

    Beginn 31. Januar 2024 um 03:45 UTC · 1h 9m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 31. Januar 2024 um 04:09 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. 31. Januar 2024 um 04:22 UTCmonitoring

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

    3. 31. Januar 2024 um 04:54 UTCresolved

      This incident has been resolved.

    Unable to upload and delete packages via the user interface.

    Beginn 21. Dezember 2023 um 20:19 UTC · 20m

    Pending
    Betroffene Komponenten
    Frontend
    1. 21. Dezember 2023 um 20:19 UTCinvestigating

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

    2. 21. Dezember 2023 um 20:39 UTCresolved

      The incident has been resolved.

    Extended indexing times

    Beginn 14. November 2023 um 23:43 UTC · 2h 28m

    Pending
    Betroffene Komponenten
    Deb/Apt RepositoriesPyPI RepositoriesRPM/yum Repositories
    1. 14. November 2023 um 23:43 UTCinvestigating

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

    2. 15. November 2023 um 02:11 UTCresolved

      This incident has been resolved.

    Duplicate entry for certain package uploads

    Beginn 19. Dezember 2022 um 10:14 UTC · 6h 50m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 19. Dezember 2022 um 10:14 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. 19. Dezember 2022 um 12:19 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. 19. Dezember 2022 um 13:21 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. 19. Dezember 2022 um 16:07 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. 19. Dezember 2022 um 17:04 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

    Beginn 15. Dezember 2022 um 02:21 UTC · 2h 8m

    OutageSchwerwiegender Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 15. Dezember 2022 um 02:21 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. 15. Dezember 2022 um 03:18 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. 15. Dezember 2022 um 04:29 UTCresolved

      This incident has been resolved.

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

    Beginn 15. Dezember 2021 um 15:58 UTC · 18m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesPyPI RepositoriesDatacenterRPM/yum RepositoriesGem RepositoriesFrontend
    1. 15. Dezember 2021 um 15:58 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. 15. Dezember 2021 um 16:16 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

    Beginn 27. Oktober 2021 um 21:15 UTC · 15h 4m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 27. Oktober 2021 um 21:15 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. 28. Oktober 2021 um 12:20 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

    Beginn 25. Januar 2019 um 23:04 UTC · 2h 56m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesDatacenterRPM/yum RepositoriesGem RepositoriesFrontend
    1. 25. Januar 2019 um 23:04 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. 26. Januar 2019 um 01:09 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. 26. Januar 2019 um 01:30 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. 26. Januar 2019 um 02:00 UTCresolved

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

    Increased Error Rates

    Beginn 19. Oktober 2018 um 18:13 UTC · 10m

    IssuesGeringfügiger Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesRPM/yum RepositoriesGem Repositories
    1. 19. Oktober 2018 um 18:13 UTCinvestigating

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

    2. 19. Oktober 2018 um 18:23 UTCresolved

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

    Database Incident

    Beginn 24. Juli 2018 um 18:26 UTC · 56m

    OutageKritischer Vorfall
    Betroffene Komponenten
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 24. Juli 2018 um 18:26 UTCidentified

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

    2. 24. Juli 2018 um 19:18 UTCmonitoring

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

    3. 24. Juli 2018 um 19:22 UTCresolved

      This incident has been resolved.

    Degraded Performance

    Beginn 23. November 2017 um 16:22 UTC · 0m

    Pending
    1. 23. November 2017 um 16:22 UTCresolved

      Increased capacity to help with load issues/degraded performance

    Increased Load/Timeouts

    Beginn 29. September 2017 um 03:17 UTC · 36m

    IssuesGeringfügiger Vorfall
    1. 29. September 2017 um 03:17 UTCidentified

      Increased load is causing issues

    2. 29. September 2017 um 03:53 UTCresolved

      Capacity has been increased, resolved

    Corrupted Deployment

    Beginn 1. September 2017 um 18:11 UTC · 1m

    OutageSchwerwiegender Vorfall
    1. 1. September 2017 um 18:11 UTCidentified

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

    2. 1. September 2017 um 18:12 UTCresolved

      This incident has been resolved.

    Host Down/Unresponsive

    Beginn 13. Juli 2017 um 15:20 UTC · 15h 9m

    IssuesGeringfügiger Vorfall
    1. 13. Juli 2017 um 15:20 UTCidentified

      Failing over

    2. 13. Juli 2017 um 16:10 UTCmonitoring

      Fully failed over, catching up on unprocessed jobs

    3. 14. Juli 2017 um 06:29 UTCresolved

      Everything is back to normal

    Degraded S3 Uploads

    Beginn 10. Januar 2017 um 20:56 UTC · 1h 22m

    IssuesGeringfügiger Vorfall
    1. 10. Januar 2017 um 20:56 UTCinvestigating

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

    2. 10. Januar 2017 um 21:09 UTCinvestigating

      In contact with AWS support to identify and resolve issue.

    3. 10. Januar 2017 um 21:20 UTCidentified

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

    4. 10. Januar 2017 um 22:09 UTCmonitoring

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

    5. 10. Januar 2017 um 22:18 UTCresolved

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

    Hardware Failure

    Beginn 21. Juli 2016 um 18:32 UTC · 13m

    OutageKritischer Vorfall
    1. 21. Juli 2016 um 18:32 UTCidentified

      Currently failing over.

    2. 21. Juli 2016 um 18:40 UTCmonitoring

      Failover complete.

    3. 21. Juli 2016 um 18:46 UTCresolved

      Everything is up and running normally

    Looking into increased connection timeouts

    Beginn 6. Juli 2016 um 19:21 UTC · 11m

    OutageKritischer Vorfall
    1. 6. Juli 2016 um 19:21 UTCinvestigating

      We are currently investigating this issue.

    2. 6. Juli 2016 um 19:32 UTCresolved

      This incident has been resolved.