Oracle Cuts Free Tier Cloud Capacity in Half with Silent Update

Oracle has silently slashed the Always Free tier allowances on its cloud platform, cutting available processing power and memory in half starting June 15, 2026. The company reduced allocations from 4 OCPUs and 24 GB of RAM to 2 OCPUs and 12 GB of RAM—a move that affects a sizable community of developers, home lab operators, and small-scale AI inference users who depend on the service.

How the Change Unfolded#

Rather than alerting customers through the typical channels, Oracle simply updated its documentation without fanfare. Community members first encountered the limits when their running instances were terminated or when the documentation changes were spotted. The company issued no blog announcement, sent no email notifications, and made no formal public statement.

The timing created immediate confusion about billing impacts. Pay-As-You-Go (PAYG) account holders who had upgraded for easier instance provisioning but still relied on Always Free resources faced uncertainty: would their existing 4 OCPU instances suddenly begin incurring charges? Free-only accounts faced a clearer outcome—instances exceeding the new limits were simply shut down until manually reconfigured.

The Gradual Clarification#

On June 22, a week after the change took effect, multiple PAYG users received emails from Oracle support agents confirming that the new restrictions apply only to free-tier accounts. However, as of now, Oracle has offered no public clarification. The official documentation remains ambiguous, stating "all tenancies" receive the reduced allocation—language that would typically include PAYG customers—creating a stark contradiction with what support agents are reportedly telling individual users.

The lack of clarity has forced developers to rely on screenshots of support emails rather than official policy documentation.

The Real Risk: Grandfathering Uncertainty#

Existing instances may retain their original 4 OCPU and 24 GB configuration, but this protection carries a significant catch. Oracle's documentation includes a caveat: "If an existing resource is terminated, it may not be possible to recreate resources above the updated Always Free limit." Since instances terminate routinely due to platform maintenance, outages, or user error, any existing workload remains one incident away from permanent downgrade to the new, lower caps.