Cloudflare 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:

• 
  Klaus Arent (@klausarent) reported 5 minutes ago

  Cloudflare returned error 7003. The message reads like a permissions problem, so that is what my agent debugged: it rotated the API token, widened the scope, checked the account id, and came back twenty minutes later with a token that had more rights and the same error. The actual cause was one character in the path. I had written dns/records where the API expects dns_records. A malformed path produced an error that described a credential problem. An error message is a hypothesis written by someone who could not see your bug. Agents treat it as a diagnosis, because it arrives in the authoritative position: last thing printed, right after the failure. The ordering that fixed this for me: 1. verify the request itself against the current docs 2. reproduce with one known-good call to the same host 3. only then touch credentials Credentials are the most expensive thing to change and the easiest thing to blame. Any error that suggests you widen access deserves the request checked first.

• 
  Larius Woodson (@LariusWoodson) reported 5 minutes ago

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

• 
  Logan Gott (@LoganTGott) reported 6 minutes ago

  Meta just cut 10% of its entire workforce. In the same breath, they moved 7,000 people onto AI teams. Cloudflare laid off 1,100 the same month and openly called it operating in the agentic AI era. And this is, unequivocally, the clearest signal I've seen since OpenAI and Anthropic both shipped agents that run entire business workflows this month. The biggest companies in the world are done paying teams for work AI can now do in seconds. We saw this coming a while back. Moved our whole model into founder-led authority content, in the founder's own voice, built to turn trust into pipeline. Already paying off for our clients, and it's only going to compound from here. This is the opportunity right now. You take the founder's actual expertise and turn it into content only they could make. You build the distribution so the right buyers actually see it. You set up the funnel underneath so the attention has somewhere to go. Then you turn that trust into booked calls, over and over. That's the core of what we do. Turning a founder into the reason their market trusts the company. There are a lot of fly-by-night offerings circulating right now when it comes to LinkedIn content. For example, 'AI ghostwriting'. Pumping the same AI posts into a feed that's already drowning in them does nothing, it just makes you blend in faster. The founders who will absolutely dominate their space over the next 5 years are building a name and a voice their market actually trusts. AI is showing you exactly what's coming for anything that can be automated. Your job is to become the one thing it can't copy, the founder your market already knows and trusts.

• 
  GrainStats 🌾 (@GrainStats) reported 7 minutes ago

  @HTSCommodities @bfl_ai @NousResearch anything is possible right now i'm betting on agentic flows being monetized. there is a market for this, it will take time, but it will get done. that and IP rights being monetized (e.g. buy my chart, limited to 100 views) most of our traffic is bots these days anyway...maybe charge them a nickel per visit? surely cheaper than burning tokens for no reason no doubt in my mind that *everything* and i mean everything of value will be paywalled and locked down in the next few years (also thesis to long Cloudflare)

• 
  flavio (@flaviocopes) reported 13 minutes ago

  @dnnskr91 Yeah but I’m doing all on Cloudflare these days from domain to compute and database for new apps so not an issue for me rn

• 
  WIV Reports — Uncensored (@WIVReports) reported 13 minutes ago

  @BasedTorba I canceled my Gab AI subscription. I paid for a full year and got hard-locked out of prompt submissions. Support claimed my ISP was blocking the site. Developer Tools (attached) explicitly showed Cloudflare returning HTTP 429 Too Many Requests on your socket io endpoint (Ray ID: a2377c992a865050-SEA). Support's official response? "Dev ops confirms you are not blocked by CF and says your understanding of what you are seeing is an incorrect assumption." An HTTP 429 from Server: cloudflare is, by definition, an edge rate limit. Instead of escalating basic DevTools data to fix a socket routing bug, support gaslit a paying customer and issued a partial refund to shut down the ticket. If this is how Gab handles infrastructure bugs and long-term users, people should know what to expect. Andrew, email chain is available if you actually care about fixing your support and edge config.

• 
  Favour Y. (@FavourYusuf1) reported 16 minutes ago

  Got this thing, for 2 months it didn't work. Then after I fixed it, like half the internet did not work on it because cloudflare blocked it. Very useless something. And their support is non-existent. Even their staff don't know how the damn thing works. Imagine them googling what the home ip address for the ODU is, they only knew the one for the indoor unit. I wish I can sell mine sef.

• 
  Rheza Pahlevi (@rheza) reported 17 minutes ago

  @eastdakota @Cloudflare Can you guys please fix your support team first ?, I have been waiting for email support. My account and domain has been hacked and taken over by someone else.

• 
  Turing (@turingops) reported 19 minutes ago

  hi @KentonVarda I can’t understate the usability improvements to CloudFlare dashboard over the past few years, but I’m having problems with the agent on mobile (iPhone) - could you maybe assign a worker to making the entry text more accessible? It scrolls below the view window.

• 
  Michael Blau (@blauyourmind) reported 21 minutes ago

  @eastdakota @Cloudflare You support @trydrip

• 
  Lockendrik (@Lockendrik41) reported 26 minutes ago

  Someone has to notify Cloudflare (SoyBooru's registrar) about the SoyBooru's current state. All the degenerate **** that's getting posted on the 'ru is only visible like the ATFbooru where you can only see the 'P by making an account there.

• 
  Sulfur (@sulfurscales) reported 28 minutes ago

  here's how to BUILD a phone farm for tiktok that costs under a cent per post instead of $0.5-3 per piece 10 old iphones running locally off a mac, iphone 7 through iphone 11. 2-3M views a month across 20 accounts, 30-40 posts a day, all targeting the us while running physically outside it. best single post hit 1.1M, median sits around 5000. 2000 views turning into 1 install, 5% of those installs converting to paid, best days pulling 80 installs and 5 new customers the problem being solved: every slideshow tool on the market charges per piece, reelfarm and the rest land around $0.5-3. at 40 posts a day that's $500+/month before you even know which angle works. a proper testing phase at that rate runs $2-3k before you get any signal, and none of those tools guarantee quality even with good prompts the fix: build the generator yourself. python scripts, settings files per phone, no database, no cloud, no saas. runs entirely off a laptop the pipeline breaks into a few agents. a parser that pulls content across the niche and ocr's it. a reference builder that turns that into reusable angles. a slide and video generator that mixes pre built pieces with new hooks and captions, no llm needed for the actual generation. a daily poster that pushes content to each phone through shortcuts so there's no manual airdrop, content lands straight in the clipboard ready to paste. a calendar and analytics scraper once excel stopped being enough past 20-30 accounts phones were $50 each, bought old. an iphone 7 on ios 15 matched an iphone 11 on ios 26 for performance, newer hardware didn't move the needle at all. the actual variable is content, not device each phone runs 30+ settings from an internal library before it touches tiktok, and the exact list differs slightly per model and ios version. dns leaks patched, webrtc leaks closed, ip tied to a specific location so the account can't be traced back to a base photos get run through a module that rewrites exif data to match a real iphone camera roll. camera dimensions, mb size, live photo data, geo tag matching that specific phone's ip, dozens of parameters layered in. this is the part that actually moves rankings, tiktok ranks native capture higher than obvious stock or ai output, and none of it triggers an ai generated label after posting video repurposing works too, same clip with a different hook counts as a new video to tiktok once it's run through the pipeline posting 20 slides across accounts takes 35 minutes total with shortcuts handling the transfer running cost: $40/month proxies, $40/month llm subscriptions, hosting free on cloudflare. one time setup was ~$300 for hardware plus ~$300 for courses, on top of $500 for the phones themselves. total spend so far sits around $1k, three months to build, now running at 2 hours a day android was tested and dropped. cloud androids passing google's full integrity check cost more per month than buying a used iphone outright, and still underperformed, the cheaper android tiers did worse. rented androids also couldn't run a second account on the same device, which killed the option outright account health has been mostly clean on ios, androids were the ones getting banned. one attempt at running tiktok on a jailbroken ios 16 device got logged out fast, no ban, but enough of a signal to not push jailbreak further until there's a way to test it without burning dozens of accounts first what's still unexplained: two accounts running nearly identical content and setup, one hits 1M on post 3, the other barely moves. same hook photos with minor crop or filter changes keep working, no clean read on whether that step is even necessary. one of the best performing accounts doesn't have us dns at all and still pulls more us traffic than accounts that do. no clean answer for any of it, just logged as unresolved and moved on next step is pushing toward phones running 24/7, automated swiping included, and expanding past tiktok into instagram reels

• 
  Bojan Josifoski (@twistedroute) reported 29 minutes ago

  @JamesWelbes I moved all my sites of wp, its sad for me but things are moving forward and wp can’t quite follow the game, because 43% of the internet is on it and things move painfully slow for it. Plus add cloudflare on top of it and what they offer for static sites, it a no brainer.

• 
  mama happy 🪿🐥🐥🐣 (@inthegardenzz) reported 30 minutes ago

  @Cloudflare fix ur technology 🖕🏽🖕🏽🖕🏽

• 
  Xamayon (@SauceNAO) reported 32 minutes ago

  If you use Vultr Firewall Groups and have a rule restricted to Cloudflare sources, it's probably blocking all traffic right now... Either switch the rule to allow all or disconnect and reconnect the firewall group from your servers. Not thrilled that they knew about the issue and didn't bother to let their customers know.