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	5 days ago
Centerville	Hosting	5 days ago
Noida	Domains	18 days ago
Purmerend	Domains	27 days ago
Istanbul	Hosting	28 days ago
Charleston	Hosting	28 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.

Namecheap Issues Reports

Latest outage, problems and issue reports in social media:

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

  @idxyllune To be honest I had no issues with namecheap so far, other than this one, but they did say there was a planned maintenance so...

• 
  Cemal Coban (@uzakyolkaptani) reported 36 seconds ago

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

• 
  👑𝘴𝓲ꪶꪶꪗ ᧁꪮꪮ𝘴ꫀ 👑 (@_SILLYGOOSE_ofl) reported 55 seconds ago

  @TheTrunkTales @GunGnome__ @Namecheap That dude sucks **** for bus fare, then walks.

• 
  Qirisiti Returns (@QirisitiReturns) reported 1 minute ago

  @Namecheap upon checking my hosting list there was nothing, talking to support they say that i have been refunded stellar, but there is no confirmation email of that. hmm, on the domain they said it was put on auction and i cant access it or recover it

• 
  WP Websites (@WebsitesWp) reported 1 minute 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

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

• 
  exitLife (@imsmokingloud) reported 8 minutes ago

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

• 
  Zara_Schneider (@ZSchneider76107) reported 9 minutes ago

  @MacdevM Mostly comes down to control and pricing for me Cloudflare and Namecheap usually stand out for clean management and no unnecessary upsells 🚀

• 
  Aaron (@aarons_takes) reported 11 minutes ago

  @MustaAras I think it comes down to normie's perceptions of Namecheap/Spaceship registrars vs GoDaddy. Very much IMHO.

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

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

  @GLAsk1d @Namecheap I got one domain taken down, it was a different registrar though. Namecheap doesn't appear to want to play ball.

• 
  based64 (@based64_eth) reported 21 minutes ago

  @faa0311 Whatever you do stay away from @Namecheap. Once they had an issue with SMS OTP and users were locked out for months with no recourse.

• 
  Hackology (@Hackology) reported 22 minutes ago

  @Namecheap Glad it's sorted ....imagine I spent 15 odd minutes figuring out what's wrong with my sites, never occurred to me it could be the host aswell - 😶

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 22 minutes ago

  GitHub — version control (free) Claude — coding ($20/mo) Namecheap — domain ($12/yr) Cloudflare — DNS (free) Vercel — deploy (free) Clerk — auth (free) Supabase — backend + database (free) Upstash — Redis (free) Pinecone — vector DB (free) Resend — emails (free) Stripe — payments (2.9% per transaction) PostHog — analytics (free) Sentry — error tracking (free) Total cost to run a startup: ~$20/month No servers. No DevOps team. No funding required. Just an idea and WiFi. There has never been a cheaper time to build. 🚀 Today is the best time to bet on yourself and build the things ⭐

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

• 
  LAMBO (@lambo_com) reported 26 minutes ago

  @AGreatDomain That's addressed to you @Namecheap Though Suzie is as good as the template churning morons who man your support system

• 
  Baber Rizvi (@BaberRizvi) reported 28 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

• 
  Dhairya (@dkare1009) reported 31 minutes ago

  📂 SaaS Stack ┃ ┣ 📂 Frontend ┃ ┣ 📂 React ┃ ┣ 📂 NextJS ┃ ┣ 📂 Vue ┃ ┣ 📂 TailwindCSS ┃ ┗ 📂 Shadcn UI ┃ ┣ 📂 Backend ┃ ┣ 📂 NodeJS ┃ ┣ 📂 Django ┃ ┣ 📂 Laravel ┃ ┣ 📂 FastAPI ┃ ┗ 📂 Express ┃ ┣ 📂 Database ┃ ┣ 📂 PostgreSQL ┃ ┣ 📂 MySQL ┃ ┣ 📂 MongoDB ┃ ┣ 📂 Redis ┃ ┗ 📂 Supabase ┃ ┣ 📂 Auth ┃ ┣ 📂 Clerk ┃ ┣ 📂 Auth0 ┃ ┣ 📂 Firebase Auth ┃ ┣ 📂 Supabase Auth ┃ ┗ 📂 NextAuth ┃ ┣ 📂 Payments ┃ ┣ 📂 Stripe ┃ ┣ 📂 Paddle ┃ ┣ 📂 Dodo Payments ┃ ┣ 📂 Lemon Squeezy ┃ ┗ 📂 Polar ┃ ┣ 📂 Emails ┃ ┣ 📂 Resend ┃ ┣ 📂 SendGrid ┃ ┣ 📂 Mailgun ┃ ┣ 📂 Postmark ┃ ┗ 📂 Amazon SES ┃ ┣ 📂 Storage ┃ ┣ 📂 AWS ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 Google Cloud Storage ┃ ┣ 📂 Supabase Storage ┃ ┗ 📂 Uploadcare ┃ ┣ 📂 Deployment ┃ ┣ 📂 Vercel ┃ ┣ 📂 Netlify ┃ ┣ 📂 Railway ┃ ┣ 📂 Render ┃ ┗ 📂 AWS ┃ ┣ 📂 Domains and DNS ┃ ┣ 📂 Namecheap ┃ ┣ 📂 Hostinger ┃ ┣ 📂 Cloudflare DNS ┃ ┣ 📂 Google Domains ┃ ┗ 📂 SiteGround ┃ ┣ 📂 Analytics ┃ ┣ 📂 Google Analytics ┃ ┣ 📂 Plausible ┃ ┣ 📂 PostHog ┃ ┣ 📂 Mixpanel ┃ ┗ 📂 DataFast ┃ ┣ 📂 Monitoring ┃ ┣ 📂 Sentry ┃ ┣ 📂 LogRocket ┃ ┣ 📂 Datadog ┃ ┣ 📂 NewRelic ┃ ┗ 📂 UptimeRobot ┃ ┣ 📂 DevOps ┃ ┣ 📂 Docker ┃ ┣ 📂 Kubernetes ┃ ┣ 📂 GitHub Actions ┃ ┣ 📂 CI CD ┃ ┗ 📂 Terraform ┃ ┣ 📂 Search ┃ ┣ 📂 Algolia ┃ ┣ 📂 Meilisearch ┃ ┣ 📂 Elasticsearch ┃ ┣ 📂 Typesense ┃ ┗ 📂 OpenSearch ┃ ┣ 📂 AI Integration ┃ ┣ 📂 OpenAI API ┃ ┣ 📂 Anthropic API ┃ ┣ 📂 Replicate ┃ ┣ 📂 HuggingFace ┃ ┗ 📂 Gemini API ┃ ┣ 📂 Integrations ┃ ┣ 📂 Zapier ┃ ┣ 📂 Make ┃ ┣ 📂 n8n ┃ ┣ 📂 Pabbly ┃ ┗ 📂 Webhooks ┃ ┣ 📂 Security ┃ ┣ 📂 SSL ┃ ┣ 📂 Cloudflare ┃ ┣ 📂 WAF ┃ ┣ 📂 Rate Limiting ┃ ┗ 📂 Secrets Management ┃ ┣ 📂 Marketing ┃ ┣ 📂 Search Console ┃ ┣ 📂 Outrank ┃ ┣ 📂 Buffer ┃ ┣ 📂 Analytics ┃ ┗ 📂 Kit ┃ ┗ 📂 Customer Support ┣ 📂 Intercom ┣ 📂 Crisp ┣ 📂 Zendesk ┣ 📂 Tawk ┗ 📂 HelpScout

• 
  Big-Abdul (@BigAbdulWeb3) reported 33 minutes ago

  - Claude = coding. ($20/mo) - Supabase = backend. (Free) - Vercel = deploying. (Free) - Namecheap = domain. ($12/yr) - Stripe = payments. (2.9%/transaction) - GitHub = version control. (Free) - Resend = emails. (Free) - Clerk = auth. (Free) - Cloudflare = DNS. (Free) - PostHog = analytics. (Free) - Sentry = error tracking. (Free) - Upstash = Redis. (Free) - Pinecone = vector DB. (Free) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

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

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

• 
  Favour Light (@RealLight47) reported 38 minutes ago

  @Namecheap has probably the worst customer support I've ever had to deal with. I've been locked out of my account and haven't gotten a single reply to any of the emails I've sent.

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

• 
  K S (@kj_kjato) reported 38 minutes ago

  @Namecheap Furthermore, I will explode that you’ve never invested anything and immediately replied that claims are unfounded when clearly they are not. You don’t want me to expose you and your bullshit customer service.😡😡

• 
  jaseeey (@jaseeey) reported 39 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...

• 
  WOLF ✨️ (@Bilal_abbasid) reported 40 minutes ago

  @Namecheap Reply to the ******* mails you pathetic customer support clowns

• 
  Sharat MR (@cosmos_genius) reported 47 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

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

  @NamecheapCEO I used Namebase (owned by @Namecheap) to manage my funds. Three months ago, you sold the platform without notifying your clients. Since Namecheap sold the platform, I have lost access to my funds, and this issue has now been ongoing for more than three months.

• 
  Shubh Jain (@shubh19) reported 49 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?

• 
  CMJ_Pro (@CMJProus) reported 56 minutes ago

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

• 
  Adel Bucetta (@adelbucetta) reported 58 minutes ago

  @rozzabuilds usually buy from registrar first, then use a registrar-agnostic service like cloudflare for namecheap or google domains. don't need another middleman between me and my registrars