Namecheap 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:

• 
  Christopher Franko (@chrisjfranko) reported 1 minute ago

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

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

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

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

• 
  anderson (@U__anderson) reported 9 minutes ago

  @John_ACW @Namecheap how many businesses with actually good support can you even name? probably none

• 
  Emad (@emad_maker) reported 12 minutes ago

  @ardent__dev I've been using Namecheap and had good experience. They offer competitive pricing and reliable service.

• 
  elena (@elephnaburky) reported 14 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.

• 
  Eric (@realfunnyeric) reported 16 minutes ago

  @Dynadot @Namecheap Eh. Gotta be a better way. Everyone trying to hang on to their customers. Taking them hostage. Maybe I’ll build a tool that does it. ¯\_(ツ)_/¯

• 
  Sahil Jaiswal (@Sahil_Jaiswal02) reported 16 minutes 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

• 
  D̸̖͌a̶̞͊r̷̙͒k̶͇͝ḽ̸̃ÿ̸͈́ (@ADesignerDarkly) reported 17 minutes ago

  @Hexangelo5 You are right about that! Pulsechain,com is registered through there, as are lots of other pulsechain project websites. While Namecheap built its brand on privacy advocacy (e.g., fighting for customer data protection in courts), control now sits largely with a Luxembourg-based PE giant whose incentives are financial returns, not ideological privacy maximalism. The registrant data required by ICANN lives in a system where EU corporate oversight meets US legal demands. In an era of rising data breaches, surveillance, and regulatory flux, relying on any large registrar under PE ownership means trusting opaque boardroom decisions with your identity footprint. Diversifying to independent or privacy-first alternatives reduces single points of failure.

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

• 
  Tung 🟠🔴 ⚔ (@Tng40234067) reported 19 minutes ago

  Imagine losing your online identity due to a registrar issue. This happens because centralized registrars like GoDaddy or Namecheap essentially rent domains to users, who have limited control over their ownership. If the registrar suspends, seizes, or loses the domain, the user is left with nothing. Doma Protocol solves this by tokenizing domains, allowing true ownership and transferability. * Tokenized domains are stored on-chain * Transferable without registrar involvement * Owners have full control over their assets This shift in domain ownership dynamics has significant implications for the future of online identities and assets. With a total network value of $27.52M and 48,421 wallets holding tokenized domains, the foundations of a new paradigm are being laid. A new era of digital ownership is unfolding. @domaprotocol @D3inc #Web3Domains

• 
  John van Rijck (@John_ACW) reported 20 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

• 
  Adel Bucetta (@adelbucetta) reported 21 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

• 
  Mr. Niba (@Nousername_ah) reported 25 minutes ago

  I’ve usually had very good experiences with @Namecheap and their customer service but today I have been on with a live agent for more than 30 mins and they can’t resolve my issue after wasting my time they are now transferring me to a different department. SMH

• 
  Big-Abdul (@BigAbdulWeb3) reported 30 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.