Warning this is rando internet detective work so YMMV JustJake at twitter would likely know the actual answer to this question.

It was mentioned that the service was artifact registery[1]. They were 5000/10min and approved at 18k/min [2] The ui appears to show a limit of 100 but not what of [3].

So reading the docs on artifact registery quota docs the only things that stands out is the "1 repository creation or deletion operation every 2 seconds."[4] so doing the math that is a rate limit of 30 per minute or 300 per 10 min so aroudn the ballpark of what they are. Looking at my own project this matches up and I can add request new quotas[4] but it needs to go through a human on googles end to approve.

Anyhoo if they were approved for 18k/min that is nearly 600x the normal quota. So they were likely (pure speculation) caught up in some kind of dragnet of quotas that were well beyond the norm. Skimming the site[6] it appears to be a rapid cloud based ide / deployment thing and I can't imagine how they are creating so many repos unless for each customer build they pass along to gcp's artifact registery 1-1. I use artifactory repo as well for managing docker images but mostly just make new tags off a handful of repos and am not typically creating them at such scale.

Sucks that they had the quota lowered without warning but "if" they were operating at the speculated quota that is flying pretty close to the sun.

[1] https://twitter.com/JustJake/status/1667660212902453248 [2] https://twitter.com/JustJake/status/1667492928758095872 [3] https://twitter.com/JustJake/status/1667478906591666176 [4] https://cloud.google.com/artifact-registry/quotas#project-qu... [5] https://console.cloud.google.com/apis/api/artifactregistry.g... [6] https://railway.app/