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	23 days ago
Centerville	Hosting	23 days ago
Noida	Domains	1 month ago
Purmerend	Domains	1 month ago
Istanbul	Hosting	2 months ago
Charleston	Hosting	2 months 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:

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

• 
  WOLF ✨️ (@Bilal_abbasid) reported 35 seconds ago

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

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

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

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

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

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

• 
  Kirtesh (@AKirtesh) reported 14 minutes ago

  My current indie hacker stack in 2026: - Claude for Coding - Stripe for Payments - GitHub for Version Control - Vercel for Deployment - Supabase for Backend - Clerk for Auth - Upstash for Redis - Pinecone for Vector DB - Resend for Emails - Namecheap for Domain - Cloudflare for DNS - PostHog for Analytics - Sentry for Error Tracking You can build and ship a complete startup from your bedroom in 2026. The barrier has never been lower 💪

• 
  Longevity World Cup (@LongevityWorldC) reported 19 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.

• 
  allmylife (@bhabhiezayn) reported 20 minutes ago

  @namesilo @Namecheap NameSilo dead rate is 60%+ for fresh domains (0-6mo) — domains are born dead. Namecheap fresh domains are 25% dead (normal setup delay). This means NameSilo domains were never intended to be used.

• 
  Hackology (@Hackology) reported 21 minutes ago

  Namecheap is facing some issues or their hosted sites are down ? @Namecheap

• 
  مركز مهارات الإبداع للتدريب (@cstcksa) reported 21 minutes ago

  @Namecheap Unfortunately, we have had an extremely poor experience with the current hosting provider. Despite multiple attempts to communicate through email and official support channels, we have received no response regarding our inquiries, technical support requests, or account management matters. The complete lack of communication and customer support has caused significant operational difficulties and has negatively affected the management of our website and educational platform. This level of service raises serious concerns about the provider's reliability, professionalism, and commitment to its contractual obligations. We respectfully request an immediate response to our pending requests and a prompt resolution of all outstanding issues. If the company is unable or unwilling to provide the required support, we request full cooperation in transferring the hosting account and related services to an alternative provider without further delay.

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

• 
  Georgii Tselkovskii (@Existentios) reported 23 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.

• 
  Hackology (@Hackology) reported 23 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 - 😶

• 
  David Maigari (@maigari_david) reported 24 minutes ago

  @Aditya_181105 Namecheap is a good one. Great customer support, too.

• 
  Jack Robert (@neutronmesh) reported 26 minutes ago

  @Namecheap @Emiliosantoss_ @omarvvvr Don't forget about the 7+ Hour (ongoing) outage with DNS changes. Thats a big seller

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

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

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 37 minutes ago

  millions of companies forget to renew their domain names every year. you can just buy the expired domain someone forgot about and get a premium on it. it’s called drop catching. where to find them discovery + filtering: → expireddomains[.]net → domcop → freshdrop → moonsy auctions + catching: → godaddy auctions → namecheap expired auctions → dynadot closeouts → namejet / snapnames → dropcatch (1,200+ registrars, best catch rate on contested names) the process: domain expires → grace period → “pending delete” → drops. once it’s pending delete (usually ~5 days before the drop) you can place a backorder. if more than one person wants it, it goes to auction. most of these never get listed for sale. catch the ones with real value (traffic, backlinks, brandable names).

• 
  Sanjay Lazar (@sjlazars) reported 39 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

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

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

• 
  Matthias Reinholz (@MattReinholz) reported 41 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?

• 
  Aaron (@aarons_takes) reported 42 minutes ago

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

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

• 
  LAMBO (@lambo_com) reported 42 minutes ago

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

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

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

• 
  Shant (@ShantDotMe) reported 52 minutes ago

  NC: 19:05:35 Hey Namecheap odd IP address access 20:06:15 IP address provided earlier does not belong to our service 20:27:17 Yes, the IP address does not belong to our company.

• 
  Sinbad 🦂 (@Sinbaad777) reported 55 minutes ago

  wtf @Namecheap down

• 
  Christine Harrington (@savvysaleslady) reported 57 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?