Namecheap status: hosting issues and outage reports

Problems in the last 24 hours

The graph below depicts the number of Namecheap 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 Namecheap users through our website.

• Hosting (57%)
• Domains (43%)

Live Outage Map

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

City	Problem Type	Report Time
Tuxtla	Domains	17 days ago
Centerville	Hosting	17 days ago
Noida	Domains	1 month ago
Purmerend	Domains	1 month ago
Istanbul	Hosting	1 month ago
Charleston	Hosting	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.

Namecheap Issues Reports

Latest outage, problems and issue reports in social media:

• 
  Álvaro Trigo 🐦🔥 (@IMAC2) reported 38 seconds ago

  @levelsio Yeah moving all my domains to Cloudflare too. Namecheap ui and price sucks now .

• 
  Adam Holter (@AdamHoltererer) reported 2 minutes ago

  @gauravsapkotanp Definitely not Namecheap, because @theo said they were bad and scammy.

• 
  Bogey Wilcox (@brasscogg) reported 4 minutes ago

  Unverified conspiracy theory: GoDaddy holds all these inactive domains through a shell company so they can charge finders fees and commission to “find” the owner of the domain, themselves Namecheap would never stoop to such loser levels

• 
  ... (@irucsbo) reported 6 minutes ago

  .@Namecheap stole my funds and refuses to provide a real solution or proper support. Extremely disappointing experience with a company I trusted for years. Criminal organization. Avoid at all costs.

• 
  Shant (@ShantDotMe) reported 7 minutes ago

  Hey @Namecheap are we trying to outdo @bluehost as worse customer service?! It has been a month and a week since I opened a security issue ticket with them (and still no reply), but your livechat isn't doing any better atm.

• 
  Garrett 🤠 (@garrett_makes) reported 10 minutes ago

  @levelsio When Cloudflare has had issues in the past did it impact domains? Always afraid to use them for the outages. I've had zero downtime from Namecheap and Hetzner in the last 2 years but Cloudflare has had multiple outages in that time.

• 
  timagixe (@timagixe) reported 12 minutes ago

  i remember the first time I bought domain on NameCheap the first thing I did in 10 minutes - transferred domain to CloudFlare luckily to me it was .com - so no issues with that

• 
  🛡️Shir Khorshid Noor Cyber Unit🛡️ (@FriendOfTheInst) reported 16 minutes ago

  Sponsored search results are not a trust boundary. A fake ChatGPT download campaign used brand impersonation, malvertising, shared-link abuse, cloaking, platform-specific payloads, CAPTCHA gating, Electron packaging, JavaScript obfuscation, and staged execution to deliver malware to Windows and macOS users. This is not merely another fake download page. It is a clear demonstration of how attackers exploit trust across multiple layers: • Trusted brand • Trusted search flow • Trusted-looking ad placement • Trusted-looking domain patterns • Trusted UI/branding • Trusted installer frameworks • Trusted code-signing assumptions • Trusted AI platform sharing features What happened: Attackers promoted a fake OpenAI/ChatGPT download experience using the domain: openew[.]app The site copied OpenAI-style branding and offered download paths for: • Windows • macOS • Chrome extension The Chrome extension path linked to a legitimate ChatGPT-related extension, further increasing perceived legitimacy. The Windows and macOS download paths delivered malware. Attackers also abused legitimate ChatGPT shared conversation links, including chatgpt[.]com/s/ pages, to host fake outage or download pages. A link hosted on a trusted domain can still deliver attacker-controlled content to users. The campaign employed cloaking and conditional rendering: automated scanners and analysis tools were shown benign content, reportedly an unrelated AR/VR company site, while real browsers received the malicious ChatGPT-themed download experience. That is the key lesson: A trusted domain, HTTPS padlock, sponsored ad, or polished UI does not equal a safe download. Why this campaign matters: Victims were not browsing dark web forums or downloading cracks. They were searching for a legitimate AI tool. That is why malvertising is effective: it targets high-intent users at the exact moment they are ready to install software. The campaign turned normal user behavior into an initial access path. Windows chain: The Windows payload was distributed as: Chat_GPT.exe Reported SHA-256: 56CC26E88C064B0C423AA8AD6530E58F91D1E4D28FAB1A8BCEDEF16A6582B4D2 Additional reported Windows hash: c9e0e6985dca3a179c9bdea4e7b38f7dc57fe00ecedc2fd634256fc53bf2de2d Important: hashes are useful for triage, not sufficient for defense. Campaigns rotate samples. Hunt behaviorally. Windows technical observations: • Installer built with Inno Setup • Electron-based application • Chromium runtime components • resources\app.asar archive • Large obfuscated JavaScript payload identified as winter.js • Hex-encoded strings • Dynamically resolved functions • Control-flow obfuscation • Event-driven execution • CAPTCHA gating before core behavior • Inner Electron payload (App.exe) launched after installation • PowerShell spawned after CAPTCHA completion Observed PowerShell pattern: -ExecutionPolicy Unrestricted -Command - That trailing dash matters. It suggests commands may be supplied through standard input rather than appearing directly in the process command line. This reduces the value of command-line-only detection and makes process-tree and behavioral monitoring much more important. Static red flags: The filename suggested ChatGPT, but embedded metadata reportedly identified the installer as: PovariEGLESVapp Setup The executable was signed by: F.F.A.P. Hurkmans Beheer B.V. That publisher does not align with OpenAI or ChatGPT. Important reminder: a valid code signature does not mean software is safe. It only confirms that the file was signed by a certificate and has not been modified since signing. It does not establish that the software is legitimate or authorized by the brand it imitates. Additional Windows indicators: • App.exe SHA-256: D9AD44D43E57B870793FA5CF7FB3A813990D0CBD0C7087BDE70A5E61FB1F1FE6 • Unexpected Chromium/Electron profile: %APPDATA%\Satoshi • Additional reported path: %APPDATA%\LeronApplication • Reported Electron/Node capabilities: systeminformation, child_process, os, fs, zip-lib, Those modules indicate a capable execution environment: system discovery, file access, archive handling, process execution, and network communication. macOS chain: The macOS payload was delivered as: ChatGpt.dmg Reported SHA-256: 7E5B708F6659B1FAD3AAE7B589A706434FBF21708AEEC5AF5910189B96E25FEF Additional reported macOS hash: c0919e1999eaee67e67aeda0287722775afb04e9a9a0f727928b4d11265fb70b The macOS malware is reported as Odyssey Stealer, a fork of AMOS / Atomic Stealer. Reported macOS targeting includes: • Browser passwords • Browser cookies • Saved logins • macOS keychain data • Telegram sessions • Cryptocurrency wallet directories • Desktop/Documents files with sensitive wallet/key extensions • Ledger Live • Trezor Suite • Exodus • Electrum • Sparrow The most dangerous macOS behavior: Wallet replacement. The malware reportedly attempts to replace legitimate wallet-related applications with trojanized versions. That means a victim may later open what appears to be their normal wallet app, but actually launch an attacker-controlled version. That is not only credential theft. That is long-tail financial compromise. Infrastructure: Reported malicious domain: openew[.]app Reported infrastructure includes: 144[.]172[.]104[.]205 188[.]137[.]246[.]189 192[.]253[.]248[.]181 172[.]94[.]9[.]250 Infrastructure notes: • Recently registered domain • Namecheap / registrar-servers infrastructure reported • RouterHosting infrastructure reported • Passive DNS linked infrastructure to other suspicious or malicious domains • .app domains require HTTPS, so browsers show a padlock The padlock only means the connection is encrypted. It does not mean the site is legitimate. Detection opportunities for defenders: 1. Newly created executables launched from Downloads, Temp, or other user-writable paths 2. Trusted-brand filenames that do not match embedded metadata 3. Installer publisher mismatch: filename says ChatGPT, signer is unrelated 4. Electron apps spawning scripting engines: powershell.exe cmd.exe osascript bash sh zsh 5. PowerShell with: -ExecutionPolicy Unrestricted -Command - 6. Unexpected Chromium/Electron profile directories, such as: %APPDATA%\Satoshi %APPDATA%\LeronApplication or other anomalous Electron profile paths 7. app.asar archives containing large obfuscated JavaScript bundles 8. CAPTCHA or user-interaction gating before malicious behavior 9. Newly registered domains impersonating major software or AI vendors 10. Users installing software from ads instead of official vendor channels 11. Suspicious wallet-app replacement attempts on macOS 12. Post-install network traffic to low-cost VPS infrastructure 13. Legitimate AI sharing URLs that render fake support, outage, update, or installation pages 14. Download pages that show different content to scanners than to real browsers The key defensive point: Do not build detections only around hashes or static strings. This campaign reduces the value of static analysis through: • Obfuscation • Runtime string construction • CAPTCHA gating • Electron packaging • Conditional execution • Cloaking • Staged payload behavior • Shared-link abuse on trusted domains The better approach: • Behavioral detection • Process-tree monitoring • Parent-child process analysis • Script-engine execution monitoring • Browser/download source telemetry • Application control • Newly registered domain monitoring • Publisher and metadata validation • EDR detections for Electron-to-shell execution • Monitoring for AI-platform shared links used as delivery pages • User training focused on sponsored-result and fake-download risk For users: Only download ChatGPT from official OpenAI channels or the Microsoft Store. Do not install software from ads, mirror sites, download portals, unfamiliar domains, or fake support/outage pages. If you installed a “ChatGPT” app from an ad or unfamiliar page: Use a clean device and: • Sign out everywhere from important accounts • Change passwords, starting with primary email • Rotate API keys, SSH keys, cloud credentials, and tokens • Revoke active sessions for email, GitHub, cloud, Discord, Telegram, crypto exchanges, banking, and password managers • Move crypto funds from a clean device • Do not open Ledger/Trezor apps on a potentially infected Mac • Monitor financial accounts • Reinstall the OS • Notify IT/security immediately if it was a work device For AI vendors and platform owners: This is now part of the product security perimeter. Brand impersonation, malicious search ads, fake download pages, clone domains, and abuse of shared AI content are active distribution channels. Practical controls: • Make official download links easy to find • Monitor sponsored ads for brand abuse • Monitor newly registered lookalike domains • Detect abuse of shared-content features • Run takedowns quickly • Publish clear download guidance • Provide signed-installer verification guidance • Coordinate with search/ad platforms • Alert users when major impersonation campaigns are active Bottom line: Attackers are not just exploiting ChatGPT. They are exploiting the trust, urgency, and confusion around fast-moving AI adoption. Today it is ChatGPT. Yesterday it was another AI tool. Tomorrow it will be the next trending product. The malware can rotate. The domain can rotate. The payload can rotate. The brand can rotate. The infrastructure can rotate. The defensive mindset must rotate too: From: “Is this file known bad?” To: “Is this behavior legitimate for this software, this publisher, this user, this source, and this execution context?” That is the difference between signature-based reaction and modern detection engineering. Analysis draws on reporting from Malwarebytes Labs, Evalian SOC, Push Security, BleepingComputer, CybersecurityNews, and OpenAI documentation. #CyberSecurity #Malvertising #ThreatIntelligence

• 
  WP Websites (@WebsitesWp) reported 19 minutes ago

  @katerleonid None. *Godaddy-pricy, had market place problems. *Hostinger+cloudflare-wouldnt use, not their niche *Namesilo-had major security incident, noone cared. *namecheap-not cheap, cluttered UI, intrusive upsells *spaceship-cheaper than internetbs, terrible UI

• 
  Qamar Issa (@QamarIssaqf) reported 23 minutes ago

  @0xPurchase @sidomains @NamePros How to buy in less 25$ Which platform bro to invest I search namecheap spaceship not support this

• 
  Panqueque AF (@panfuckingcakes) reported 24 minutes ago

  @JeremySCook @notdan @Namecheap Came here to say this. Never have to worry about domain suspension lol

• 
  Sahil Jaiswal (@Sahil_Jaiswal02) reported 26 minutes ago

  Godaddy is a **** I should have gone with hostinger or namecheap My site is down after 2 days of getting it …even after successfull verification 😤 No support, no person available… poor service @GoDaddy

• 
  Cemal Coban (@uzakyolkaptani) reported 28 minutes ago

  Why @Namecheap Live Support need always 5-10 minutes before speak with you ?

• 
  Adam Maysonet (@synozeer) reported 29 minutes ago

  @TopShelfNames @spaceship If someone typed in the domain in their browser bar, they would have seen an Afternic lander. The person instead searched for the domain on Namecheap/Spaceship and bought it that way (aka. reg path), so they may never have even seen the lander.

• 
  Priyangu Patel (@patelpriyangu) reported 29 minutes ago

  @PratikSinhatwt Namecheap I use which is the best in pricing and support.

• 
  Greg Lynch (@g_tone_) reported 31 minutes ago

  @Arfness @1grid_hosting Just been through the drama of moving client domains away from NameCheap (in protest of their pro-Zionist BS). I need to find a home for novelty TLDs that Xneelo doesn't support. Can you recommend anything?

• 
  Jenna. Ellis (@JennaeIlIisEsq) reported 32 minutes ago

  @Namecheap @TeamDreier Pls what is going on with namecheap hosting ? My hosting has not been working since yesterday….. fix it pls

• 
  Rozzabuilds (@rozzabuilds) reported 33 minutes ago

  @ffinbuilds I swear I'm the only person on earth to have never used namecheap...

• 
  Longevity World Cup (@LongevityWorldC) reported 33 minutes ago

  Longevity World Cup is temporarily unavailable due to a @Namecheap hosting network incident affecting hosted websites and accounts. We’re monitoring the situation and will be back online once connectivity is restored.

• 
  RGK🌹 (@rgk_degen) reported 35 minutes ago

  1 prompt. Claude builds a $2,000/week website from scratch. Here’s the exact system, step by step. Most people build sites the wrong way. They hire a developer for $3,000–8,000. Wait 3–6 weeks. Get something generic. Then pay another $500/month to maintain it. The new way: 1 prompt. 45 minutes. Launch-ready. WHAT YOU’RE BUILDING A niche service landing page conversion-optimized, Stripe-integrated, SEO-structured that targets a local or vertical market with $200–500 average order value. Target: $2,000/week minimum by week 4. THE PROMPT ARCHITECTURE Your 1 prompt has 4 layers: → Layer 1 Business context “I’m building a [niche] service site targeting [city/audience]. Average order: $[X]. Primary CTA: book a call / buy now.” → Layer 2 Stack spec “Build in HTML/CSS/JS, Stripe Checkout embedded, Calendly widget for booking, Google Analytics 4 ready.” → Layer 3 Content skeleton “Homepage: hero with pain point + 3 benefits + social proof section + FAQ + CTA. No blog. No filler.” → Layer 4 Conversion rules “Above the fold: 1 headline, 1 subheadline, 1 button. No nav clutter. Mobile-first. Load under 2 seconds.” Paste all 4 layers into Claude as 1 message. Hit send. WHAT CLAUDE DELIVERS IN 45 MINUTES → Full HTML file, production-ready → Stripe Checkout flow embedded → Mobile layout done → Meta tags + OG data for social sharing → Contact form wired to Formspree (free tier) You copy the output. Drop into Netlify or Vercel. Live in 8 minutes. Domain: $12/year on Namecheap. Hosting: $0. Total launch cost: $12. REALISTIC REVENUE PROGRESSION Week 1 Site live. Run $50 in Meta ads to local audience. 3 conversions at $150 = $450. Week 2 Add Google Business Profile. 2 organic calls. 1 closes. $200. Week 3 Raise price 20%. Run retargeting on the 60 visitors who didn’t convert. $600. Week 4 Email the 3 week-1 buyers. Ask for referrals. 2 referrals at $250 = $500 + repeat. Total week: $2,100+. The site didn’t change. The traffic system compounded.

• 
  Resolver Vicky | Dev 🔧 (@resolvervicky) reported 35 minutes ago

  Cloudflare Registrar sells domains at cost and they make zero profit on domain registration. It's a loss leader to get you on their platform. That's why the renewal price never spikes. Namecheap's first-year discount is a customer acquisition trick; the real price is the renewal. Agree?

• 
  Blake Ryan (@blakefakhoury) reported 39 minutes ago

  @namemaxicom @NamePros @Namecheap Haha didn't mean to be rude! I use your tool religiously and have made 7 figures from flips on it, was just pointing it out.

• 
  Shant (@ShantDotMe) reported 42 minutes ago

  @Namecheap that security ticket is with bluehost, not you (thankfully). But 3.5hrs on chat to ID an IP is way too much. and that came after they reviewed the info I provided?? 🤯 I could easily rate this as the worse experience I had with your service!

• 
  🃏 (@anupamrjp) reported 44 minutes ago

  SaaS builders in 2026 👀 Domains? Cloudflare 🔥 Namecheap Hostinger GoDaddy Porkbun Domain won’t save a bad SaaS. Ship anyway 🚀

• 
  CodeWithStu (@CodeWithStu) reported 46 minutes ago

  Hey @Namecheap - getting multiple phising attempts from a domain hosted by you trying to be @moonpay - told me that my phone number had been changed and to call them... lol... domain is arewasolutions [dot] com - please can you take down <3

• 
  Clément Sauvage (@clementsauvage) reported 50 minutes ago

  .@Namecheap locks your account Support : You have to check the email we sent Me : No email, dumbass Support : Ok write to security, they'll reply in 2 hours Me : OK, doing it ... 5 hours later... nothing Current status: no access to my domain, can't swap my DNS. I rly think they don't give a **** about their customers... a huge and deep f*ck you. Have you seen a worst company ? Tell me more... @NamecheapCEO

• 
  The Trunk Tales (@TheTrunkTales) reported 54 minutes ago

  @RealTripleA I know exactly what happened. I cc'd the "host" and they took it down to prevent Namecheap from seeing it. Won't give them the heads up next time.

• 
  Shubh Jain (@shubh19) reported 56 minutes ago

  real monthly infra cost of a solo SaaS in 2026: - Supabase free: ₹0 - Railway starter: ₹800 - Resend free (3K emails): ₹0 - Cloudflare free: ₹0 - UptimeRobot free: ₹0 - Sentry free (5K errors): ₹0 - PostHog free (1M events): ₹0 - Vercel hobby: ₹0 - Namecheap domain: ₹900/year - Anthropic API (light usage): ₹500–2K total: under ₹2,000/month the "I can't afford to build" excuse died in 2024. what's the real reason?

• 
  Bennico (@baro0xx) reported 58 minutes ago

  @Namecheap Fix your servers!!! 33% packet lost to 8.8.8.8 is unacceptable even for a server in Africa. Your tech support telling me to reboot and change hostname. They clueless. This is a serious production software. Fix your servers and educate your tech support!!!

• 
  Chidi inyama (@chidimarvel) reported 58 minutes ago

  @RaenestApp trying to make a payment on namecheap, getting insufficient balance error when there are funds on my card. Please what is going, your support has not replied livechat for hours