The advice you see everywhere for keeping an Oracle Always Free instance alive is to point a cron job at it — hit it once a day and it counts as activity. I went and read Oracle's own Always Free documentation, and that isn't how the rule works.
Oracle deems a compute instance idle only if, across a 7-day period, all three of these are true at once:
- CPU utilization at the 95th percentile is below 20%
- network utilization is below 20%
- memory utilization is below 20% — this one applies to A1 shapes only
A once-a-day HTTP request does essentially nothing to a 95th-percentile CPU figure. That statistic asks what your CPU was doing during the busiest 5% of the window, and a handful of requests spread across seven days doesn't register. So the ping trick can leave you fully inside the idle definition while feeling like you've solved it.
The useful half of the rule is the word all. Because every condition has to hold for the instance to count as idle, clearing any single one keeps you out. On a 12 GB A1 the memory threshold is usually the easiest to stay above without trying: anything genuinely resident — a Docker stack, a database, a password manager — holds memory above 20% continuously, no cron job required.
So the honest version is that you don't keep the box by pinging it. You keep it by actually running something on it.
Full current Always Free numbers, including what the June 2026 halving changed: https://toolfreebie.com/oracle-free-arm-vps/
