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	13 days ago
Centerville	Hosting	13 days ago
Noida	Domains	26 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:

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

• 
  Sahil Jaiswal (@Sahil_Jaiswal02) reported 1 minute ago

  Godaddy is a **** I should have gone with hostinger or namecheap My site is down after 2 days of getting it …even after successfull verification 😤 No support, no person available @GoDaddy

• 
  Alex 🇵🇸 (@alexjaxuk) reported 1 minute ago

  @receipts_lol But people are praying attention. I've been a lifelong namecheap customer but after what they did to you guys I've moved everything to porkbun

• 
  elena (@elephnaburky) reported 2 minutes ago

  Glitch uses 3 different registrars, and never have their organization name publicly listed. - GoDaddy (Glitch Store, TheWackyWatch) - NameCheap (TheProphecy, ParkPlanet, Store Redirects) - Tucows (GlitchProd) They don't use NiceNIC, which is what the Solver site uses. 10/20

• 
  Johnmark Obiefuna (@jayhemz) reported 3 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.

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

• 
  Steve Bailey (@stevebaileyseo) reported 6 minutes ago

  The most powerful thing a platform can do is make you feel like you don't need your guard up. Namecheap does that. Not by promising the world. By just... not being awful.

• 
  Abu Fatimah.Dev (@Hameed_360) reported 7 minutes ago

  @Namecheap has never failed me

• 
  Dante (@thedntx) reported 9 minutes ago

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

• 
  rodrigo (@_whiletruedo) reported 12 minutes ago

  @Namecheap thx for the heads up! I'll reach out the support. but don't be alarmed bc you're my first choice to buy domain sice ever! and I'll continue to buy!

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

  .@Namecheap stole my funds and refuses to provide a real solution or proper support. Extremely disappointing experience with a company I trusted for years. Criminal organization. Avoid at all costs.

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

  FYI I won't be able to talk on Matrix for a while, because namecheap seems to be down and doesn't want to update their DNS with my new ip address... I guess I will need to make a server on discord after all

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

• 
  Devon Wayne (@TheDevonWayne) reported 22 minutes ago

  @PratikSinhatwt namecheap never godaddy ever again

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

• 
  Spencer Heckathorn (@mrhobbeys) reported 32 minutes ago

  @BacLeodiv Everyone hates on Godaddy but I e been there 20 years and only had one major issue related to their migration in the early 2010s. Hundreds of domains and 40ish customers. No complaints. I also use the others. Namecheap is up and down on their support. Cloudflare I thought of as expensive. But honestly they all are now.

• 
  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

• 
  Michael Knight (@michaelmknight) reported 38 minutes ago

  @cPanel Hi, I upgraded from ImunifyAV+ to Imunify360. I’m now being asked for a license key. I wasn’t provided one and I can’t find a key anywhere in your Client Area and under Orders/Licenses. Your support states to contact Namecheap and is sending me around in circles, but it's nothing to do with them as I purchased the upgrade from you and I can't send a support ticket. Any help would be appreciated.

• 
  K S (@kj_kjato) reported 42 minutes ago

  @Namecheap I just wanted to let you guys know that I’ve contacted my local law-enforcement to stop some websites that you’re hosting from scamming any further. I’ve asked repeatedly fake the domain down and you refuse now I’m pursuing legal action.😡😡😡😡

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

• 
  Bogey Wilcox (@brasscogg) reported 43 minutes ago

  Unverified conspiracy theory: GoDaddy holds all these inactive domains through a shell company so they can charge finders fees and commission to “find” the owner of the domain, themselves Namecheap would never stoop to such loser levels

• 
  Christopher Franko (@chrisjfranko) reported 43 minutes ago

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

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

• 
  👑𝘴𝓲ꪶꪶꪗ ᧁꪮꪮ𝘴ꫀ 👑 (@_SILLYGOOSE_ofl) reported 49 minutes ago

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

• 
  Mehmet Ali Demirci (@malidemirci_gm) reported 49 minutes ago

  @Namecheap unable to solve CDN and slow site problems for over two days!

• 
  Jack Robert (@neutronmesh) reported 50 minutes ago

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

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

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

• 
  Cemal Coban (@uzakyolkaptani) reported 55 minutes ago

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

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