Cloudflare status: hosting issues and outage reports

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.

Most Reported Problems

The following are the most recent problems reported by Cloudflare users through our website.

• Cloud Services (58%)
• Hosting (25%)
• Domains (17%)

Live Outage Map

The most recent Cloudflare outage reports came from the following cities:

City	Problem Type	Report Time
Ahmedabad	Cloud Services	2 days ago
Le Puy-en-Velay	Cloud Services	4 days ago
Ann Arbor	Cloud Services	5 days ago
Palermo	Hosting	6 days ago
New York City	Hosting	15 days ago
New York City	Cloud Services	1 month ago

Full Outage Map

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:

• 
  Krishna Singh (@krishnasinghdev) reported 9 minutes ago

  @tapasadhikary @Namecheap I never liked namecheap / godaddy, don't know why people choose it over simple providers like cloudflare where they charge same amount for 1 or 10 years

• 
  Lubos Kolouch (@LubosKolouch) reported 9 minutes ago

  Think twice before you paste: if a website's "Cloudflare CAPTCHA" asks you to open Windows Terminal and run a command, it's a trap. This is TerminalFix, a malware campaign Microsoft detailed in late August 2026. Pasting the code installs malware, exposes your accounts, and opens a backdoor to your network. Real CAPTCHAs only ask you to click images or checkboxes. Never open Terminal or PowerShell just because a website told you to. If you see these instructions, close the tab immediately to avoid a full corporate breach.

• 
  LilRhodySpecial (@rhody_special) reported 11 minutes ago

  @Sprytixl Yet another ad to get you to use their data stealing bot on the cloudflare data snooping service

• 
  Declan | Rust Developer (@buildWithDeclan) reported 14 minutes ago

  @acolombiadev @Cloudflare Thats why i am loyal to them. They provided services when i was poor. All my platforms are in cloudflare

• 
  Durp  (@durpsick) reported 14 minutes ago

  This will happen in the span of 30 days. We will also be adding • Accounts (if you wanna make one) • backed server support • meny charity's • better service support Everything listed will also be supported by Cloudflare Security!

• 
  Anime Novakai | Anime News, Updates & Leaks (@AnimeNovakai) reported 18 minutes ago

  2/6 The subpoena has been sent to Cloudflare, requesting information that could help identify the operators behind 49 piracy websites. Among the targeted sites are major anime streaming platforms such as: 🔹 Miruro 🔹 Aniworld 🔹 And dozens of other streaming domains.

• 
  Karsten Lehmann (@Klehmann79) reported 21 minutes ago

  Hey @Cloudflare I accidentally ordered a pro account (1 year) for the wrong domain and all I get in your support portal are standard docs. How can I submit a case? There‘s no way to get to a form, even as paying customer.

• 
  ⚛︎ Daddio ⚛︎ (@ScienceDaddio) reported 26 minutes ago

  @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.

• 
  ticktechh (@sprki999) reported 29 minutes ago

  @OmegaNekoSimp @NoboKik Does cloudflare use PoW? Never noticed a temperature spike from those and the ryzen in my thinkpad likes to spike 15 degrees just from looking at it

• 
  James (@jamescoder12) reported 33 minutes ago

  The uncomfortable truth. Your ISP has no incentive to optimize your router settings. They have every incentive to leave them on factory default and every incentive to upsell you when the defaults cause problems. When your Wi-Fi is slow, you call and complain. They test Speed 1 the connection to your modem. It's fine. So they tell you "everything looks good on our end" which is technically true. Then they offer you a faster plan. You pay $30/month more. Speed 1 goes up. Speed 2 the Wi-Fi to your devices doesn't change. Because the bottleneck was never the pipe coming into your home. It was the 6 feet between your router and your laptop. When your firmware is 4 years out of date, they don't push an update. When your channel is congested, they don't suggest switching. When your DNS is slow, they don't mention Cloudflare. When your channel width is halved, they don't widen it. When your security is on WPA2 with the factory admin password, they don't flag the risk. Every free fix that would make your Wi-Fi faster is a fix that prevents them from upselling you a more expensive plan. Every month you rent their router is $14 in revenue for a $60 device they deployed years ago. The rental has no end date. The equipment depreciates. The revenue doesn't. He called his ISP 4 times. They suggested upgrading twice. He upgraded twice. He paid $360 extra over a year for a faster plan that didn't make his Wi-Fi faster because the problem was never the plan. It was 9 settings his ISP could have fixed in a 5-minute phone call. They chose to sell him a faster highway instead of widening the off-ramp. "Your ISP isn't slow. Your settings are. And the company delivering your internet profits every month you don't know the difference." 9 settings. 15 minutes. $528/year back. Faster internet on a cheaper plan. The router was never broken. The defaults were designed by a company that makes money when you think it is.

• 
  LUIS- LUIS- (@LUISLUIS532957) reported 34 minutes ago

  @itz_pippo still not working, akira is blocked by cloudflare, please include always other hosts, thanks.

• 
  Elijah Trillionz (@ElijahTrillionz) reported 36 minutes ago

  There is currently no cards or payment methods that is working for Cloudflare. @Cloudflare @CloudflareDev @CloudflareHelp And no way of getting help. This is bad

• 
  Alexey Vasilev (@Alvasilevv) reported 38 minutes ago

  @Jilles Code Mode trades an enumerated surface for a searchable one. Works when the agent already knows it wants Cloudflare. The tool list was a terrible context budget, but it was the only enumeration the model got. Once you import what you need, discovery is a step nobody owns.

• 
  ticktechh (@sprki999) reported 39 minutes ago

  @OmegaNekoSimp Thats the only human check that doesnt trigger me. What the actual **** does the challenge of clicking a box from cloudflare do? How isnt that challenge useless?

• 
  David T Kramaley (@simplydt) reported 40 minutes ago

  @mathieuxtms @whop lean stack wins. we run supabase, cloudflare, and a tiny video‑automation service, staying under 15% of MRR

• 
  Tang Vu (@tangvu_dev) reported 42 minutes ago

  In the Vietnam 100-VU burst, Cloudflare averaged 191.77 ms vs Vercel’s 430.95 ms. P95 was 337.11 vs 879.96 ms, with 0% errors on both. But cross-region burst tests reversed the winner in the same regions as the warm tests.

• 
  vidaaustera.x (@vidaaustera) reported 45 minutes ago

  Stopping the bad guys with Cloudflare: 5,262 malicious requests blocked or challenged in the last month #cloudflare

• 
  PureStory (@PureStoryLabs) reported 53 minutes ago

  @capybaraReborn The best part of the $RDDT debate is where it happened: WSB argued this stock from inside the product. The bull thread that stuck was the S&P 500 add, 2,900 points. The bear thread that stuck was Cloudflare data saying 57% of Reddit's traffic is bots. The stock is down 15% since the July scare over the Google deal, so the crowd living inside the asset still hasn't settled what it's worth.

• 
  Saeid Shahriari (@saeidshahriari) reported 54 minutes ago

  Stopping the bad guys with Cloudflare: 16,098 malicious requests blocked or challenged in the last month #cloudflare

• 
  Tang Vu (@tangvu_dev) reported 55 minutes ago

  I 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.

• 
  Sameer Bhagtani (@sameerbhagtani) reported 55 minutes ago

  @NiceCodeWriter You should make use of cloudflare tunnels. That should solve your problem.

• 
  Andy Knowles (@andykn101) reported 55 minutes ago

  @SportingNest @Cloudflare It's absolutely a scam. If you don't know what those instructions do listen to those who. If you're not clicking on the ads in your search results you've probably already got malware poisoning your search results. Get help.

• 
  Adie (@wbvend) reported 55 minutes ago

  @levelsio @Cloudflare My agent can buy on Namecheap API without issues Then goes on to build + deploy on the VPS everything is very easy now I also have expired domain hunter which pulls down then checks on DataforSEO 🎉🥳

• 
  William Bello (@belljobs94) reported 56 minutes ago

  THE GOAT on their free service !! @Cloudflare hands down

• 
  DeathScythe (@DeathScytheH) reported 58 minutes ago

  @BowTiedWaterDog @BowTiedCrocodil Netbird self hosted. Zero trust network wireguard based with “cloudflare tunnels”.

• 
  SyntaxError » CEO of "CEO of..."-names (@SyntaxError2505) reported 1 hour ago

  @NewAgeRetroNerd It never failed on me Cloudflare should have a look

• 
  Adam Rackis (@AdamRackis) reported 1 hour ago

  @kettanaito @flydotio Do your pods auto-sleep when they’re not getting traffic? I think there’s a min setting you have to set to zero to let everything shut down and then just cold start on the next request. Really though surely Cloudflare free tier is simpler?

• 
  Paul T (@BscTraynor) reported 1 hour ago

  @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

• 
  Coobyk (@Coobyk_) reported 1 hour ago

  How 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?

• 
  Deyder Cintron (@deydercintron) reported 1 hour ago

  @levelsio @Cloudflare Full API surface that lets you register and manage without handoffs is the real unlock. Anything that forces a browser click or support ticket re-introduces the bottleneck.