#0001
`Heroku`: traffic spike left a **$1.3k** dyno bill
40radar
HerokuPaaS platform — managed cloud for simple app deploys
Temporary capacity can turn into a real invoice if nobody turns it back down. Without spend alerts, scaling is a cost trap, and support may still say no.
- Traffic from national news led to scaling dynos and workers up, then usage stayed elevated for weeks after the spike ended.
- The overage reached about $1,300 on a site with no revenue, despite already paying
Herokuhundreds per month. - A refund request was rejected, which makes one thing clear: platform goodwill is not a budget control.
- The operational fix is boring but mandatory: billing alerts, post-spike checklists, and auto-scale rollback rules.
Source: news.ycombinator.com/item?id=1688904Read original →