ivanvas

Hi there,

Next month, we're introducing new weekly rate limits for Claude subscribers, affecting less than 5% of users based on current usage patterns.

Claude Code, especially as part of our subscription bundle, has seen unprecedented growth. At the same time, we’ve identified policy violations like account sharing and reselling access—and advanced usage patterns like running Claude 24/7 in the background—that are impacting system capacity for all. Our new rate limits address these issues and provide a more equitable experience for all users.

What’s changing:

Starting August 28, we're introducing weekly usage limits alongside our existing 5-hour limits:

    Current: Usage limit that resets every 5 hours (no change)
    New: Overall weekly limit that resets every 7 days
    New: Claude Opus 4 weekly limit that resets every 7 days
    As we learn more about how developers use Claude Code, we may adjust usage limits to better serve our community. 

What this means for you:

    Most users won't notice any difference. The weekly limits are designed to support typical daily use across your projects. 
    Most Max 20x users can expect 240-480 hours of Sonnet 4 and 24-40 hours of Opus 4 within their weekly rate limits. Heavy Opus users with large codebases or those running multiple Claude Code instances in parallel will hit their limits sooner.
    If you do reach a weekly usage limit, you’ll have the option to purchase more usage at standard API rates to continue working without interruption. This is completely optional.
    You can manage or cancel your subscription anytime in Settings.

We take these decisions seriously. We're committed to supporting long-running use cases through other options in the future, but until then, weekly limits will help us maintain reliable service for everyone. Max 20x subscribers can purchase additional usage at standard API rates if needed.

We also recognize that during this same period, users have encountered several reliability and performance issues. We've been working to fix these as quickly as possible and will continue addressing any remaining issues over the coming days and weeks.

–The Anthropic Team

I've been with DigitalOcean for more than a year. No illegal stuff, of course. I've got an email about investigation. Asked for details, in response got an email that "it's over, we won't tell anything"

The services are terminating within 10d from the original email.

Thanks, DigitalOcean, I actually wanted to move to self-hosted PaaS solution for a long time. More resources for 3x less money.

======= DigitalOcean has become aware of platform abuse involving your account and/or DigitalOcean resources. After review, we are reaching out via email to inform you recent actions performed on your associated infrastructure are in violation of our acceptable use policies.

Activity of an abusive nature violates DigitalOcean’s Terms of Service Agreement [1] and also violates DigitalOcean’s Acceptable Use Policy [2]. As a result, your account has been flagged for suspension per the agreements made when signing up to utilize DigitalOcean.

DigitalOcean has taken proactive action to mitigate harm by administratively locking your resources until we can better understand the intended usage.

No adverse actions have been taken against your data at this time. We will not be able to retain servers and associated data beyond ten days starting from May XX, 2025. Please treat this email as a notice of imminent account termination from our side if we do not hear back from you.

We are requesting this email be considered a high-priority communication to preserve resources. If you believe this decision is in error, DigitalOcean invites you to share a detailed explanation about the deployed resources and their intended purposes.

DigitalOcean is happy to consider appeals based on the information shared with us, along with data we have on file, to determine the best course of action.

If this event is determined to be the result of a misconfiguration of an offering leveraged from the DigitalOcean product portfolio, we are happy to forward the event details over to our Cloud Support operations to help further after we have confirmed. The Cloud Support team will assist with deployment optimization or DigitalOcean resource selection if appropriate based on your needs.

Any further actions and decisions DigitalOcean takes will entirely depend on the response we receive. We are looking forward to hearing from you within 10 days to resolve this event swiftly and prevent destruction of resources.

You can review our Terms of Service agreement and Acceptable Usage policy here

[1] Terms of Agreement: Legal - Terms of Service Agreement (https://www.digitalocean.com/legal/terms-of-service-agreement) [2] Acceptable Usage Policy: Legal - Acceptable Use Policy (https://www.digitalocean.com/legal/acceptable-use-policy)

=======

Thank you for contacting DigitalOcean Support.

We have come to the conclusion that your deployment and actions were in violation of our Terms of Service Agreement [1] and Acceptable Use Policy [2] and as a result, we are unable to remove the lock from your account.

I sincerely apologize for any inconvenience caused by this.

Additionally, please note that we're unable to share details regarding what factors we considered that led to this decision or how we came to this conclusion as this is critical to maintaining the integrity of our platform security operations.

You can review our Terms of Service agreement and Acceptable Usage policy here

[1] Terms of Agreement: Legal - Terms of Service Agreement (digitalocean.com) [2] Acceptable Usage Policy: Legal - Acceptable Use Policy (digitalocean.com)

We recommend you find a new service provider that better suits your needs as our security tooling would consider these actions when you sign up again resulting in account locks and termination of linked accounts during manual platform-wide reviews.

No further actions are needed from your end.

Regards,

--- --- Associate Customer Advocate DigitalOcean Support