For years, Oracle Cloud Infrastructure (OCI) has offered one of the most generous free cloud hosting plans available. Developers, hobbyists, and self-hosting enthusiasts flocked to Oracle’s Always Free tier because it included a remarkably powerful virtual machine featuring 4 Ampere A1 ARM OCPUs and 24GB of RAMβenough to run websites, VPNs, Docker containers, development environments, and even lightweight Kubernetes clusters at no cost.
That era appears to be over.
Without any public announcement or customer notification, Oracle has cut its Always Free ARM allocation in half. New documentation now lists the free entitlement as 2 OCPUs and 12GB of memory, significantly reducing the resources available under the free plan.
If you’re currently running an ARM virtual machine on Oracle Cloud, it’s worth checking your account immediately.

The New Always Free Limits
Under Oracle’s updated free tier, ARM virtual machines based on the VM.Standard.A1.Flex shape are now limited to:
- 2 Ampere A1 OCPUs
- 12GB RAM
Previously, eligible users could configure an instance with:
- 4 Ampere A1 OCPUs
- 24GB RAM
That configuration has long been one of the biggest reasons developers chose Oracle Cloud over competing free cloud providers.
Anyone still running a 4 OCPU / 24GB instance is now technically exceeding the updated Always Free limits.
Why This Matters
Many users rely on Oracle’s free ARM servers to host:
- Personal websites
- Reverse proxies
- VPN servers
- Home automation platforms
- Docker applications
- Self-hosted services
- Development and testing environments
- Small Kubernetes clusters
Because these workloads often run continuously, many owners may not notice the policy change until Oracle begins enforcing the new limits.
Existing Users Should Resize Their Instances
If your ARM VM is still configured with 4 OCPUs and 24GB RAM, Oracle recommends resizing it to comply with the revised Always Free allocation.
The process is relatively straightforward and usually takes only a few minutes.
From the Oracle Cloud dashboard:
- Open your virtual machine.
- Select Actions.
- Choose More Actions.
- Click Edit.
- Expand the Shape configuration.
- Select the VM.Standard.A1.Flex shape.
- Change the allocation to 2 OCPUs and 12GB RAM.
- Save the configuration.
- Reboot the virtual machine.
Once the server restarts, you can reconnect over SSH and verify that everything is operating normally.
What Happens If You Ignore the Change?
The consequences depend on the type of Oracle Cloud account you have.
Pay-As-You-Go Accounts
Users enrolled in Oracle’s Pay-As-You-Go plan could begin paying for resources that now exceed the revised Always Free limits.
Several users who contacted Oracle support report being told that any usage beyond the new free allocation may eventually become billable.
While Oracle’s pricing calculator has reportedly continued showing $0 for some larger ARM configurations, that may simply reflect a delay in updating billing tools rather than an indication that excess resources will remain free indefinitely.
Free Tier Accounts
Users with accounts that remain entirely within the Free Tier face a different risk.
If Oracle decides to enforce the updated limits automatically, virtual machines exceeding the new allocation could potentially be:
- Suspended
- Stopped
- Reclaimed
- Deleted if resources are needed elsewhere
Although Oracle has not publicly detailed its enforcement timeline, waiting may expose users to unnecessary risk.
Oracle Didn’t Publicly Announce the Change
Perhaps the most controversial aspect of the update isn’t the reduced resourcesβit’s how the change was introduced.
According to numerous community reports, Oracle:
- Sent no customer emails.
- Published no official announcement.
- Issued no prominent blog post.
- Provided no advance warning.
Instead, users discovered the change only after Oracle quietly updated its documentation.
For many customers, especially those running production services, the lack of communication has generated significant frustration.
Be Careful Before Rebooting Your ARM Instance
Ironically, resizing your instance carries its own risk.
Oracle’s ARM infrastructure has frequently experienced capacity shortages in many regions. Users have long reported difficulty creating new Ampere A1 instances because available capacity can disappear quickly.
That means shutting down an existing ARM virtual machine to resize it may not always be risk-free.
In some cases, users worry that after stopping the instance, Oracle may be unable to allocate equivalent ARM resources when the VM restarts.
To reduce that possibility, many experienced Oracle Cloud users recommend upgrading the account to Pay-As-You-Go before making configuration changes. While this does not eliminate capacity issues entirely, it generally lowers the chances of losing access to the instance due to resource availability.
When Will Oracle Begin Enforcing the New Limits?
At the moment, no definitive enforcement date has been announced.
The uncertainty is what concerns many Oracle Cloud users the most.
Some account dashboards and pricing tools have not yet fully reflected the updated policy, leading to speculation that billing enforcement or automated compliance checks may begin later rather than immediately.
Until Oracle provides official clarification, it’s safest to assume the new limits could be enforced at any time.
Oracle’s Generous Free Tier Just Became Much Less Generous
Oracle Cloud’s Always Free ARM offering has been a favorite among developers and self-hosting enthusiasts because it provided far more computing power than most competing free cloud platforms. Offering 4 ARM cores and 24GB of RAM at no cost was exceptionally generous and helped build a loyal community around Oracle Cloud Infrastructure.
Reducing those resources to 2 OCPUs and 12GB RAM may be understandable from a business perspective, but implementing such a significant change without clearly informing customers has left many users frustrated.
If you’re hosting anything on an Oracle ARM instanceβwhether it’s a website, VPN, media server, or development environmentβit’s worth logging into your Oracle Cloud account today. Spending a few minutes verifying your VM configuration now could save you from unexpected charges, service interruptions, or the loss of your server later.
Add Tech2Geek as a preferred source on Google to see more of our latest tech articles.
Support Tech2Geek β€οΈ
Did this guide help you? If Tech2Geek saves you time or helps you solve a problem,
consider buying me a coffee. β
Your support helps keep Tech2Geek independent and free.

Comments