Where most complaints about this service are coming from, over the last 24 hours.
Shows where the service URL was unreachable during the detected outage periods. Percentages indicate the share of failed checks from monitoring locations in each country.
Tap what’s going wrong — one click helps thousands of others see the outage.
If the hosting control panel refuses to open or stalls on a blank screen, the issue is almost always browser-related. Clear cached data and cookies, then reload the page. If that doesn't help, try a different browser entirely — Chromium-based browsers tend to work best with cPanel-style interfaces. Disable extensions one by one, since ad blockers and script blockers frequently break dashboard functionality.
Wrong credentials are the obvious culprit, but not the only one. Check that Caps Lock is off and that you're using the correct account type — hosting login, client area login, and server SSH credentials are all separate. If the password reset email doesn't arrive, check your spam folder and wait a few minutes before requesting another. Repeated failed login attempts can trigger a temporary IP block, so switching networks can help confirm whether that's the case.
A 500 error on your hosted site usually points to a misconfigured .htaccess file or a PHP memory limit being hit. Access your file manager through the control panel and check recent changes to .htaccess. Raising the PHP memory limit via the PHP configuration settings often resolves unexplained crashes. If the server itself is unreachable via SSH, wait a few minutes — brief maintenance windows can cause short outages.
Large file uploads through the browser-based file manager frequently time out or freeze the interface. Use an FTP client instead — it handles large transfers more reliably and gives you real progress feedback. Set passive mode in your FTP client settings if the connection stalls at the directory listing stage.
After updating nameservers or DNS records, propagation typically takes between one and 24 hours. If your own device keeps resolving the old address, flush the local DNS cache — on Windows use ipconfig /flushdns, on macOS use the appropriate terminal command. Switching to a public DNS resolver temporarily can confirm whether propagation has completed on external networks.