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 Yourhosting control panel returns a blank page or times out, start by clearing your browser cache and cookies. Try a different browser — Chrome and Firefox handle the panel best. If the issue persists across browsers, check whether your ISP is blocking port 8443 or 2083, which the panel often relies on. Switching to a wired connection can also rule out local network instability.
A failed login is usually caused by one of three things: a cached session conflict, an expired password, or a browser extension interfering with the form. Clear autofill data, disable extensions temporarily, and try again. If you get an 'invalid credentials' error but the password is correct, use the password reset link — the system may have locked the account after repeated failed attempts.
Failed payments at checkout are almost always a card authorization issue rather than a platform bug. Make sure your bank hasn't flagged the transaction as foreign — Yourhosting processes payments through EU-based gateways. Try a different card or use PayPal as a fallback. If the charge appears on your statement but the account isn't upgraded, contact support with the transaction ID; the payment likely needs manual reconciliation.
An SSL error after setup usually means DNS hasn't fully propagated yet. Wait up to 24 hours before assuming something is broken. If propagation is complete but the browser still shows a certificate warning, log into the panel and reissue the certificate manually. Make sure the domain points to the correct server IP — a mismatch between DNS A record and server address will cause validation to fail every time.
If pages load slowly or ping to the server is unusually high, run a traceroute to identify where the delay occurs. A bottleneck at the first few hops points to a local network issue; a bottleneck near the destination suggests server-side load. Check PHP memory limits and database query times in the panel — a single slow query can drag down the entire site response time.