oracle cloud recently announced an official update to its free-tier policy, stating that starting june 15, 2026, the permanently free arm‑based plan for global users will see a significant reduction in resource allocations: the number of ocpu cores will be cut from 4 to 2, and memory capacity will be reduced from 24 gb to 12 gb. this adjustment applies not only to new users but also to all existing instances—regardless of whether they have been deployed or are currently active. once cumulative resource usage exceeds the new limits, the system will automatically terminate the affected instances. for pay-as-you-go users who continue using their previous high‑spec configurations, any resources exceeding the new thresholds will be billed at standard rates, with no further free quota.
the specific changes are as follows:
- redefined total free quota
under the old rules, users could flexibly allocate up to 4 ocpu cores and 24 gb of memory (e.g., running two instances each with 2 cores and 12 gb). the new policy uniformly caps the total allocation at no more than 2 ocpu cores and 12 gb of memory, applicable across all arm instances under a single account.
- clear restriction on applicable instance types
the adjustment affects only arm instances powered by ampere altra processors (i.e., the a1 series). free instances based on amd architectures remain unchanged, still offering 1 ocpu core and 1 gb of memory.
- clearly marked effective date
starting at midnight on june 15, 2026, the free‑quota dashboard for all accounts will reflect the updated values. any instances created prior to this date that exceed the new limits will trigger a resource check on that day, resulting in automatic downgrading or shutdown.
key impacts on users and recommended actions:
- existing free users must act immediately
if your current arm instances collectively exceed the 2‑core/12‑gb threshold, the system will automatically shut them down once the effective date arrives. it is strongly advised to back up your data and proactively scale down to compliant specifications before the deadline to avoid service interruptions, unavailability, and potential data loss.
- pay‑as‑you‑go users should also take note
even if you’ve upgraded to a paid account, continuing to use your original free‑tier configuration (e.g., 4 cores and 24 gb) will result in charges for any resources exceeding the new limits. failure to adjust promptly may lead to unexpected billing spikes, and prolonged non‑compliance could even result in account suspension or termination of services.
analysis of the policy change’s underlying drivers:
oracle has long differentiated itself by offering “high‑spec free arm instances along with complimentary ipv4 addresses” to attract developers. however, as global user numbers surge and regional resources face mounting pressure—manifesting in issues such as quota exhaustion, restrictions on cross‑region registrations, and tightened account‑level controls—the underlying infrastructure is clearly approaching its capacity limits. while this reduction in instance specifications weakens individual performance (theoretical compute power dropping by approximately 50%), it still maintains strong practical utility within the free cloud‑service framework. by adopting a rational perspective and promptly adapting to these new guidelines, users can ensure the continued stability and availability of their development and testing environments.
