1. Home
  2. ❯
  3. Companies
  4. ❯
  5. Namecheap
Namecheap

Namecheap status: hosting issues and outage reports

No problems detected

If you are having issues, please submit a report below.

Full Outage Map

Namecheap provides services on domain name registration, and offer for sale domain names that are registered to third parties (also known as aftermarket domain names). It is also a web hosting company.

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.

At the moment, we haven't detected any problems at Namecheap. Are you experiencing issues or an outage? Leave a message in the comments section!

Most Reported Problems

The following are the most recent problems reported by Namecheap users through our website.

  • 57% Hosting (57%)
  • 43% Domains (43%)

Live Outage Map

The most recent Namecheap outage reports came from the following cities:

CityProblem TypeReport Time
Tuxtla Domains 9 days ago
Centerville Hosting 9 days ago
Noida Domains 22 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:

  • codewith55
    Mohit (@codewith55) reported

    Total monthly cost to run a startup: $20 - 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)βœ… There has never been a cheaper time to build

  • Existentios
    Georgii Tselkovskii (@Existentios) reported

    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.

  • ShantDotMe
    Shant (@ShantDotMe) reported

    Hey @Namecheap are we trying to outdo @bluehost as worse customer service?! It has been a month and a week since I opened a security issue ticket with them (and still no reply), but your livechat isn't doing any better atm.

  • QirisitiReturns
    Qirisiti Returns (@QirisitiReturns) reported

    This is the issue. i hope i don't sound entitled. On @Namecheap I had a domain that was expiring in a day, and stellar hosting had already expired. so i added domain renewal and hosting renewal yearly subscription, plus helping services to my cart and paid 45 USD thread..

  • uzakyolkaptani
    Cemal Coban (@uzakyolkaptani) reported

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

  • QArtify28
    QARTIFY (@QArtify28) reported

    @vivoplt Namecheap is good, but if you want best service after purchase, GoDaddy

  • USS_Kearsarge_
    π•‚π•–π•’π•£π•€π•’π•£π•˜π•–βš“β˜”πŸ‘ΎπŸ‡ΊπŸ‡Έ (@USS_Kearsarge_) reported

    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

  • kj_kjato
    K S (@kj_kjato) reported

    @Namecheap Never once have you reached out to me properly to verify my claims you know how to find my contact information. I’ve already told you where it is not affiliated with that garbage. Please reach out and rectify the problem. I don’t want to call the police department again😑😑😑

  • y1vl3vy
    LND (@y1vl3vy) reported

    @the_smart_ape Tbh I have nothing to do with it. There are no clear alternatives for gmail. Every other email registrar could fall as well so no point into thinking that switching from google is gonna save you for sure. Namecheap can go down, microsoft as well and every other ******* email registrar.

  • YouPulseX
    Paul Sant Β· Telecodex (@YouPulseX) reported

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

  • legacyunchain
    Legacy (@legacyunchain) reported

    @yfly58 Nice one. Boss I need help, I'm trying to set up a business mail. I bought a domain on namecheap, connected it to the Google workshop. I have been trying to activate the Gmail but the MX record I created on namecheap is not working and the activation is failing.

  • Obinna_Gates
    O.G Obinna (@Obinna_Gates) reported

    @tomilola_ng @timithechef I’ve used hostinger way back in 19/20, Dreamhost VPS 22/23. I stuck with namecheap for their customer support. It’s the best & cheapest.

  • JennaeIlIisEsq
    Jenna. Ellis (@JennaeIlIisEsq) reported

    @Namecheap @TeamDreier Pls what is going on with namecheap hosting ? My hosting has not been working since yesterday….. fix it pls

  • ShantDotMe
    Shant (@ShantDotMe) reported

    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.

  • ShantDotMe
    Shant (@ShantDotMe) reported

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

  • based64_eth
    based64 (@based64_eth) reported

    @faa0311 Whatever you do stay away from @Namecheap. Once they had an issue with SMS OTP and users were locked out for months with no recourse.

  • milanm_
    Milan (@milanm_) reported

    @levelsio @Cloudflare I don't like Namecheap neither (their DNS setup sometimes causes my browser to freeze). But so far all domain providers I tried were generally ****, so I kind of made peace with the fact that they all suck. Why is @Cloudflare different?

  • CDomainer
    Charles (@CDomainer) reported

    @BTCUFO It’s really **** that @Namecheap don’t let users list .ai domain names on their platform

  • prasanto
    PKR | ΰ¦ͺ্রঢান্ঀ | ΩΎΨ±Ψ΄Ψ§Ω†Ψͺو (@prasanto) reported

    @baxiabhishek @Namecheap a whois issue, how come? BtW have had great experience with @dd24 for my domains

  • 0xKachi
    Polyvalent kaizen πŸ€„οΈ (@0xKachi) reported

    Is namecheap hosting down? My websites won’t load

  • FriendOfTheInst
    πŸ›‘οΈShir Khorshid Noor Cyber UnitπŸ›‘οΈ (@FriendOfTheInst) reported

    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

  • monsterTRAPxx9
    monsterTrapXx9 (@monsterTRAPxx9) reported

    @Namecheap @TomoLifeUpdates you guys suck ***** for suspending neocities when they werent even mentioned in the court order. We are actively avoiding ur service & dissuading ppl from using it

  • TomoLifeUpdates
    Tomodachi Life Updates (@TomoLifeUpdates) reported

    @Namecheap We'd appreciate it if your abuse team could take a look at tomodachilife[.]gg and tomoez[.]com (X has flagged both domains in posts already). We've received multiple reports from users who believed these sites were associated with an official web version/port of Nintendo's Tomodachi Life. The sites appear to be hosting a CAPTCHA scam disguised as an in-game Tomodachi Life menu, using Nintendo's branding and trademark in a way that may mislead users. A separate domain hosting the same scam, tomodachilife[.]cc, has already been taken down following reports. Could someone from your team review these domains and their operators or direct us to the appropriate reporting channel?

  • ennycodes
    π•―π–Šπ–›π•°π–“π–“π–ž (@ennycodes) reported

    πŸ“‚ 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

  • MahdiEzz_code
    Mahdi Ezzeddine (@MahdiEzz_code) reported

    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?

  • JennaeIlIisEsq
    Jenna. Ellis (@JennaeIlIisEsq) reported

    @Namecheap @TeamDreier Pls what is going on with namecheap hosting ? My hosting has not been working since yesterday….. fix it pls

  • clementsauvage
    ClΓ©ment Sauvage (@clementsauvage) reported

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

  • Sudoku1016705
    John Kenn (@Sudoku1016705) reported

    @TTrimoreau Godaddy is better to buy domain, I never found pricing diff between namecheap and godaddy

  • cstcksa
    Ω…Ψ±ΩƒΨ² Ω…Ω‡Ψ§Ψ±Ψ§Ψͺ Ψ§Ω„Ψ₯Ψ¨Ψ―Ψ§ΨΉ Ω„Ω„Ψͺدريب (@cstcksa) reported

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

  • TheTrunkTales
    The Trunk Tales (@TheTrunkTales) reported

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