Of the shared address pool? Not publicly, but folks are clever. Hazard of making tools for other devs, I guess. In some regions things are stable enough that folks noticed that all Hyperdrive connections were coming in from a small number of addresses, and eventually just coded that into their firewall rules.
Hey thanks for reply on this. Yes when I try to setup hyperdrive + a managed DO database in cf dashboard it errors
I have setup connections with supabase in the past successfully and I searched this channel for issues with DO leading me to believe it’s with DO ip range?
Interesting. I searched and you're right, TCP connect from workers to DO seems to have some issues.
I'm not sure if it's due to the shared address range or not, though.
I'll check Monday with my teammate who's working on the migration to the CF IP ranges and see if we have a way to test if DO cooperates with those. I'd be curious to know, honestly
I want to hide my database behind Cloudflare's Network without needing to have the CloudflaredCloudflared application on all devices.. Is that what Hyperdrive fixes?
Hyperdrive is a way to talk from Workers to a centralized database. We integrate with tunnels too so you'd only need have cloudflared running once somewhere within your vpc to egress the traffic to your DB from.
Based on your questions I'm assuming you're not running your application on Workers?
Are there any plans for supporting custom connection limits per region? Right now we seem to be hitting that limit and losing performance by being routed to a nearby region.
Hello~ I was reading about hyperdrive, and wanted to confirm something: is hyperdrive ONLY for accessing a database from workers, or can it be used for connecting from other type of distributed applications (that aren't hosted on Cloudflare?).
I assume the answer is "nope, sorry!", since it looks like Hyperdrive operates as a worker binding, but just want to confirm.
Yes, that is correct. We've kicked around opening it up more, but have not committed to that yet. Hyperdrive operates as a standalone service, so it is technically possible, though would take some work.
If you're willing to discuss your use case a bit, it'd help us as we evaluate.
@AJR Hmm, I think I may have found a pretty bad bug. When you reconnect, are you doing a fresh DNS lookup, or are you maybe accidentally using a cached entry?