-
-
Notifications
You must be signed in to change notification settings - Fork 791
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High Bandwidth Usage #6223
Comments
This is the mail I sent to Netlify Support:
|
Netlify has forgiven such usage bumps for other projects, so I'm hopeful. But I don't see our usage going down (we typically see lower traffic in December) long-term. For now, I've updated the Credit Card on Netlify, and if the payment goes through, I'll update it on Open Collective. Might be a good time to add more years to our domain renewal. |
Got a reply from Netlify:
|
I'll look at setting up the Edge Rule, but with our current bandwidth usage, the edge function itself might bump our costs. Can you give an estimate - since we don't know our number of requests either. The null-user-agent being 38GB actually makes sense, since we provide an API I'd expect 3% of users to not provide a user-agent while making a call. What I'm curious about is why the powershell usage is so high. Since all of our content is static, it should be well-cached by Netlify, and not result in a bandwidth charge. Maybe we should be setting cache-headers manually since the default headers that Netlify sets seem to be optimized for browser cache via e-tags, which non-browser clients like powershell will just ignore. |
Got another mail today from Netlify that we reached 50% of the current allowance in billing cycle from November 12 to December 12. |
We crossed our 1TB limit on the OSS Plan for October-November billing period (by 300GB), resulting in a 55x3 = $165 charge. Netlify sends me a warning when we cross 75% and 90% bandwidth usage every month, but this was the first time where we blew past.
While our impressions have only gone up by 10-20%, our bandwidth usage has more than doubled over the same period:
The bandwidth usage is only on the primary domain. We haven't had any recent changes to configuration. Everything is static content, which ought to be well-cached, but Netlify clears the cache on each new deploy, but our number of builds/deploys haven't changed at all:
In the absence of logs, it is hard to figure out if we can actually do anything about this bandwidth bump.
I've opened a Support ticket with Netlify for now (319294) to see if we can get a Bandwidth upgrade on our OSS Plan.
The text was updated successfully, but these errors were encountered: