Heroku Eco Dyno Sleeping / Slow First Load

How to fix it

Try these in order — the most common fix is first.

1. 1. Upgrade to Basic or Standard

   Copy steps
   1. Run heroku ps:type basic -a <app> (Basic is $7/month, always on)
   2. Or heroku ps:type standard-1x for $25/month
   Did this fix it? Yes No

2. 2. Speed up the wake-up

   1. Reduce startup work and slug size so the dyno boots faster
   Did this fix it? Yes No

3. 3. Check your hour pool

   Copy steps
   1. Open dashboard billing and see Eco dyno hours used
   2. H82 means the pool is exhausted until reset
   Did this fix it? Yes No

4. 4. Consider other hosts

   1. Render, Railway and Fly.io are common alternatives if you want a cheaper always-on hobby app
   Did this fix it? Yes No

Symptoms

First visit after idle time is very slow or times out; later requests are fast. H82 appears if the shared Eco hour pool is used up.

Why it happens

• Eco dyno sleeps after 30 minutes of inactivity
• Eco hours (1,000/month) are shared across all Eco apps on the account
• Cold start plus slow boot

This guide also covers

• heroku dyno sleeping
• heroku eco dyno sleep
• heroku app slow first load
• heroku h82

The same problem in other apps

All not loading, error messages & connection guides →

• DigitalOcean Droplet SSH Connection Refused or Timed Out (DigitalOcean)
• Vercel FUNCTION_INVOCATION_TIMEOUT (504) Error (Vercel)

Other Heroku errors

• Heroku H10 App Crashed Error
• Heroku H12 Request Timeout Error
• Heroku R14 Memory Quota Exceeded Error
• Heroku Application Error Page
• Heroku Build Failed Error
• Heroku Git Push Rejected / Remote Rejected
• Heroku H14 No Web Dynos Running
• Heroku R10 Boot Timeout / H20 App Boot Timeout