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	12 days ago
Centerville	Hosting	12 days ago
Noida	Domains	25 days 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:

• 
  Jack Robert (@neutronmesh) reported 2 minutes ago

  @chrisjfranko @Namecheap Seriously, I pick today to change MX records and this thing has been down for hours.

• 
  DomainHero (@mynamehack) reported 4 minutes ago

  @dynatodd @Namecheap @namecheapceo123 but don't know still they abuse to customer or investors community after VC takeover..

• 
  Wiz (@wizminar) reported 7 minutes ago

  @kalashvasaniya totally agreed, one crucial advice i can give is to keep domain and hosting service different. Will ideally prefer about it can look namecheap or porkbun for domain and netlify or hostinger for hoosting rest please do your own research

• 
  🛡️Shir Khorshid Noor Cyber Unit🛡️ (@FriendOfTheInst) reported 8 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

• 
  Rozzabuilds (@rozzabuilds) reported 9 minutes ago

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

• 
  The Trunk Tales (@TheTrunkTales) reported 10 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.

• 
  Spencer Heckathorn (@mrhobbeys) reported 11 minutes ago

  @BacLeodiv Everyone hates on Godaddy but I e been there 20 years and only had one major issue related to their migration in the early 2010s. Hundreds of domains and 40ish customers. No complaints. I also use the others. Namecheap is up and down on their support. Cloudflare I thought of as expensive. But honestly they all are now.

• 
  Arsi Hoxha (@ArsiHoxha_) reported 12 minutes ago

  @adahstwt Namecheap for years then switched to Cloudflare and never looked back. no markup, no upsells, no drama 🫶

• 
  Ken 🧙 (@thekenndubisi) reported 15 minutes ago

  How to setup an online business doing $1k a day revenue in 30 days: Step 1: Register a business and get a biz bank account. If you’re in Canada, use Ownr. If you’re incorporating in the US, use LegalZoom or Bizee. Step 2: Setup a business email address with Namecheap, connect it to Gmail and sort out tax registration (GST/HST in Canada, EIN for the US) 3: Choose your niche, build your one person offer and price it for an easy yes. A rough example: “I help local gym owners get 10-20 new member leads using meta ads in 30 days or less for $500 a month” 4. Setup your ad account and launch your one-person ad. Rough example: “Attention Toronto gym owners, are your ads getting clicks but no members? Most gym ads fail because of xyz. I help gym owners get x qualified signups using this. Click to watch this 3 minute video showing how it works” 5. Send the traffic to a landing page with the VSL that has these 3 components: a headline mirroring the ad, a short video speaking about the problem, and a link to book a call. 6. Get on a call and ask these 4 questions: where’s your business right now? What have you tried so far? If we solved this like this, what would that look like for you? Here’s how we’ll solve this bottle neck….” and then present your offer. It’s not easy but it is simple; don’t over complicate it. Do this and get to $1k a day within 30 days. You want my help setting this up? Send a DM.

• 
  CMJ_Pro (@CMJProus) reported 15 minutes ago

  @Namecheap is a moron service fu moron ****

• 
  jaseeey (@jaseeey) reported 17 minutes ago

  @Codebender_Cate Noooooo! The GoDaddy control panel is terrible and slow. I have a few domains there because Namecheap doesn't support all of the TLDs that I use. However, I'm certainly not disagreeing with the prices, it feels like the recent increases have been quite steep...

• 
  Cemal Coban (@uzakyolkaptani) reported 19 minutes ago

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

• 
  Sean Coker (@okcoker) reported 20 minutes ago

  I later found out, you can no longer even register this TLD on the Namecheap website because they have sunsetted them according to customer "support" 3/

• 
  Shawn (@shawn_dot_so) reported 21 minutes ago

  @elgermerlo @GoDaddy @Cloudflare GoDaddy isn’t even a consideration for me.. it’s Cloudflare first place or namecheap for TLDs that Cloudflare doesn’t support yet

• 
  Uday👨‍💻 (@uday_devops) reported 21 minutes ago

  @adahstwt I think namecheap is best but their renewal cost is not same that is the issue

• 
  Milan (@milanm_) reported 26 minutes ago

  @levelsio @Cloudflare I don't like Namecheap neither (their DNS setup sometimes causes my browser to freeze). But so far all domain providers I tried were generally ****, so I kind of made peace with the fact that they all suck. Why is @Cloudflare different?

• 
  Ajetomobi Jamiu (@JamiuAjetomobi) reported 26 minutes ago

  It doesn't matter how great your content or product is if your audience never sees it. ​The fix requires updating your technical security keys inside your domain host (like @GoDaddy or @Namecheap) so providers know you are a trusted sender.

• 
  Tommy Thomas (@0xTommyThomas) reported 27 minutes ago

  @adahstwt I’ve been using Namecheap for a while now, generally good integrations with other apps which make it easy to use. Pork bun is pretty decent too Will never understand why godaddy is called godaddy lol Squarespace in my experience is the most annoying to deal with for domain management tbh

• 
  Sarthak Shaurya (@alwaysSarthak) reported 30 minutes ago

  @nalinrajput23 I have tried namecheap and GoDaddy both but I never understood what is the difference between buying it from each

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

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

• 
  𝕂𝕖𝕒𝕣𝕤𝕒𝕣𝕘𝕖⚓☔👾🇺🇸 (@USS_Kearsarge_) reported 31 minutes ago

  FYI I won't be able to talk on Matrix for a while, because namecheap seems to be down and doesn't want to update their DNS with my new ip address... I guess I will need to make a server on discord after all

• 
  Matthias Reinholz (@MattReinholz) reported 32 minutes ago

  Interesting side-fact: they say the issue was about DNSSEC. However, in contrast to .com, @Namecheap doesn't let me configure DNSSEC for .de domains (not because of the current issue but generally). @grok does DENIC use a different layer/method of DNSSEC that doesn't allow configuring it on the registry level?

• 
  nicolasexc (@nicolasexcc) reported 33 minutes ago

  I'm a Global Admin locked out of my M365 tenant due to MFA with no recovery methods. Error 500121. I own the domain (registered in Namecheap) and can verify via DNS. Need urgent help resetting MFA. @MicrosoftHelps

• 
  Akinsete Motunrayo (@Harkinsete) reported 34 minutes ago

  I built my entire personal brand with AI and a clear process. Here is exactly what I built and how I did it, because you can do this too. What I Built ✅ Brand Strategy (mission, vision, values) ✅ Visual identity: colors, fonts, logo, brand guidelines ✅ A full pitch deck (12 slides) ✅ A speaker kit PDF ✅ A complete multi-page personal brand website ✅ A free lead magnet (a guide people can actually use) How I Built the Website Step 1: I planned before I touched anything I wrote down my brand colors, my fonts, my page structure, and what I wanted each page to do. Most people skip this. Everything breaks when you skip this. Step 2: I gave Claude one detailed prompt with my brand colors, fonts, pages, and copy. It returned a complete, mobile-responsive, multi-page website as a single HTML file. One file. Ready to deploy. The prompt I used: - "Build me a complete personal brand website as a single HTML file. Pages: Home, About, Services, Portfolio, Contact. Primary color [your hex], accent color [your hex], background [your hex]. Display font [font name], body font [font name]. Home page needs: dark hero with my name, photo on the right, tagline, and a CTA button. Services section. Impact numbers. Mobile responsive. No frameworks." Copy this, edit your details, and fine-tune as you want. Step 3: I pushed to GitHub: Free. This took me less than five minutes. Now every update I make is version-controlled and safe. Step 4: I deployed to Vercel for free. Connected my GitHub repo to Vercel and the site was live in under few minutes. This requires no hosting fees and nothing to manage. Step 5: I bought my domain on Namecheap - Searched for my full name and found the .com. Bought it for less than $12 for the year. Added it to Vercel. Updated the DNS settings on Namecheap. Waited 20 minutes. My website was live at my own domain. - Total cost: less than $12. - Total time to go live: under 2 hours. I am also working on a mobile app. A Progressive Web App, which means anyone can visit the URL on their phone and add it to their home screen like a real app. I may be running a live training in July where I will walk you through this entire process step by step to build your live website with a custom domain. If you have a phone and a laptop, you can do this. I documented everything the steps, the exact AI prompts, the domain checklist, the deploy instructions in a free PDF guide. Comment BRAND IDENTITY below and I will send it straight to your inbox. 💾SAVE THIS POST. You will want to come back to it. 🔁 SHARE IT with someone who keeps saying they need a website. The only thing standing between you and a professional online presence is the decision to start. Love and Light, Motunrayo 🤍

• 
  Aaron Douglas (@astralbodies) reported 38 minutes ago

  Waking up to @Namecheap being down is not how I wanted to finish off my weekend. I've never seen an outage like this before with them!

• 
  PKR | প্রশান্ত | پرشانتو (@prasanto) reported 39 minutes ago

  @baxiabhishek @Namecheap a whois issue, how come? BtW have had great experience with @dd24 for my domains

• 
  Andrew Warner (@AndrewWarner) reported 45 minutes ago

  Goodbye SquareSpace. Finally! I've hated having my wife's site on Squarespace. Some consultant set her up with it and I never had the patience to move it. On Sunday I told Claude Code to copy her site to a free @Cloudflare acount. Then I told Claude's Chrome plugin to figure out how to tell NameCheap where to point the domain. So satisfying.

• 
  Insignificant Developer (@insigdev) reported 48 minutes ago

  @tomilola_ng Namecheap sucks though 😭 Namecheap VPS is just Hostinger in a different coat. Low initial cost, ridiculous renewal prices as well, and a predatory domain expiration pipeline that funnels your forgotten domains straight to their marketplace auctions.

• 
  exitLife (@imsmokingloud) reported 57 minutes ago

  @not_puppycat ugh no idea i just bought the domain from namecheap.. do u know how i can fix it ;-;

• 
  Bennico (@baro0xx) reported 59 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!!!