Hi @ashahba, I think to be fair to the good folks supporting PyPI here, 3 weeks is not a long time for a recovery of an account with that many heavy packages. You’ve had a first response already last week, and replied to that 5 days ago. Now you are waiting for another reply. I’m not sure about the exact timeline, but days to a few weeks between replies doesn’t seem unreasonable.
Now that you are here: you also have a responsibility to PyPI to keep the load you put on PyPI reasonable. Among the packages you own is the number one user of space on PyPI, tf-nightly-intel (see Statistics · PyPI, it uses 325 GB right now). I don’t know if you received the request from the upstream Google TensorFlow team (from this comment: Those builds are not published by the TF DevInfra team and rather by partners. We will bring it to their attention and look to have them remove older nightlies like the official tf-nightly does), but please implement a cleanup mechanism for those nightlies.
And now that I’ve touched on this topic: the support requests for limit increases are also quite backed up. Once in a while I help triage those, because the first response can often be done without needing a PyPI admin, and just knowing the process helps either closing some invalid requests or make the requester add needed info so the admins can decide. My triaging usually happens when I’m getting a question from a project maintainer whose releases are blocked. It’d be great if those requests could get a bit more attention as well. Unlike account recoveries they’re not due to “user error” but only due to using PyPI as it’s meant to be used. Here is an example of a request that is almost 3 months old, for a very popular package (JAX) that now has to delete old releases to make space for new ones: Project Limit Request: Jaxlib - 50 GiB · Issue #3417 · pypi/support · GitHub.