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.
This typically points to misconfigured .htaccess files or PHP memory limits. Log into KAS (Kunden-Administrations-System) and check your error logs under 'Logfiles'. Look for specific script names causing the crash. If you recently updated a CMS like WordPress, try renaming your .htaccess file temporarily to .htaccess_old via FTP. Check if your hosting package has sufficient PHP memory — upgrade if needed or optimize your database queries. Clear your site's cache if you're using plugins like WP Super Cache.
Double-check your FTP credentials in the KAS panel under 'FTP-Zugänge'. The hostname should be your domain or the server name provided during setup. If you're behind a restrictive firewall, switch from active to passive mode in FileZilla or your FTP client. Some users forget that FTP passwords are separate from KAS login credentials — reset them if unsure. Try using SFTP on port 22 instead, which works more reliably through corporate networks.
Your MySQL credentials might have changed after a password reset. In KAS, navigate to 'MySQL-Datenbank' and verify the database name, username, and hostname. The hostname is usually localhost, but some configurations require the specific server address shown in your panel. Export a backup before running repairs. If your site shows 'Error establishing database connection', your config file likely contains outdated information — update wp-config.php or your CMS equivalent with current credentials from KAS.