Oracle Cloud Slashes Free Tier: Thousands of Users Face 10-Day Ultimatum

basanta sapkota
Picture this: you're checking your Oracle Cloud dashboard over morning coffee, and suddenly your free tier instances are showing red. Over the limit. But you didn't change anything. No email warning.Now blog post. Nothing.

That's exactly what hit thousands of developers and hobbyists in mid-June 2026. Oracle slashed its Always Free tier compute allowance in half. Just like that. The Ampere A1 free tier dropped from 4 OCPUs and 24 GB of RAM down to 2 OCPUs and 12 GB.

Got instances over those new limits? You have until August 18, 2026 to fix it, or Oracle terminates them automatically.

Oh, and here's the best part—they never told anyone. They just updated the docs and walked away.

The Damage Report

Oracle halved everything. The Always Free tier went from 3,000 OCPU hours and 18,000 GB RAM hours per month down to 1,500 and 9,000. No official announcement. Users found out when their instances died or they stumbled across the updated documentation.

August 18, 2026 is your deadline. Miss it and your instances get shut down.

Now, some support emails claim PAYG accounts might be exempt. But the official docs say otherwise. So nobody really knows.

And those grandfathered instances you're running at the old 4/24 configuration? One termination event—maintenance, outage, user error—and you're locked into 2/12 forever. Can't recreate what you had.

Trust in Oracle's free tier? Completely cratered across Reddit and Hacker News.

People are looking at AWS, Google Cloud, Hetzner, DigitalOcean. Anywhere but Oracle.

What They Actually Cut

Let's look at the numbers.

Before: 3,000 OCPU hours monthly, 18,000 GB RAM hours monthly. Run 24/7 and that's 4 OCPUs with 24 GB RAM.

After June 15, 2026: 1,500 OCPU hours, 9,000 GB RAM hours. Now you get 2 OCPUs and 12 GB continuously.

This was genuinely one of the best free cloud offerings out there. Developers were running personal VPNs on it. Minecraft servers. Docker containers. Home automation reverse proxies. Lightweight AI inference with Ollama. That 4-core, 24GB ARM instance handled real workloads.

Now you get half. And if you had multiple smaller instances together exceeded 2 OCPUs and 12GB? Those count too.

The Stealth Update

Here's where Oracle really messed up.

According to InfoQ's reporting, they made zero public announcements.Now blog post.And email to free tier users.And console banner notification.

They updated the Always Free Resources documentation page. That's it.

Users found out when their instances stopped working. Or when community members noticed the changed numbers on Oracle's site.And when they tried spinning up new instances and hit the lower caps.

One Reddit user came home to find their homelab dead. Another spent hours troubleshooting what they thought was a technical glitch. The r/oraclecloud subreddit and Hacker News lit up immediately.

Look, cloud providers adjust free tiers. That's normal. AWS does it. Google Cloud does it. Azure does it.

But you don't do it silently. You don't leave people to discover their infrastructure is dead without any warning. That's just bad form.

The PAYG Account Mess

This is where things get really confusing.

Oracle's official documentation says: "All tenancies get the first 1,500 OCPU hours and 9,000 GB hours per month for free." Every account type. Including PAYG users who added payment methods.

But then multiple users got emails from Oracle human support agents saying PAYG accounts can still use the original 4 OCPU and 24 GB allowance at no charge. One Reddit commenter posted screenshots of their support response explicitly confirming this.

So which is it?

Oracle hasn't clarified publicly. Users are relying on private support tickets and word-of-mouth. If you're a PAYG user, you're stuck wondering whether you'll get billed for the overage or if you're grandfathered.

And even if you're safe as a PAYG user, there's this lovely buried detail one user highlighted:

"If an existing resource is terminated, it may not be possible to recreate resources above the updated Always Free limit."

Your grandfathered 4/24 instance is one termination away from being locked to 2/12 permanently. That termination could be Oracle maintenance. A data center outage. You accidentally stopping the instance.

Once it's gone, it's gone.

What You Need to Do Right Now

If you're running Oracle Cloud free tier instances, here's your action plan.

Free-only accounts: Audit your Ampere A1 instances today. Calculate your total OCPU and RAM usage across everything. Exceed 2 OCPUs or 12 GB total? Resize or delete instances before August 18, 2026. After that deadline, Oracle stops instances automatically.

PAYG accounts: Contact Oracle Support directly. Chat or ticket. Ask specifically whether your account is exempt from the new limits. Screenshot the support response. But honestly? Consider downsizing anyway since the documentation is all over the place.

Everyone: Back up your data and configurations now. Document your infrastructure setup. Research migration options. And don't rely on "grandfathered" status because it's fragile and Oracle hasn't documented it officially.

The Community Is Not Happy

Developers are furious.

A Hacker News commenter put it well:

"Oracle's way of handling this is the real story. Every cloud provider adjusts free offerings over time, but doing it without a blog post, without an email, and without clear documentation creates exactly the kind of trust erosion that makes developers hesitant to build on a platform."

Reddit threads are packed with migration plans and warnings to avoid Oracle Cloud entirely. The consensus: even if you're not affected yet, Oracle just showed they'll make major changes without notice.

Some users defended Oracle. Hosting thousands of free ARM instances costs real money. Adjustments were probably inevitable. But even those defenders slammed the execution. One longtime Oracle Cloud user noted:

"I get free tiers aren't sustainable forever. But you give people 30 or 60 days notice. You send an email.So don't just update docs and shut things down."

It's become a case study in how to destroy community trust, especially when you're competing with AWS, Azure, and Google Cloud for developer mindshare.

Time to Leave? Here Are Your Options

If you're done with Oracle Cloud—or just want a backup—here are alternatives with their own free or cheap tiers.

AWS Free Tier: 750 hours monthly of t2.micro or t3.Plus instances. Free for 12 months on new accounts. Services like Lambda and DynamoDB have permanent free tiers. More limited than Oracle's old offering but backed by Amazon's reliability.

Google Cloud Platform: e2-micro instance free. $300 credit for new users (90 days). Always Free tier continues after trial. Better documentation and communication than Oracle.

Hetzner Cloud: No free tier, but dirt cheap. Cloud servers start at €4.15/month for 2 vCPU and 4GB RAM. Excellent performance. Straightforward pricing. Popular with European developers and self-hosters.

DigitalOcean: $200 credit for new accounts (60 days). Droplets start at $4/month for 512MB RAM. Simple, predictable pricing. No surprise changes. Strong reputation for developer-friendly policies.

Fly.io: Generous free tier for small apps. 3 shared-cpu VMs with 256MB RAM each. 160GB bandwidth included. Great for Docker-based deployments.

I've used Hetzner for production workloads. Their pricing and performance are solid. No gimmicks.Now sudden policy changes. Just straightforward cloud hosting.

Are Free Tiers Even Sustainable?

Oracle's move raises bigger questions.

Hosting ARM instances with 4 cores and 24GB RAM costs money. Multiply across thousands of users and you're looking at substantial infrastructure spending.

Cloud providers use free tiers as marketing. Get you comfortable with their platform. Build dependencies. Eventually convert you to a paying customer. Oracle clearly decided their conversion rate didn't justify the costs.

But there's a difference between scaling back gradually with communication versus pulling the rug out. The first is business.Still second damages your reputation in developer communities where word spreads fast.

AWS has kept free tier offerings relatively stable for years. Google Cloud has tweaked limits but always with advance notice. Oracle chose a different path.

They're paying for it in community goodwill.

What Oracle Should've Done Instead

Reducing a free tier isn't wrong. But Oracle could've handled this properly:

Announce the change 60-90 days in advance via blog post and direct email to affected accounts. Clearly differentiate between free-only and PAYG account policies in official documentation. Provide migration resources and guidance. Offer a reasonable grace period for downsizing without immediate termination. Grandfather existing instances with explicit documentation.

Instead they updated a docs page and hoped nobody would notice until their instances stopped working.

That's not how you build developer trust in 2026.

Bottom Line

Oracle Cloud's silent free tier reduction isn't just a policy change. It's a trust breach.

Thousands of developers relied on that generous 4 OCPU, 24GB offering for personal projects, learning environments, small production workloads. Now they're scrambling to resize or migrate.

The PAYG account confusion makes it worse. When your official documentation contradicts what support agents tell individual users, you've created a mess that erodes confidence.

If you're using Oracle Cloud free tier, audit your instances now. Don't wait until August 18.

And honestly? Consider whether you want to build on a platform that makes major changes without notice.

For those migrating, you've got options. AWS, Google Cloud, Hetzner, DigitalOcean all have trade-offs, but at least they communicate changes to their users.

Oracle had a chance to differentiate themselves with an industry-leading free tier. Instead they've become a cautionary tale about transparency and communication in cloud services.

What's your experience with Oracle Cloud's free tier changes? Staying or migrating? Drop your thoughts in the comments, and check out our guide on cloud provider comparisons for help choosing your next platform.

Sources

  1. InfoQ - "Oracle Quietly Halves Free Tier Ampere A1 Compute Limits with No Public Announcement" (July 2026) - https://www.infoq.com/news/2026/07/oracle-cloud-free-tier-limits/

  2. Reddit r/oraclecloud - "New Always Free Tier Limits (21-June-2026 Update)" - https://www.reddit.com/r/oraclecloud/comments/1ubk2qy/new_always_free_tier_limits_21june2026_update/

  3. Oracle Cloud Documentation - "Always Free Resources" - https://docs.oracle.com/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm

  4. Terminal Bytes - "Oracle Cloud free tier 2026: 4 OCPU/24GB cut to 2 OCPU/12GB" - https://terminalbytes.com/oracle-cloud-free-tier-changes-2026/

  5. Reddit r/oraclecloud - "New Free Tier Limits (confirmed by oracle support)" - https://www.reddit.com/r/oraclecloud/comments/1u4lzkk/new_free_tier_limits_confirmed_by_oracle_support/

  6. Hacker News - "Oracle cut its Always Free ARM limits to 2 OCPU / 12GB" - https://news.ycombinator.com/item?id=49183750

  7. LowEndTalk Forums - "Oracle Free Tier being reduced" - https://lowendtalk.com/discussion/218183/oracle-free-tier-being-reduced

  8. Full Metal Brackets - "Breaking down the free tier of Oracle Cloud Infrastructure" - https://fullmetalbrackets.com/blog/oci-free-tier-breakdown

Post a Comment