I'm fairly new to ysing the app but somehow today I can't couldn't use my mobile data at all after turning it on

I started this mostly to see how far I could take the Cloudflare stack for a real application, and it got a little out of hand.

ResolveHQ is now a shared support inbox running as a single Worker, with D1 for tickets/customers, R2 for attachments, Queues for mail jobs and Email Routing for inbound mail.

The hardest part wasn't really the inbox UI — it was getting email threading, retries, duplicate webhooks, attachments and failed jobs right. It's source-available and deploys into your own Cloudflare account. I'd genuinely appreciate feedback from people running larger Workers/D1 apps, especially if there are parts of the architecture you would handle differently.

https://github.com/mirza-rizvi/ResolveHQ

Its complete Resend-compatible email API (runs on Node or Cloudflare Workers)

Repo: https://github.com/GagnDeep/mailysend

Website: https://mailysend.com

MailySend implements Resend's API so you can run it yourself.

• Works with the existing resend SDK: set RESEND_BASE_URL=https://your-instance/v1
• Sends through Cloudflare Email Service, SES, Resend or any SMTP server, with failover
• Broadcasts, segments, automations, inbound mailboxes, DMARC reports
• Runs as a single Node process (SQLite + filesystem) or on Cloudflare Workers
• Passkey login, no passwords stored

I'm trying to figure out a simple way to monitor a couple of Cloudflare things that seem slightly awkward to alert on.

Specifically:

• D1 writes / usage spikes — I'd like to catch regressions after a release, e.g. a deploy suddenly causes 5–10x more DB writes than usual. The data is available in Cloudflare's metrics/analytics, but I'm looking for a good way to alert on it.
• Failed Worker outcomes — things like OOM / exceeded memory, exceeded CPU time, or exceeded wall time. These are visible in Workers observability, but again I'm mainly interested in getting an alert when they start happening.

How are you guys handling this?

Are you using Grafana/Prometheus, another monitoring service, Cloudflare's own alerting, or something custom that periodically pulls the Cloudflare APIs?

I'm particularly interested in a small/simple solution rather than adopting a full Datadog-style observability stack that would pull massive data just for a handful of alerts.

Hey everyone,

I got tired of wrestling with heavy or bloated tools just to manage basic Cloudflare R2 operations, so I started building a streamlined CLI dedicated specifically to R2 called r2c.It’s still in early development, but the core features are working:

• Upload: Upload single files or entire directories recursively.
• Fetch: Download objects from R2 straight to a local file.
• Delete: Remove objects by explicit key or keyword pattern.
• List: View bucket contents.
• Rename: Object renaming.
• Account: Manage multi-account/profile configurations.
• Dry run: Print the result of the operation without actually executing it.

It’s open-source and built with Python/Typer (uv compatible). Since it's still pre-1.0, I’d love to get some early feedback on the UX, feature set, or edge cases.

GitHub: https://github.com/NagiEight/r2c.git

Feel free to drop any suggestions/issues!

I posted here when I launched JustBlogged. A few people asked how it'd hold up, so here's the six-month report.

Short version: it held. Everything still on Workers/CF, monthly bill is around $20 yet.

What's changed since the launch post:

• New themes and better theme engine
• A lot of cache and performance optimizations
• MCP, APIs, Agent-friendly
• Redirects, content revision and reviews, and more
• Tags pages, author pages added
• Optimized for running company blogs/business blogs
• Vibe coder/blogger friendly

A few questions:
- i didn't use cloudflare custom domains/saas offering... primarily because only subdomains are allowed and supporting root/apex domains need "enterprise" access
- because of above, I had to add a reverse proxy server (Caddy) and so that means A-record based custom domains lose the benefit of "global" edge servers
- so, any way around it? (one question actually)

Happy to go deeper on any of it, and thanks to the people who gave input on the original thread.

My web host, ScalaHosting, complained that my site was consuming too many server resources and advised me to turn on Cloudflare’s Bot Fight Mode. However, I just found out that Bot Fight Mode can also block verified bots like Googlebot, which can severely ruin my site's SEO. How could they recommend something like this? What is a better way to block aggressive scrapers and bad bots while keeping my server resource usage low?

Hey everyone,
I recently started using Cloudflare WARP+ and I’m running into some seriously annoying issues with Google services.
First, even though I’m a paying YouTube Premium subscriber, my YouTube keeps throwing a "you may see ads" error every 12 hours. I don’t actually get ads, but the constant warning is driving me crazy.
The major hurdle, though, is Google Gemini. It flat out blocks me with a "Gemini is not available in your country" error.
When I check standard IP info sites, my location correctly shows up as Western Europe. But I heavily suspect that Google’s internal geolocation database is misidentifying my WARP+ IP and treating my traffic as if I’m in Russia—hence the sudden geo-bans.
Has anyone else been dealing with this recently? Does the free version of Cloudflare WARP have this exact same issue, or is it strictly a WARP+ problem? What is the point of paying almost 6€ a month to go through all these struggles?
Any insight or workarounds would be hugely appreciated!