Firebase Hosting served 54 GB after I undeployed the site and monthly quota reset — how is this possible?
I’m trying to understand unexpected Firebase Hosting bandwidth usage across two billing cycles and whether anyone else has seen something similar.
During March, my Firebase Hosting downloads suddenly jumped to about 859 GB, which resulted in charges of roughly ₹11,357. The project is still early-stage with very limited real users, so this traffic level doesn’t make sense from normal usage.
As soon as I noticed the spike, I undeployed the site from Firebase Hosting to stop further traffic.
However, after the quota reset on April 1, I saw another 54 GB of downloads recorded within a single day, even though the site had already been undeployed before the reset. I expected usage to drop to zero once hosting content was removed.
That’s the part I can’t explain.
What I’ve checked so far:
- Site was undeployed before the new billing cycle began
- No new deployment was made in April
- Traffic still appeared immediately after quota reset
- This is a static hosting setup (no intentional large asset delivery)
- No marketing campaigns or traffic spikes occurred
- Real user traffic is minimal
So my current guesses are:
- cached CDN edge responses still being served globally
- asset hotlinking from another site
- bots repeatedly requesting previously indexed URLs
- some Firebase Hosting behavior I don’t fully understand yet
Has anyone seen bandwidth continue after undeploy + monthly reset like this?
Is there a way to identify which files were downloaded from Hosting logs?
And is CDN cache delivery counted toward Hosting bandwidth even after removal?
I’ve already contacted Firebase support, but I’m trying to understand whether this is a known pattern or something unusual with my setup.
Any insights would really help.
