Storage
Hyperdrive review
Score: 8/10Makes an existing database fast from Workers, and does it well.
The breakdown explains the score. It is not an average. How to read these.
Last updated
Hyperdrive makes it practical to use a traditional Postgres or MySQL database from Workers. It pools connections close to the database and can cache queries, so each invocation does not pay to set up a connection across an ocean.
Setup takes minutes: give it a connection string and swap in the binding. Read-heavy workloads can see an immediate latency improvement. Including it with paid Workers plans removed the last reason to hesitate.
Points off only for opacity: you get limited visibility into pool behavior, cache hit rates, and where your pool is actually placed, and the config surface is minimal when you want to tune. But as the bridge between “we have a real database” and “we want to build on Workers,” it’s exactly the product it should be.
Status page incidents
Published under Hyperdrive, plus incidents whose title names it.
- Last 2 years
- 10
- 2 from the title
- Major or critical
- 0
- Median time open
- 3.8 h
- Since April 2024
- 10
Counts what Cloudflare published, not what broke: time open is how long the status entry stayed open, and nothing before April 2024 is tracked at all. Incidents Cloudflare tagged against nothing but named in the title are counted too. The caveats in full.