Cloudflare status: hosting issues and outage reports
No problems detected
If you are having issues, please submit a report below.
Cloudflare is a company that provides DDoS mitigation, content delivery network (CDN) services, security and distributed DNS services. Cloudflare's services sit between the visitor and the Cloudflare user's hosting provider, acting as a reverse proxy for websites.
Problems in the last 24 hours
The graph below depicts the number of Cloudflare reports received over the last 24 hours by time of day. When the number of reports exceeds the baseline, represented by the red line, an outage is determined.
At the moment, we haven't detected any problems at Cloudflare. Are you experiencing issues or an outage? Leave a message in the comments section!
Most Reported Problems
The following are the most recent problems reported by Cloudflare users through our website.
- Cloud Services (57%)
- Hosting (29%)
- E-mail (7%)
- Domains (7%)
Live Outage Map
The most recent Cloudflare outage reports came from the following cities:
| City | Problem Type | Report Time |
|---|---|---|
|
|
Cloud Services | 4 days ago |
|
|
Cloud Services | 8 days ago |
|
|
12 days ago | |
|
|
Hosting | 13 days ago |
|
|
Cloud Services | 18 days ago |
|
|
Cloud Services | 20 days ago |
Community Discussion
Tips? Frustrations? Share them here. Useful comments include a description of the problem, city and postal code.
Beware of "support numbers" or "recovery" accounts that might be posted below. Make sure to report and downvote those comments. Avoid posting your personal information.
Cloudflare Issues Reports
Latest outage, problems and issue reports in social media:
-
Ozmium (@ozonchain) reported@kennyistyping A lot is pick-and-choose too, but it's been incredibly useful for me personally at least to see and fix areas of the Ozmium front-end and back-end to make it so AI Agents and Humans basically have 100% equal footing on what they can do through the app/domain. I've even used it on some other side non-blockchain things that I realized would greatly benefit from being fully agent-ready (e.g., I run an economic development map to help IRL builders find serious community funding and site selection, data export for all the paperwork data requirements to get the funding, etc.) I've always been a bit biased to Cloudflare because their free plan lets you do so much.
-
Carlo GG (@CarloDotGG) reported@SimonHoiberg Easy fix Step 1: Use Cloudflare AI Gateway to build your own custom Openrouter for your business, then select whichever provider you'd like, or even attach custom providers like BaseTen, FAL .... Step 2: set billing limits per user if needed.
-
DeathScythe (@DeathScytheH) reported@BowTiedWaterDog @BowTiedCrocodil Netbird self hosted. Zero trust network wireguard based with βcloudflare tunnelsβ.
-
Muntasir Mallik (@muntaxir04) reported@acolombiadev @Cloudflare Maybe it's Gemini? We never run out of searches bec nobody uses it anymore
-
Brij Pandey (@LearnWithBrij) reportedπ SaaS Stack β β£ π Frontend β β£ π React β β£ π NextJS β β£ π Vue β β£ π TailwindCSS β β π Shadcn UI β β£ π Backend β β£ π NodeJS β β£ π Django β β£ π Laravel β β£ π FastAPI β β π Express β β£ π Database β β£ π PostgreSQL β β£ π MySQL β β£ π MongoDB β β£ π Redis β β π Supabase β β£ π Auth β β£ π Clerk β β£ π Auth0 β β£ π Firebase Auth β β£ π Supabase Auth β β π NextAuth β β£ π Payments β β£ π Stripe β β£ π Paddle β β£ π Dodo Payments β β£ π Lemon Squeezy β β π Polar β β£ π Emails β β£ π Resend β β£ π SendGrid β β£ π Mailgun β β£ π Postmark β β π Amazon SES β β£ π Storage β β£ π AWS β β£ π Cloudflare β β£ π Google Cloud Storage β β£ π Supabase Storage β β π Uploadcare β β£ π Deployment β β£ π Vercel β β£ π Netlify β β£ π Railway β β£ π Render β β π AWS β β£ π Domains and DNS β β£ π Namecheap β β£ π Hostinger β β£ π Cloudflare DNS β β£ π Google Domains β β π SiteGround β β£ π Analytics β β£ π Google Analytics β β£ π Plausible β β£ π PostHog β β£ π Mixpanel β β π DataFast β β£ π Monitoring β β£ π Sentry β β£ π LogRocket β β£ π Datadog β β£ π NewRelic β β π UptimeRobot β β£ π DevOps β β£ π Docker β β£ π Kubernetes β β£ π GitHub Actions β β£ π CI CD β β π Terraform β β£ π Search β β£ π Algolia β β£ π Meilisearch β β£ π Elasticsearch β β£ π Typesense β β π OpenSearch β β£ π AI Integration β β£ π OpenAI API β β£ π Anthropic API β β£ π Replicate β β£ π HuggingFace β β π Gemini API β β£ π Integrations β β£ π Zapier β β£ π Make β β£ π n8n β β£ π Pabbly β β π Webhooks β β£ π Security β β£ π SSL β β£ π Cloudflare β β£ π WAF β β£ π Rate Limiting β β π Secrets Management β β£ π Marketing β β£ π Search Console β β£ π Outrank β β£ π Buffer β β£ π Analytics β β π Kit β β π Customer Support β£ π Intercom β£ π Crisp β£ π Zendesk β£ π Tawk β π HelpScout
-
Reina Cruz π₯Όπ§€π¨πΊ (@rea1ReinaCruz) reported@Cloudflare Fix human verification
-
robot 2.0 (@alightinastorm) reported2 weeks of prompting can build this now, in the browser, no platform fees, no pre-downloading gigabytes, stream as you play is it AAA? no is it low poly slop? no can you build real games with it? you absolutely can stop inventing bullshit about distribution, what distribution do you get from steam? ZERO, that's why you hire marketers to run guerilla campaigns on social media, streamers to hype it up and backdoor some cash to youtubers to pump it on release week You can do the same for the web, your likes and followers on X are your wishlist Pay stripe 3% instead of 30%, throw a couple $$ to cloudflare for traffic Or keep betting on steam and die a slow painful corporate death
-
Noel Ceta (@noelcetaSEO) reported8/ Layer 5: CDN implementation (distribute content): CDN = Content Delivery Network How it works: - Content stored on multiple servers worldwide - User gets content from nearest server - Fast delivery regardless of geography Setup: - Cloudflare (easiest, free tier available) - Akamai (enterprise) - CloudFront (AWS) Impact: 20-40% speed improvement for global sites.
-
Girish (@spectragai) reported@UthaaleReDeva @acolombiadev @Cloudflare It serves different purposes. But Iβm just answering the post: name a generous free tier service
-
π₯π΄ββ οΈCyberTechWolfπ΄ββ οΈπ₯ (@CyberTechWolff) reported@ChaoticTKnight I'm gonna laugh if Cloudflare gets DDOSed or some **** because they wanna claim the Internet. Not everyone has to be hijacked by Cloudflare and I hope someone hacks their ******* **** I don't use these words a lot but the Internet might just have robophobia.
-
Lex (@TheLexTimes) reportedHey @Cloudflare I reached out via DM about WARP constantly disconnecting. Is there a direct contact I can talk to? Happy to provide any data to help figure this issue out.
-
James (@jamescoder12) reportedThe full impact. What he changed and what happened: 1. Moved router from cabinet to open shelf: 74 Mbps β 155 Mbps 2. Changed Wi-Fi channel to least congested: 155 Mbps β 290 Mbps 3. Widened channel width to 80 MHz: 290 Mbps β 380 Mbps 4. Switched DNS to Cloudflare (1.1.1.1): browsing latency dropped noticeably on every device 5. Updated firmware (first time in 4 years): 380 Mbps β 400 Mbps + eliminated smart TV disconnections 6. Changed admin password + upgraded to WPA3: closed the 2 biggest security holes in the network 7. Separated 2.4 GHz and 5 GHz bands: eliminated TV buffering caused by band steering 8. Enabled QoS (work laptop prioritized): zero Zoom call drops during peak household usage 9. Bought own router, returned ISP rental: $168/year saved + full control over all settings Starting speed: 74 Mbps (on a 500 Mbps plan getting 15% of what he paid for) Ending speed: 440 Mbps (getting 88% of what he paid for) Then the real move: he downgraded from the 500 Mbps plan back to 200 Mbps because 200 Mbps with optimized settings delivered faster Wi-Fi to his devices than 500 Mbps with factory defaults. Monthly savings from the plan downgrade: $30 Monthly savings from returning the rental: $14 Total annual savings: $528 with faster, more stable, more secure internet Total time to make all 9 changes: 15 minutes of settings + one trip to Best Buy + one phone call to return the rental.
-
Atif (@ioAtif) reported@acolombiadev @Cloudflare @coderhq Although it's not a service but a whole platform
-
William Bello (@belljobs94) reportedTHE GOAT on their free service !! @Cloudflare hands down
-
SoccerGuy (@SoccerGuyUS) reported@levelsio @Cloudflare Namecheap is awful. Anyone looking for a better Google Domains (since they rug pulled) alternative: Porkbun.
-
chosem π (@chosem_) reported@synopsi use cloudflare receive and sending. connect receive to an openrouter API, basically most modern AI will do, even cheaper ones. make it categorize: promotion, support, misc. and then route the support to your actual support platform so you can see it all in one place.
-
Miget (@miget_com) reportedThen you reach it from outside. Four terminators, and you can run more than one on the same network. WireGuard per person or per machine. Tailscale into a tailnet you already run. Cloudflare WARP into a Cloudflare org. IPsec site-to-site.
-
Tang Vu (@tangvu_dev) reportedI compared Cloudflare Workers and Vercel Edge Functions, two production platforms built on V8 isolates, using a latency-sensitive crypto analytics service. The workload fetched prices and computed OHLC + VWAP over 24 kline periods.
-
Nuvorlane (@nuvorlane) reportedCloudflare AI Gateway monthly usage invoices no longer break out input and output tokens. Previously you got two lines, e.g. 40k input at $0.000001 ($0.04) and 24k output at $0.000005 ($0.12). Now one line: anthropic/claude-haiku-4.5 β $0.16. Model names on invoices and logs also normalize to provider/model, so dated suffixes disappear from the identifier. Credit-purchase invoices are unchanged. If a FinOps parser keys on token line items or version suffixes, fix it before the next month-start invoice lands.
-
Reina Cruz π₯Όπ§€π¨πΊ (@rea1ReinaCruz) reported@Cloudflare Fix human verification
-
My1 (@nep.one - Misskey) (@My1xT) reported@slendidev interesting question would be how fast or slow cloudflare runs on those, as especially on my older laptop it sometimes took a decent while, before needing a click and taking a decent while again, while anubis you dont need to babysit.
-
βοΈ Daddio βοΈ (@ScienceDaddio) reported@grok @DaddioAI E4H.1 is implemented. The pump-activity table is now the reusable presentation surface; events are optional overlays, not duplicate source tables. Raw duration rows stay immutable. E4G.6B canonical stable-ID work is intact (trend_report.html, trend_report.js, test/trend-report-stable-id-e4g6b.test.js). The workspace is not a *** repo, so that was confirmed by file inspection, not *** status. Codex had only started reading; no detector or research files were rewritten. βββ 1. Working-tree inspection No *** repo. Inspected files vs the E4G.6B baseline. E4H.1 presentation files were already present from the interrupted session. This closeout preserved that work, then stopped overlaying Current Assembly / Station Packet tables so automatic assembly still uses detector is_event_row highlighting instead of the new ERT overlay. 2. Distinction from E4G.6B E4G.6B remains: stable IDs and trend_report.js?v=e4h1-e4g6a-e4g6b. E4H.1 added presentation state, ERT overlay, settings UI, and Search Tables controls. Research under research/e4c8g/ was not touched. 3. Existing table architecture found Canonical BossDataTable renders Trend Report, Search Tables, and exports. Manual/Search tables use the approved catalog with exact start/end, pump, and sort. Event tables keep Context Before/After. Snapshots store source columns/rows; presentation is a separate optional field. EMAIL-v1 already highlights via is_event_row. 4. Existing fixed ERT architecture ββββββββββββββββββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββββββββββ¬ββββββββββββββββββββββ β Layer β Behavior β E4H.1 action β ββββββββββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββΌββββββββββββββββββββββ€ β Python PumpDurationERT / β Materialized at ERT_MINUTES = 15, β Preserved β β PumpActivityERT β RUN_TIME β₯ β β ββββββββββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββΌββββββββββββββββββββββ€ β detectFixedErt() β Exists; not called from β Preserved β β β detectEvents() β β ββββββββββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββΌββββββββββββββββββββββ€ β Settings fixedErtEnabled / β Default enabled, 900 seconds β Reused as overlay β β fixedErtSeconds β β config β ββββββββββββββββββββββββββββββββββββββββΌβββββββββββββββββββββββββββββββββββββββΌββββββββββββββββββββββ€ β Historical FIXED_ERT Station Events β Readable history β Preserved β ββββββββββββββββββββββββββββββββββββββββ΄βββββββββββββββββββββββββββββββββββββββ΄ββββββββββββββββββββββ 5. Existing Adaptive Long Runtime architecture detectAdaptiveRuntime() remains in detectEvents(). Station Events, Current Assembly, and report generation still consume Adaptive events. No silent detector swap. 6. Settings architecture Existing analysis settings: global row + per-station overrides in analysis-settings.js, Station Review cards, PUT /api/station-review/settings/global and station override PUT. No parallel settings universe. 7. ERT setting storage Existing columns: β’ fixed_ert_enabled (boolean, default true) β’ fixed_ert_seconds (number, default 900) Read-only reshape: GET /api/pump-activity/ert-settings β { default_enabled, default_threshold_seconds, stations: { [id]: { enabled, threshold_seconds } } }. Writes go through the existing Station Review settings APIs. No new write endpoint. 8. ERT defaults 15 minutes (900 seconds) when no station override exists. Sands is not hardcoded. 9. Threshold semantics Granular rows only: RUN_SECONDS >= station.threshold_seconds Annotation metadata records comparison: 'gte'. Equality counts (6:00 at a 6-minute threshold is ERT; 5:59 is not). Validation range: finite, 1 to 2,592,000 seconds (1 second through 30 days). That is the existing analysis-settings bound. UI is minutes: 0.0167β43,200, converted Γ 60 on save. Allowed values include 6, 10, 15, 17, 20, 30 minutes. Invalid overlay input clamps to 900 seconds; settings save still rejects out-of-range values. 10. Shared table presentation model Fields actually implemented: β’ context β SEARCH \| TREND_EVENT \| TREND_MANUAL β’ start / end β’ pump β '' \| PUMP-1 \| PUMP-2 β’ row_mode β ALL_ACTIVITY \| EVENTS_ONLY β’ event_display β NONE \| ALL \| EXTENDED_RUNTIME \| CONSECUTIVE_SAME_PUMP β’ enabled_event_types β’ highlight_enabled β’ consecutive_available β’ ert_settings (optional snapshot of thresholds) 11. Annotation provider model src/public/pump-activity-presentation.js (BossPumpActivityPresentation): β’ ERT provider: derived from row runtime + per-station threshold β’ Consecutive provider: persisted evidence only (event_source_keys / source_key / is_event_row fallback) β’ 0βN annotations per row, keyed by sourceIdentity, not DOM index 12. Raw data integrity applyPresentation clones rows. Source objects are not mutated. Annotations are not written into duration history. Tests stringify the source array before and after. 13. Trend Report integration User-inserted granular tables get a collapsed Table Display card: Start, End, Pump, Rows, Events, Highlight Events, Apply. Event-from-tray tables default All Events + Highlight ON. Manual/Search-style inserts default None + Highlight OFF. Apply updates the same Canvas section (no duplicate). Context Before/After still exist; once they produce a new window, annotations follow that window. Current Assembly and Station Packet tables do not attach overlay presentation and do not show Table Display. They keep detector is_event_row highlighting. 14. Search Tables integration Granular duration tables (pump_runs, pump_durations, PumpDurationERT, rolling48_all, *_durations) show Rows / Events / Highlight. Defaults: Events: None, Highlight: Off, All Pump Activity. Consecutive is not offered. Aggregate tables (PumpActivityDaily, PumpActivitySQL, PumpActivityERT, StationActivityDaily) stay plain with the bar hidden. 15. Generate Report / aggregate handling Generate Report was not merged or redesigned. PumpActivityDaily MAX above threshold is not treated as a granular ERT event (aggregate: true, no Event column). 16. Time-range recalculation Annotations are computed from the tableβs current start/end. Expand the window β newly visible ERT rows annotate. Contract β out-of-range annotations disappear. The table is not married to the initiating event. 17. Row modes β’ ALL_ACTIVITY β all qualifying source rows; annotated rows carry labels when highlight is on β’ EVENTS_ONLY β only rows with currently enabled annotations β’ EVENTS_PLUS_CONTEXT was not built event_display = NONE forces ALL_ACTIVITY. 18. Highlight toggle / plain mode Highlight OFF (or Events = None): no event-row class, no Event column, no event_labels / event_annotations, no threshold text in the row payload. Same source rows, visually plain. 19. Pump filter Both / Pump 1 / Pump 2 preserved. Annotations follow remaining rows. 20. Sorting Existing newest/oldest/runtime sorts remain. Highlight class uses sourceIdentity, not row index. 21. Multi-station threshold behavior Each row uses that rowβs station config. Example: Sands 6 minutes + Magnolia 20 minutes β a 10-minute Sands row is ERT; the same duration at Magnolia is not. 22. Multiple-annotation support One row can show EXTENDED RUNTIME Β· CONSECUTIVE. Structure is a list, not one-event-per-row. 23. Consecutive compatibility Now: Trend Report event tables may show persisted Consecutive annotations when source keys or is_event_row evidence exists. Deferred: no detectConsecutiveRuns() changes, no LG30/C1, no historical reconstruction. Search Tables are ERT-only because complete Consecutive evidence is not available there. 24. Adaptive legacy behavior Preserved. Adaptive still feeds Station Events and Current Assembly. The new overlay is fixed-threshold ERT only. 25. Legacy fixed ERT tables PumpDurationERT and PumpActivityERT remain in the catalog and Python pipeline at 15 minutes. 26. Canonical snapshot / save-reopen presentation is optional on table sections. Legacy snapshots with presentation: null still validate and render with is_event_row. New snapshots store view state (including ert_settings when present) and reapply on reopen. 27. EMAIL rendering HUB presentTableSection applies the overlay when presentation is set and the table is not assembly-bound. EMAIL-v1 was not modified. Highlight still uses is_event_row; HUB sets that flag from overlay identity when annotations are shown. Plain presentation leaves rows unhighlighted and without an Event column. Cloudflare requests stay 0 in tests. 28. Auto/custom narrative autoTableNarrative() exists as a helper only. It is not wired into Current Assembly. Deferred to E4H.2. 29. Future AI compatibility A later local AI can set the same structured presentation object (station/start/end/pump/row_mode/event_display/highlight_enabled) without HTML-specific logic. No AI was implemented. 30. Files created β’ src/public/pump-activity-presentation.js β’ test/pump-activity-presentation-e4h1.test.js β’ test/pump-activity-table-integration-e4h1.test.js 31. Files modified β’ src/public/trend_report.js β’ src/public/trend_report.html β’ src/public/data_views.js β’ src/public/data_views.html β’ src/public/station_review.js β’ src/public/station_review.html β’ src/public/styles.css β’ src/server.js β’ src/services/saved-reports.js β’ src/services/trend-report-email.js β’ cache-bust strings in a few existing tests (saved-reports-e4d, station-event-email-ui-e4c1, station-review-queue-e4h1) Not modified: event-engine.js, analysis-settings schema (reused), Python ERT builders, EMAIL-v1, research/. 32. Focused E4H.1 tests 30 / 30 33. Search Tables regression 40 / 40 (catalog, exact time, pump, historical durations, shared renderer) 34. Trend Report regression 85 / 85 on X4 + E4G.6 / 6A / 6B core files; remainder included in full HUB 767. 35. Saved Report regression 16 / 16 (saved-reports-e4d + report-table-compatibility-e4d2) 36. Event/detector regression 54 / 54 (local events, event quality, fixed-ERT workflow, event presentation) 37. HUB full regression Starting baseline 737 / 737. 767 / 767 (737 prior + 30 E4H.1 tests) A first parallel run hit 766/767 from two suites sharing temp files; the serial rerun was 767/767. 38. EMAIL full regression 64 / 64 39. Capture reliability 9 / 9 40. Production DB writes 0 in tests. ERT settings GET is read-only. 41. Real emails sent 0. Cloudflare requests 0. 42. Real captures 0 43. Detector files modified NO. detectConsecutiveRuns() unchanged. detectFixedErt() still unused by detectEvents(). 44. Research files modified NO 45. Manual owner QA Live BOSS UI was not opened in a browser from this session; behavior was verified with node --test. Please confirm: 1. Station Review β settings: EXTENDED RUNTIME Enabled + Threshold (minutes). Set a station to 6.0; confirm storage is 360 seconds. Confirm Adaptive controls are unchanged. Confirm email/SMS are not flipped on. 2. Search Tables β historical durations: defaults Events None / Highlight Off. A 20-minute row looks like any other row. Turn Events = Extended Runtime and Highlight On β Event column and yellow row. Highlight Off β same rows, fully plain. 3. Search Tables β PumpActivityDaily: no Event overlay; MAX above 15 minutes is not an ERT event. 4. Trend Report: drag a Station Event table. Table Display exists. Defaults All Events / Highlight On. Events Only hides ordinary rows. Changing Start/End then Apply reloads annotations for the new window. Apply does not create a second Canvas section. 5. Current Assembly: no Table Display / Apply. Consecutive/Adaptive detector rows still highlight via is_event_row. No extra Event column from the overlay. 6. Save / reopen / email a mixed report: annotated user table stays annotated; a plain table stays plain; a pre-E4H.1 saved report still opens. 7. Multi-station granular table: different thresholds on two stations; a 10-minute run annotates only the 6-minute station. 46. Recommended E4H.2 (do not implement now) β’ Wire auto/custom narrative to the overlay counts β’ One unified event-aware pump-activity table per useful station/window β’ One standard trend β’ Stop emitting redundant automatic event-specific tables β’ Controlled Adaptive β owner-threshold ERT transition for Station Events (history preserved) βββ Acceptance check: raw rows immutable; per-station ERT; default 15 minutes; no moving average for the overlay; same table annotated or plain; Search defaults plain; event-focused Trend Report defaults annotated; range refresh; Events Only; All Activity; sort/pump/multi-station; no aggregate MAX-as-ERT; deterministic presentation; multi-annotation; Consecutive detector unchanged; Adaptive and legacy ERT tables preserved; historical snapshots compatible; no notifications/email/captures/production writes in tests. Stopped here. Automatic report assembly was not redesigned.
-
R.Gion (Any/All) (@Gion_the_critic) reported@SportingNest @Cloudflare Where was this? I've never seen it
-
Coobyk (@Coobyk_) reportedHow AI pilled am I if I ask Poke to use Cloudflare MCP to create a Worker that would translate Poke MCP calls to Porkbun's custom system just to never use it because I don't need to buy domains that often?
-
GoβΏrrr.me (@GoBrrr_me) reported@janrothen @paoloardoino @The_Pi_Hole And/or set your DNS Servers to: Primary: 1.1.1.2 Secondary: 1.0.0.2 Cloudflare blocks a lot of bad stuff like phishing, scams, and malicious domains right at the network level.
-
J. (@munchivelo) reported@dillon_mulroy @EffectTS_ hm. what do you mean great cloudflare support? if i'm building apps for cloudflare ecosystem, what benefit does using EffectTS have over regular typescript/tailwind? can you be specific.
-
Nick Dodd (@nickdodd) reported@BraydenWilmoth Who knew billing was important for a company literally selling services? I never, ever, have wondered why I have never used Cloudflare for anything.
-
Paul T (@BscTraynor) reported@ClareCraigPath petition site receives a massive surge of traffic from X, Cloudflare may issue a "Checking your browser" challenge page or briefly queue users to prevent the server from crashing
-
Awais alwaisy (@alvaisy) reportedcloudflare workers are definitely not for everything. i spent 20 hours on problem. `give you agent docs`. better alternative to context7. at the time of testing. cloudflare worker 50 subrequest limit crushed it. i've 2 choice now. - abandon it. - move to vps.
-
Reina Cruz π₯Όπ§€π¨πΊ (@rea1ReinaCruz) reported@Cloudflare Fix human verification