20,000% cost increase in July

[Viktor Bresan]

Hello everyone!

I haven't deployed new versions recently and there is no increase in traffic. But the billing is showing 20,000% cost increase starting from July.

I have contacted the support and they didn't have a clue why it happened. My request was forwarded to technical support a week ago and I haven't received any news regarding this.

It looks like I am not the only one who is reporting the sudden inexplicable cost increase recently.

Any tips or advice?

[jhf555]

Something similar happened to me.  Huge cost increase in mid-June with no new instances deployed and no traffic increase that I can see.  The Billing console shows it as a huge increase in "Frontend Instances".  I have been emailing with support a little bit and they told me there was a big "traffic increase" and that auto-scaling is turning on more instances.  I am trying to figure out from them where they saw this traffic increase because I certainly can't find it (Google Analytics data shows no increase).  I suspect something buggy, or an automatic change in behavior (e.g. some setting).

[Viktor Bresan]

Guys from Google claimed that they didn't change anything. I suspect the scheduling algorithm that launches additional instances has changed. For me the solution was (it was their recommendation) to limit the maximum number of instances and maximum number of idle instances to 1.

[Tapir]

The same for me. 10x more cost increase in Judy and August.

[Viktor Bresan]

My answer here includes details how to limit the number of instances:

https://serverfault.com/a/1073568

[Joshua Turmel]

Thanks Viktor. It's a shame that there's been no real progress/reason given on why this has happened.