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.
After switching nameservers or updating DNS records, your site might show errors for up to 48 hours. This happens because changes need time to propagate globally. Clear your browser cache and try accessing from a different device or network. If the issue persists beyond two days, check your domain settings in the control panel—incorrect A-records or missing entries often cause problems.
Connection timeouts during file transfers usually point to firewall restrictions or passive mode issues. Switch your FTP client to passive mode (PASV) in settings—active mode rarely works behind routers. If uploads still fail, your local antivirus might be blocking port 21. Try FileZilla with explicit FTP over TLS and verify you're connecting to the right hostname from your package details.
The 'Error establishing database connection' message typically means wrong credentials in wp-config.php. Log into your control panel, navigate to database settings, and confirm the database name, username, and host address match exactly what's in your config file. The host is usually 'localhost' but some packages require the specific server name. After updating, give it a few minutes—database servers sometimes need a moment to recognize new connections.
If you keep getting logged out while managing your hosting, check that your browser accepts cookies from strato.de. Private browsing modes and aggressive privacy extensions often interfere with session management. Clear cookies specifically for the domain, disable extensions temporarily, and try again. Using multiple tabs simultaneously can also trigger premature logouts.