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	15 days ago
Centerville	Hosting	15 days ago
Noida	Domains	27 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:

• 
  Dhairya (@dkare1009) reported 1 minute 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

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

  @Namecheap So, you are not going to take action against the domain simply because it removed the subdomain? The root domain is the threat, and it continues to create subdomains with this content. This is not an isolated issue.

• 
  Sanjay Lazar (@sjlazars) reported 5 minutes ago

  @baxiabhishek @Namecheap Name cheap is just that ! Cheap !! I’ve had a similar experience a year ago, and I never went back to them. Buy domains elsewhere and pay a wee bit more for peace of mind

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

• 
  Kingsley Ibietela Felix (@Iamkingsleyf) reported 11 minutes ago

  @adahstwt Namecheap, first on the list should never be there

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

• 
  Qirisiti Returns (@QirisitiReturns) reported 18 minutes 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

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

• 
  Imagine-This (@ImagineThisSM) reported 23 minutes ago

  @Namecheap hi, all my sites and applications are down, whats going on. please update us right away

• 
  Adam Holter (@AdamHoltererer) reported 24 minutes ago

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

• 
  Resolver Vicky | Dev 🔧 (@resolvervicky) reported 30 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?

• 
  Wiz (@wizminar) reported 32 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

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

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

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

• 
  Christine Harrington (@savvysaleslady) reported 34 minutes ago

  My domain was shut down by @GoDaddy on May 10th. No idea why & the domain was paid up for a year back in Feb. 2026. I’ve called twice a day trying to get this resolved with GoDaddy. Absolutely a waste of my time. I moved the domain today to @Namecheap but GoDaddy is now taking 5-7 days to initiate the transfer. I’ve reached out to @GoDaddyHelp numerous times with no response. Can you imagine providing such poor service?

• 
  John van Rijck (@John_ACW) reported 35 minutes ago

  Does @Namecheap pay their support team based on the amount of minutes they're in an active chat or what? Every support chat opens with: "Please allow me 10-12 minutes to check" Terrible support

• 
  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

• 
  Mahdi Ezzeddine (@MahdiEzz_code) reported 41 minutes ago

  My domain has become too expensive I can't afford it (it wasn't that much when I bought it in 2023, it's getting expensive with each year) soo, I'm thinking of switching domains, and using cloudflare this time not namecheap but I'm gonna lose all my seo progress damn, idk what do you think guys?

• 
  Bhavya (@Bhavyaztwt) reported 41 minutes ago

  @Namecheap No problem man We gng 💥

• 
  David O. Ehibor (@grayontop_) reported 42 minutes ago

  @AlfinCodes Namecheap altho I had a bad experience with them and it took time to get resolved. Cloudfare is a better option.

• 
  Paul Sant · Telecodex (@YouPulseX) reported 43 minutes ago

  @rmastiyev @Namecheap 8080 works, 80 times out, fresh installs logged - "back to the same ticket" is not a network review.

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

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

• 
  Pratik 📈 (@PratikSinhatwt) reported 46 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) Total monthly cost to run a startup: ~$20 There has never been a cheaper time to build.

• 
  CMJ_Pro (@CMJProus) reported 48 minutes ago

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

• 
  Ken 🧙 (@thekenndubisi) reported 49 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.

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

• 
  Hackology (@Hackology) reported 54 minutes ago

  @Namecheap VPS CP is now responsive, even that was not loading rest even namecheap site appears to off ... VPS etc all down , even the IP associated with it

• 
  Formerly Exit 2 🏴 ☮️ (@SchraderValves) reported 56 minutes ago

  @YourHornedGod I used to use Namecheap, never had a problem. Don't know if they are still good

• 
  Sarthak Shaurya (@alwaysSarthak) reported 59 minutes ago

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