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

• 
  O.G Obinna (@Obinna_Gates) reported 6 minutes ago

  @tomilola_ng @timithechef I’ve used hostinger way back in 19/20, Dreamhost VPS 22/23. I stuck with namecheap for their customer support. It’s the best & cheapest.

• 
  Shawn (@shawn_dot_so) reported 8 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

• 
  Johnmark Obiefuna (@jayhemz) reported 9 minutes ago

  @Nueltek a few minor inaccuracies here. > low-traffic websites the hypernova VPS subscription on Namecheap accomodates up to 10TB in bandwidth. that's more than enough for most traffic loads. > if the VPS goes down it's still more reliable than shared hosting > if one website gets compromised, the entire server could be at risk true. only if the exploit gets a hold of 'root' > 1 site experiences a major traffic spike cloudflare to the rescue > single point of failure? cloudflare to the rescue hehe.

• 
  CodeWithStu (@CodeWithStu) reported 9 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

• 
  Christopher Franko (@chrisjfranko) reported 12 minutes ago

  @Namecheap Oh ****... Nice! I thought I was tripping.

• 
  Fanboy.nz (@fanboynz) reported 15 minutes ago

  @Namecheap What did you find? based on the hundreds of domains it creates weekly on your service.

• 
  CAPED CRUSADER🦇 (@stilleclectic) reported 17 minutes ago

  @matthansbello Sigh, everything was originally done on namecheap but I’ve now just moved the dns to cloudflare. Waiting to see if that fixes the issue

• 
  nicolasexc (@nicolasexcc) reported 19 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

• 
  Clément Sauvage (@clementsauvage) reported 22 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

• 
  Blake Ryan (@blakefakhoury) reported 23 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.

• 
  Sinbad 🦂 (@Sinbaad777) reported 27 minutes ago

  wtf @Namecheap down

• 
  Kylobayd (@kylobtc) reported 27 minutes ago

  @John_ACW @Namecheap Good support shouldn’t feel this slow

• 
  Rajiya Sultana (@HeyRajiya) reported 29 minutes ago

  @ZimalDesigner_ godaddy and namecheap mostly, never had issues with either 👍

• 
  ChiseledCactus | Analyst (@chiseledcactus) reported 31 minutes ago

  @deanelazab @YayJayBae Hello! If it helps, it looks like it's running via cloudflare servers, and registered via "Namecheap". It still lists "Mediadroid LTD UK", with a "Jonathan hassall, but was dissolved a while back, so this is all sorts of shady. I imagine twitch and YouTube wouldn't be too happy with them continuously scraping content and causing issues, yeah? But is that even an option to try and rally to them?

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

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

• 
  Nitish (@nitishxk) reported 38 minutes ago

  today i learned how to make a website landing page using @claudeai added all my affiliate links in it namecheap domain for 11CAD uploaded index.html hosted on netlify added custom DNS verified SSL made 2 changes already site is mobile responsive **** beacons page

• 
  Garrett 🤠 (@garrett_makes) reported 38 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.

• 
  Georgii Tselkovskii (@Existentios) reported 40 minutes ago

  It has never been cheaper to build a startup. Claude for coding — $20/mo Supabase for backend — free Vercel for deploys — free Namecheap for domain — $20/yr Stripe for payments — % only GitHub for version control — free Resend for emails — free Clerk for auth — free Cloudflare for DNS — free PostHog for analytics — free Sentry for error tracking — free Upstash for Redis — free Pinecone for vector DB — free You can literally launch with ~$20/month. The hard part is no longer building. The hard part is getting people to care.

• 
  GatewayToDomains (@gatewaytodomain) reported 41 minutes ago

  @katerleonid No, I use Namecheap, Porkbun, Unstoppable, Regery, Netim, 101Domains based on the support for tld I want to register.

• 
  timagixe (@timagixe) reported 41 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

• 
  josh (@xcopydotexe) reported 41 minutes ago

  @uwunetes i know godaddy is a scam but why is namecheap bad?

• 
  Baber Rizvi (@BaberRizvi) reported 41 minutes ago

  @NamecheapCEO namecheap support on live chat keep asking for money just to reboot the server which is already down and they can't explain why it's down. We paid for reboot and server is still down now they are asking more money. This is insane. We are already paying for subscription and suffering business loss and they can't even tell us why our server is down for over 2 days now. Server down means all our websites are down and we can't run business. Need HELP

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

• 
  🇬‌🇱‌🇦‌🇸‌🇰‌🇮‌🇩‌ (@GLAsk1d) reported 43 minutes ago

  @TheTrunkTales @Namecheap Not at my PC rn so I can't check, but those all resolved to a login portal? 😳

• 
  Cemal Coban (@uzakyolkaptani) reported 45 minutes ago

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

• 
  Enjoyment Minister(SHINIGAMI🎮👩‍🚒) (@enjoymentmin) reported 45 minutes ago

  @dev_olayinka Im sure you had other cheaper options from the start. You know why you chose Namecheap. I will never use any other hosting server other than namecheap my bro.

• 
  Ajetomobi Jamiu (@JamiuAjetomobi) reported 48 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.

• 
  Arsi Hoxha (@ArsiHoxha_) reported 49 minutes ago

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

• 
  Sharat MR (@cosmos_genius) reported 52 minutes ago

  @captn3m0 I got the same email from namecheap. .in domain never had allowed whois protection AFAIK but for some reason the domain contacts where all weird in namecheap. Had to manually correct it. Didn't know the domain would be suspended so soon. one week is too short a period for warning