Massive egress showing in usage
I just got an email showing a massive increase in usage costs for one of my apps. On the Usage page it's showing >400GB total egress so far this month. My Cloudflare dashboard for this site only shows 13GB of transfer, so I don't know where the other 387GB of egress is going.
Project ID: 9d59e9da-a468-48cd-a457-2e53813fe7f3
(Reposted because Percy closed previous thread)
13 Replies
Project ID:
9d59e9da-a468-48cd-a457-2e53813fe7f3That's very odd. Are you sending requests outside of Cloudflare? (apologies if that's a stupid question, I've never actually used CF as a proxy)
All requests go through CF (not a stupid question :)). Only thing I can think is that I've written 387GB of traces to Honeycomb, but that seems unlikely.
Honeycomb isn't showing that many traces, that's for sure
Hmm. Odd.
Thread has been flagged to Railway team by @aleks.
Maybe you have a legacy database (those created as plugins) and all the communication is going through public endpoints, which produce egress
No additional services at all, it's a self-contained app
CF's transfer stats on their site dashboard is only for inbound, i.e. requests made to your app. Outbound is any request you're making from your app.
Can you share more about what your service does and how you're using CF?
The service is https://www.fretbadger.com - it basically generates static HTML pages showing various scales and arpeggios on bass/guitar/ukulele fretboards. Each page is ~50K, and I'm not getting the kind of traffic that would cause 400GB of egress. The only outbound calls from my app are OpenTelemetry items being written to Honeycomb, and very occasional calls to GitHub for the feedback page.
My traffic is roughly the same as it was last month, when my Usage-based bill was £3. It's currently showing $42 for this month, with estimated $61.
That's cool! I might use it.
Thanks @aleks
Do you know how much bandwidth otel->honeycomb is consuming?
Sorry this is kinda hard to debug for us without additional info; we can't trace all of your network calls and give you a list of what you've been making, and we haven't had any reports about wildly inaccurate egress billing that isn't due to public/private networking w/ databases or other services within Railway
We fixed a bug on egress billing recently, so you weren't previously charged for the amount of bandwidth you were sending accurately
@ray Yeah, I appreciate it's difficult to diagnose this kind of thing. I've definitely eliminated Honeycomb as the culprit, nowhere near enough traces to hit 100s of GB.