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 MIRhosting control panel returns a blank page or times out, start by clearing your browser cache and cookies. Try a different browser — Chromium-based ones tend to behave better with hosting dashboards. Check whether the issue is specific to your account by opening the panel in an incognito window. If the page still won't load, the problem might be a stale DNS record on your end: flush your local DNS cache with ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS.
A failed login usually comes down to one of three things: wrong credentials, a session conflict, or two-factor authentication acting up. Reset your password through the official recovery form rather than guessing. If 2FA codes aren't accepted, make sure your device clock is synced — TOTP codes are time-sensitive and a drift of 30 seconds breaks them. Clear site data for the domain and try again.
When your hosted server stops responding, first check whether the issue is on your machine or at the data center. Run a basic ping to your server's IP. If packets drop entirely, try traceroute to identify where the connection breaks. Log into the MIRhosting client area to check the server status — sometimes a reboot task is stuck in queue and needs manual cancellation before the server comes back online.
Spikes in ping or sluggish response times from your hosted site can come from route congestion between your ISP and the data center. Run an MTR report (mtr yourdomain.com) to pinpoint exactly which hop is introducing delay. If the bottleneck is outside the MIRhosting network, contact your ISP with the report. On the server side, check resource usage — a CPU spike caused by a runaway process will inflate response times just as badly as a network issue.
After updating A records or nameservers, propagation typically takes up to 48 hours, but if nothing changes after that window, something is wrong. Double-check the TTL value on the old record — a high TTL like 86400 means resolvers cached the old value for a full day. Use a public DNS resolver like 8.8.8.8 to query your domain and confirm what's actually being returned. If the panel shows the correct record but it still doesn't resolve, open a ticket with the support team and include the full dig output.