Cloudflare status: hosting issues and outage reports

Problems in the last 24 hours

Cloudflare signals over the past 24 hours. The dashed line is the service-wide baseline used to detect unusual activity.

• Service-wide signals
• Service-wide baseline

Most Reported Problems

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

• Cloud Services (62%)
• Hosting (31%)
• E-mail (8%)

Live Outage Map

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

City	Problem Type	Report Time
Tlajomulco de Zúñiga	Cloud Services	6 days ago
Asnières-sur-Seine	Cloud Services	10 days ago
New York City	E-mail	15 days ago
Township of Evan	Hosting	15 days ago
Ahmedabad	Cloud Services	21 days ago
Le Puy-en-Velay	Cloud Services	22 days 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:

• 
  Lex (@TheLexTimes) reported 3 minutes ago

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

• 
  Awais alwaisy (@alvaisy) reported 5 minutes ago

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

• 
  CerooDan (@danieldmai) reported 8 minutes ago

  Whats going on ? Gmail not working properly rn, websites not loading properly. Don't see errors on cloudflare or AWS.

• 
  Reina Cruz 🥼🧤🇨🇺 (@rea1ReinaCruz) reported 8 minutes ago

  @Cloudflare Fix human verification

• 
  siftydeals (@siftydeals) reported 9 minutes ago

  Cloudflare had 487 outages in H1 2026. Most teams still treat uptime like a technical metric instead of a customer trust issue. Your SaaS tool only works if your customers can actually reach it. 🔧 Details in link.

• 
  Tim (@Trendy_Tim) reported 10 minutes ago

  @The_Baron_X150 @SportingNest @Cloudflare That was crowdstrike, cloudflare take down half the internet with some dodgy js or dns config.

• 
  Durp  (@durpsick) reported 11 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!

• 
  Przemysław Zalewski (@Ciunkos) reported 12 minutes ago

  @efalcao @proofpoint @Cloudflare Most likely by the fact Cloudflare is kinda bad at handling abuse reports - try filling their form and see for yourself. Any service that could be used for spam delivery, will eventually be used for that. And Cloudflare now tastes what other providers experience day to day.

• 
  Daniel Zahoor (@DanielZahoor) reported 12 minutes ago

  Set your router DNS to 1.1.1.2 and 1.0.0.2 to block malicious sites across your Wi-Fi. These free Cloudflare addresses silently block scams and phishing on every device. You get network-wide protection with zero software to install or manage.

• 
  Wes Roth (@WesRoth) reported 14 minutes ago

  Cursor cloud agents can now run on infrastructure you manage, including machine pools that automatically scale with demand. Self-Hosted Machines let agents execute inside your network with access to internal services, source control, custom hardware like GPUs and Macs, and existing build infrastructure, while inference, planning, and the agent loop remain in Cursor’s cloud. Cursor also supports AWS Lambda, Cloudflare, Coder, Daytona, E2B, Modal, Namespace, and Vercel. Cursor says cloud agents now create more than 60% of the pull requests it merges internally.

• 
  Blockchain Daily News (@blckchaindaily) reported 19 minutes ago

  🚨 CLOUDFLARE $NET EXPANDS AI AGENT SUPPORT, NOW RUNS CURSOR CLOUD AGENTS ON CLOUDFLARE SANDBOXES FOR CUSTOMER-CONTROLLED EXECUTION - PRESS RELEASE

• 
  MoMoMacro (@MoMoMacro) reported 20 minutes ago

  $NET is in the buy zone. Price: $273.85 Aggressive pullback zone: $274.04 Why we own it: Cloudflare owns the edge that traffic physically transits - a real enforcement point, plus the pay-per-crawl and bot-control layer that decides which AI agents may touch a site at all. Risk: THE MOST EXPENSIVE NAME IN THE ROTATION: 43.3x EV/Sales and ~184x forward earnings on a business with a NEGATIVE GAAP operating margin, ~$109B cap, sitting near its 52-week high. Every take must state the multiple explicitly - the thesis is quality and positioning, never value, and a de-rate does not need bad news to happen. This is the level the work pointed at. Nothing about the thesis changed on the way down.

• 
  Michael Bruno (@brubarian) reported 24 minutes ago

  @RockyCapital18 @TMTLongShort Yes - but it's more of a framework because some rx/diligence are on the private side. But big blue arrow: 1. What are the top three pieces of information that I want to have? 2. What role/function would use this data to solve their own problem? e.g., A DoW analyst wants to know where to buy widgets for a Humvee; how would he try to find the answer? Or a gas station owner wants to know how many Poland Spring bottles to order based on expected highway traffic because of the Sturgis motorcycle rally. 3. Which US institutions/think tanks/policy/others have the raw data? (too many to list) 4. Download CSVs, databases, etc. to desktop to isolate it, Claude from hallucinating or pulling information from the internet. (You may have to get a cloudflare/suprabase/*** to help facilitate accelerated use.) 5. Instruct Claude to clean the data sets (this used to be what data scientists spent most of their time on; NaN, void answers, separating street addresses from state, etc.) 6. In clear, concise, simple language, ask Claude to take XYZ categories of data and produce a snapshot to serve a "product manager at company XYZ" or a "credit risk manager at Bank ABC", etc. 7. Adjust and iterate. Force Claude to produce "Tufte" data visualizations. If Claude is left to run linear/logistic regressions, it becomes a science project instead of a problem-solving or illuminating exercise. 8. Force Claude to explore. e.g., take an analogy, "You are a surgeon; this data set is akin to human nervous system, if you were performing surgery, which node, if removed would destroy the utility of the system"? Random questions like this. Analogically map it in unique ways. Claude RL underbelly does nicely here. And as a guiding principle, I'd suggest focusing on being creative. The best definition I've seen is from Bruner: "Creativity is a way of figuring out what you already know in order to go beyond what you currently think."

• 
  jc (@jc1337asd) reported 26 minutes ago

  My project on @Cloudflare keeps going down because of free tier limits. I want to upgrade to a paid plan but there seems to be no way to limit spending. A plan that costs from $5 to infinity is not really a good plan :(

• 
  2$p00ky (@dos2p00ky) reported 29 minutes ago

  Cloudflare tracker already? Damn girl, you didn’t **** around today

• 
  Ali Avali | #ExtraLife 2026 (@ItsAliAvali) reported 32 minutes ago

  @Porkbun @pcshipp Heh, I have beef with NoDaddy lol If couldn't tell. I do use you guys (PorkBun) and CloudFlare for all my service.

• 
  Alex Betok | PolyViper (@alexanderbetok) reported 35 minutes ago

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

• 
  ッ ᴇᴇʟᴋᴏ ᴀʟᴇxᴀɴᴅᴇʀꜱ (@eelko1976) reported 38 minutes ago

  ethereum:native under the 2400$ solana:So11111111111111111111111111111111111111112 just under the $100 mark. Aay. @BloFin_Official Why do I get a temporarily ban from @Cloudflare for too many requests wtf?! Have to use a VPN now (which I wasn't before) otherwise I cannot access MY account.

• 
  Colby Hill (@Chill_Investing) reported 39 minutes ago

  A TON OF THINGS HAPPENED IN THE STOCK MARKET TODAY. Here's a full recap: 1. Middle East $SPY $QQQ Stocks sold off after the U.S. struck Iranian military assets and Tehran retaliated with missile and drone attacks, putting the Strait of Hormuz back in focus. Crude jumped about 5%, with Brent trading above $90. The S&P 500 fell 0.70% to 7,631, the Nasdaq dropped 1.03% to 26,100, and the Dow slipped 0.79% to 52,767. 2. Bonds $TLT The global bond selloff continued, with U.S. 30-year yields holding at levels not sustained since 2006 and Japan's 10-year briefly touching 3% for the first time in 30 years. The U.S. 10-year sat near 4.77%. Rising discount rates hit long-duration growth names hardest, which is how the tape traded all session. 3. Dell $DELL Dell reported fiscal Q2 revenue of $47.0 billion, up 58% year over year, with adjusted EPS of $7.04 against a $4.88 estimate. Record AI server orders pushed backlog to $95 billion and management raised full-year revenue guidance to $192 billion. Third-quarter guidance of $49.0 billion in revenue and $6.50 in EPS came in well above the $41.42 billion and $4.49 analysts expected. Shares fell 6.9% during the session to $424.36, then rose about 7% after hours. 4. Apple $AAPL John Ternus took over as chief executive and Tim Cook became executive chairman, ending a 15-year run that grew Apple from roughly $350 billion to about $4.6 trillion. Ternus, a 25-year company veteran who led hardware engineering, also joined the board. Shares rose 2.62% to $325.14, the strongest mega-cap performance on an otherwise red day. 5. Palo Alto Networks $PANW Fiscal Q4 revenue rose 34% to $3.41 billion against a $3.35 billion consensus, with adjusted EPS of $1.02. Next-Generation Security ARR grew 63% to $9.10 billion, and fiscal 2027 revenue guidance of $14.10-14.20 billion topped estimates. The company also announced it acquired Console, an AI-native agentic platform being folded into Cortex, with terms undisclosed. Shares still closed down 5.2% to $362.25. 6. MongoDB $MDB Revenue of $771.8 million grew 30% year over year, the fastest rate in several years, and adjusted EPS of $1.90 came in ahead of consensus. Management raised full-year revenue guidance to $2.99-3.03 billion. Shares fell roughly 14% after hours anyway, with expectations having run further than the print. 7. Fed $SPY Futures now imply roughly 68% odds of a 25 basis point hike at the September 16 FOMC meeting. Core PCE is running at 3.3% with headline at 3.7%, and Chair Kevin Warsh has been explicit about the need for further tightening. Energy-driven inflation from the Hormuz disruption complicates the read further. 8. Moderna $MRNA Moderna climbed 9.93% to $154.28, extending its run on continued analyst upgrades following the intismeran autogene Phase 3 melanoma readout with Merck in the 1,137-patient INTerpath-001 study. William Blair moved the stock to Outperform. Merck rose 1.48% to $149.94. 9. Axon $AXON Axon was the worst performer in the S&P 500, falling 8.52% to $518.30. Demand is not the problem, with net revenue retention at 123%. The pressure is coming from a premium multiple meeting rising discount rates, compressed operating margins, and heavy R&D and acquisition integration spend. 10. Software $CRWD $NET High-multiple software took the brunt of the rate move. CrowdStrike fell 6.90% to $215.07 and Cloudflare dropped 6.44% to $285.47. With yields climbing and oil spiking, expensive growth software was the wrong place to be positioned. 11. Duolingo $DUOL Evercore ISI upgraded Duolingo to Outperform and doubled its price target to $210, citing product gains and engagement trends. Shares rose 7.10% to $158.89, one of the few green names anywhere in growth tech. 12. Crypto $COIN $CRCL Bitcoin slid about 2.2% to roughly $77,076, pulling the crypto-linked equities down with it. Coinbase fell 6.00% to $176.83 and Circle dropped 6.36% to $89.48. Interactive Brokers fell 7.00% to $90.42. 13. Energy $XLE $XOM $CVX Energy was the only sector with real strength as crude surged. The sector ETF gained 1.28%, with Exxon up 2.24% to $164.56 and Chevron up 2.38% to $211.05. The defensive tilt showed elsewhere too: the low-volatility ETF fell just 0.20% against a 2.12% drop for high beta, while gold slipped 2.83%. 📈 CHILL INVESTING — YOUR DAILY STOCK MARKET RECAP

• 
  avrin (@itsavrinwave) reported 41 minutes ago

  Is cloudflare down again??

• 
  Patrick Meenan (@patmeenan) reported 44 minutes ago

  @Cloudflare So awesome, but so many questions! Always transcode or pass-trough zstd if the client supports it (since most browsers now support zstd)? Is this also the case when origins provide compressed assets or only when they don't?

• 
  Villainess of Resevoi (@GalCharoShipper) reported 45 minutes ago

  @Tepafray @Sean_Topic AI crawlers simply ignore ****. Even layered defenses recommended by artist-protection groups (Glaze for image-level noise, Cloudflare-style bot blocking, watermarking, opt-out registries) are described as a partial, constantly-shifting arms race, not a solved problem

• 
  ⚛︎ Daddio ⚛︎ (@ScienceDaddio) reported 46 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.

• 
  William Bello (@belljobs94) reported 47 minutes ago

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

• 
  Adsy (@adsydeveloper) reported 52 minutes ago

  @backblaze Dashboard having issues? Cloudflare errors indicating host down (and was ~20s response time just before)

• 
  Noel Ceta (@noelcetaSEO) reported 53 minutes ago

  8/ 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.

• 
  HandsomeHank (@HandsomeHank_) reported 53 minutes ago

  Last night through this afternoon I was pushing Reed (Bot) to maximize my usage after the free reset. I had another reset today at 2pm. I had him create and edit multiple trailers, merge two old websites into one with a new theme, host it on Cloudflare, and create and link a Square store. Then I had him use Printful to recreate old designs from the other site that were never really finished. We also updated a current site so it stays current until we switch over. Reed ended up bringing in another bot (Jules) to help so we could finish before 2pm. Both of them worked hard and stopped at 1:56 so I wouldn’t burn into the next allotment. I have other uses for this week. They left notes to pick it back up if I have extra usage left. Very pleased with their work. @bot @grok 🔥

• 
  Anthony Lambert (@AnthonyTBM) reported 54 minutes ago

  @jb_ma @sb_chadi Yes, but I've never had CloudFlare request a terminal command sequence. I think most people will be immediately on guard if that occurred after clicking their human status?

• 
  robot 2.0 (@alightinastorm) reported 56 minutes ago

  2 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

• 
  Nick Dodd (@nickdodd) reported 1 hour ago

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