> In this position my first step would be to determine if there's any legal basis for disputing the charge
Let's calm down.
The first step is to pay the bill, set up better infrastructure monitoring on your end, so you don't act surprised that you are consuming 7000% more resources than third party service is reporting.
Then, if you want to burn some money, you can file a petition and tell the court that you deserve to get free service because you did not know that you have been going over the reported data by 50%, I mean 7000% for... two years.
As far as I understood, Firebase didn't report it before. As mentioned, the meter "suddenly jumped" to 100GB and then 180GB (if I remember the numbers correctly).
The author decided to figure it out with support later, which makes sense if the previous number was something like 20-30GB and you guess it's simply in error.
Let's calm down.
The first step is to pay the bill, set up better infrastructure monitoring on your end, so you don't act surprised that you are consuming 7000% more resources than third party service is reporting.
Then, if you want to burn some money, you can file a petition and tell the court that you deserve to get free service because you did not know that you have been going over the reported data by 50%, I mean 7000% for... two years.