Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Packagecloud 中断历史

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

    返回当前状态

    Intermittent errors on package uploads

    开始时间 2025年11月26日 UTC 13:00 · 0m

    Issues轻微事件
    1. 2025年12月5日 UTC 04:38resolved

      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. 2025年12月5日 UTC 04:39postmortem

      # 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

    开始时间 2025年10月24日 UTC 04:12 · 29m

    Outage重大事件
    受影响的组件
    DNSAPIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2025年10月24日 UTC 04:12investigating

      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. 2025年10月24日 UTC 04:24investigating

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

    3. 2025年10月24日 UTC 04:38investigating

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

    4. 2025年10月24日 UTC 04:40resolved

      This incident has been resolved.

    5. 2025年11月7日 UTC 03:08postmortem

      ## 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

    开始时间 2024年1月31日 UTC 21:36 · 2h 16m

    Issues轻微事件
    受影响的组件
    Frontend
    1. 2024年1月31日 UTC 21:36investigating

      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. 2024年1月31日 UTC 23:35monitoring

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

    3. 2024年1月31日 UTC 23:51resolved

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

    Intermittent 50X Errors

    开始时间 2024年1月31日 UTC 03:45 · 1h 9m

    Issues轻微事件
    受影响的组件
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2024年1月31日 UTC 04:09investigating

      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. 2024年1月31日 UTC 04:22monitoring

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

    3. 2024年1月31日 UTC 04:54resolved

      This incident has been resolved.

    Unable to upload and delete packages via the user interface.

    开始时间 2023年12月21日 UTC 20:19 · 20m

    Pending
    受影响的组件
    Frontend
    1. 2023年12月21日 UTC 20:19investigating

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

    2. 2023年12月21日 UTC 20:39resolved

      The incident has been resolved.

    Extended indexing times

    开始时间 2023年11月14日 UTC 23:43 · 2h 28m

    Pending
    受影响的组件
    Deb/Apt RepositoriesPyPI RepositoriesRPM/yum Repositories
    1. 2023年11月14日 UTC 23:43investigating

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

    2. 2023年11月15日 UTC 02:11resolved

      This incident has been resolved.

    Duplicate entry for certain package uploads

    开始时间 2022年12月19日 UTC 10:14 · 6h 50m

    Outage重大事件
    受影响的组件
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2022年12月19日 UTC 10:14investigating

      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. 2022年12月19日 UTC 12:19identified

      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. 2022年12月19日 UTC 13:21monitoring

      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. 2022年12月19日 UTC 16:07monitoring

      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. 2022年12月19日 UTC 17:04resolved

      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

    开始时间 2022年12月15日 UTC 02:21 · 2h 8m

    Outage重大事件
    受影响的组件
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2022年12月15日 UTC 02:21identified

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

    2. 2022年12月15日 UTC 03:18monitoring

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

    3. 2022年12月15日 UTC 04:29resolved

      This incident has been resolved.

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

    开始时间 2021年12月15日 UTC 15:58 · 18m

    Issues轻微事件
    受影响的组件
    APIDeb/Apt RepositoriesPyPI RepositoriesDatacenterRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2021年12月15日 UTC 15:58monitoring

      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. 2021年12月15日 UTC 16:16resolved

      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

    开始时间 2021年10月27日 UTC 21:15 · 15h 4m

    Issues轻微事件
    受影响的组件
    APIDeb/Apt RepositoriesPyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2021年10月27日 UTC 21:15investigating

      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. 2021年10月28日 UTC 12:20resolved

      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

    开始时间 2019年1月25日 UTC 23:04 · 2h 56m

    Issues轻微事件
    受影响的组件
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesDatacenterRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2019年1月25日 UTC 23:04monitoring

      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. 2019年1月26日 UTC 01:09identified

      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. 2019年1月26日 UTC 01:30monitoring

      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. 2019年1月26日 UTC 02:00resolved

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

    Increased Error Rates

    开始时间 2018年10月19日 UTC 18:13 · 10m

    Issues轻微事件
    受影响的组件
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesRPM/yum RepositoriesGem Repositories
    1. 2018年10月19日 UTC 18:13investigating

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

    2. 2018年10月19日 UTC 18:23resolved

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

    Database Incident

    开始时间 2018年7月24日 UTC 18:26 · 56m

    Outage严重事件
    受影响的组件
    APIDeb/Apt RepositoriesData StorePyPI RepositoriesRPM/yum RepositoriesGem RepositoriesFrontend
    1. 2018年7月24日 UTC 18:26identified

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

    2. 2018年7月24日 UTC 19:18monitoring

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

    3. 2018年7月24日 UTC 19:22resolved

      This incident has been resolved.

    Degraded Performance

    开始时间 2017年11月23日 UTC 16:22 · 0m

    Pending
    1. 2017年11月23日 UTC 16:22resolved

      Increased capacity to help with load issues/degraded performance

    Increased Load/Timeouts

    开始时间 2017年9月29日 UTC 03:17 · 36m

    Issues轻微事件
    1. 2017年9月29日 UTC 03:17identified

      Increased load is causing issues

    2. 2017年9月29日 UTC 03:53resolved

      Capacity has been increased, resolved

    Corrupted Deployment

    开始时间 2017年9月1日 UTC 18:11 · 1m

    Outage重大事件
    1. 2017年9月1日 UTC 18:11identified

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

    2. 2017年9月1日 UTC 18:12resolved

      This incident has been resolved.

    Host Down/Unresponsive

    开始时间 2017年7月13日 UTC 15:20 · 15h 9m

    Issues轻微事件
    1. 2017年7月13日 UTC 15:20identified

      Failing over

    2. 2017年7月13日 UTC 16:10monitoring

      Fully failed over, catching up on unprocessed jobs

    3. 2017年7月14日 UTC 06:29resolved

      Everything is back to normal

    Degraded S3 Uploads

    开始时间 2017年1月10日 UTC 20:56 · 1h 22m

    Issues轻微事件
    1. 2017年1月10日 UTC 20:56investigating

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

    2. 2017年1月10日 UTC 21:09investigating

      In contact with AWS support to identify and resolve issue.

    3. 2017年1月10日 UTC 21:20identified

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

    4. 2017年1月10日 UTC 22:09monitoring

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

    5. 2017年1月10日 UTC 22:18resolved

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

    Hardware Failure

    开始时间 2016年7月21日 UTC 18:32 · 13m

    Outage严重事件
    1. 2016年7月21日 UTC 18:32identified

      Currently failing over.

    2. 2016年7月21日 UTC 18:40monitoring

      Failover complete.

    3. 2016年7月21日 UTC 18:46resolved

      Everything is up and running normally

    Looking into increased connection timeouts

    开始时间 2016年7月6日 UTC 19:21 · 11m

    Outage严重事件
    1. 2016年7月6日 UTC 19:21investigating

      We are currently investigating this issue.

    2. 2016年7月6日 UTC 19:32resolved

      This incident has been resolved.