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	22 days ago
Centerville	Hosting	22 days ago
Noida	Domains	1 month 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:

• 
  Abu Fatimah.Dev (@Hameed_360) reported 49 seconds ago

  @Namecheap has never failed me

• 
  Umesh Kumar Yadav (@Umesh__digital) reported 1 minute 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 ⭐

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

• 
  𝕂𝕖𝕒𝕣𝕤𝕒𝕣𝕘𝕖⚓☔👾🇺🇸 (@USS_Kearsarge_) reported 6 minutes 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...

• 
  elena (@elephnaburky) reported 12 minutes ago

  @ChrisProd_ @Echotheglitch8 What Glitch is probably doing right now is probably consulting with the Registrar (NiceNIC, which they also don't use. Glitch uses Tucows, Namecheap, and GoDaddy) to get the domain taken down. Or, they might not be doing anything. Who knows.

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

• 
  Gamingtronium (@Gamingtronium) reported 16 minutes ago

  @bybydev Never tried namecheap! 🤧

• 
  Tommy Thomas (@0xTommyThomas) reported 17 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

• 
  Great Bin Elroi (@OgaGreat) reported 19 minutes ago

  International companies understands customer care ! @Namecheap can reply even at 12 midnight ! That is a company that is customer oriented .

• 
  Arsi Hoxha (@ArsiHoxha_) reported 19 minutes ago

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

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

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

• 
  ChiseledCactus | Analyst (@chiseledcactus) reported 21 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?

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

• 
  Ehsan (@acadictive) reported 24 minutes ago

  @BacLeodiv i always buy from namecheap. i like their ui and service. btw, lets also connect.

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

• 
  CMJ_Pro (@CMJProus) reported 28 minutes ago

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

• 
  Rozzabuilds (@rozzabuilds) reported 32 minutes ago

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

• 
  Aaron Douglas (@astralbodies) reported 37 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!

• 
  ∴ (@irucsbo) reported 39 minutes ago

  @Namecheap Why don't I got access to my funds for over 3 months? Why is @Namecheap support ignoring me?

• 
  SpamAuditor (@SpamAuditor) reported 40 minutes ago

  Watch for emails pretending to be support at @Namecheap, thankfully NameCheap has good SPF records in place, fake storage is full emails. If you get one of these, tell your email administrator to tighten up their SPF checks.@DatalixDE IP address 45.11.229.]113 this time

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

• 
  Polyvalent kaizen 🀄️ (@0xKachi) reported 43 minutes ago

  Is namecheap hosting down? My websites won’t load

• 
  Dante (@thedntx) reported 47 minutes ago

  @TTrimoreau Porkbun if u want clean interface. Namecheap for bundles. Never godaddy, thats 2010 behavior.

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

• 
  Nitish (@nitishxk) reported 48 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

• 
  Chidi inyama (@chidimarvel) reported 50 minutes ago

  @RaenestApp trying to make a payment on namecheap, getting insufficient balance error when there are funds on my card. Please what is going, your support has not replied livechat for hours

• 
  RGK🌹 (@rgk_degen) reported 53 minutes ago

  1 prompt. Claude builds a $2,000/week website from scratch. Here’s the exact system, step by step. Most people build sites the wrong way. They hire a developer for $3,000–8,000. Wait 3–6 weeks. Get something generic. Then pay another $500/month to maintain it. The new way: 1 prompt. 45 minutes. Launch-ready. WHAT YOU’RE BUILDING A niche service landing page conversion-optimized, Stripe-integrated, SEO-structured that targets a local or vertical market with $200–500 average order value. Target: $2,000/week minimum by week 4. THE PROMPT ARCHITECTURE Your 1 prompt has 4 layers: → Layer 1 Business context “I’m building a [niche] service site targeting [city/audience]. Average order: $[X]. Primary CTA: book a call / buy now.” → Layer 2 Stack spec “Build in HTML/CSS/JS, Stripe Checkout embedded, Calendly widget for booking, Google Analytics 4 ready.” → Layer 3 Content skeleton “Homepage: hero with pain point + 3 benefits + social proof section + FAQ + CTA. No blog. No filler.” → Layer 4 Conversion rules “Above the fold: 1 headline, 1 subheadline, 1 button. No nav clutter. Mobile-first. Load under 2 seconds.” Paste all 4 layers into Claude as 1 message. Hit send. WHAT CLAUDE DELIVERS IN 45 MINUTES → Full HTML file, production-ready → Stripe Checkout flow embedded → Mobile layout done → Meta tags + OG data for social sharing → Contact form wired to Formspree (free tier) You copy the output. Drop into Netlify or Vercel. Live in 8 minutes. Domain: $12/year on Namecheap. Hosting: $0. Total launch cost: $12. REALISTIC REVENUE PROGRESSION Week 1 Site live. Run $50 in Meta ads to local audience. 3 conversions at $150 = $450. Week 2 Add Google Business Profile. 2 organic calls. 1 closes. $200. Week 3 Raise price 20%. Run retargeting on the 60 visitors who didn’t convert. $600. Week 4 Email the 3 week-1 buyers. Ask for referrals. 2 referrals at $250 = $500 + repeat. Total week: $2,100+. The site didn’t change. The traffic system compounded.

• 
  Phil (@0xPhilH) reported 57 minutes ago

  @milanm_ @levelsio @Cloudflare To add here, since CFs offices are in France, they overcomply with every bs EU request, even if you host a service that is US only. They won't do that for the content part, so namecheap registar + CF dns + CF CDN is actually best of both worlds combo.

• 
  The Smart Ape 🔥 (@the_smart_ape) reported 58 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).