Is Zabbix Down? Live status & outage reports

Service info and troubleshooting

Server Not Responding or Timeout Errors

When the monitoring dashboard shows timeout messages or fails to connect, first check if the Zabbix server process is actually running. SSH into your server and execute systemctl status zabbix-server to verify the service state. If it's down, restart it with systemctl restart zabbix-server. Check firewall rules—port 10051 must be open for server connections. Look at /​var/​log/​zabbix/​zabbix_server.​log for specific error messages. Database connectivity issues often cause this problem, so verify your MySQL or PostgreSQL service is running and accessible.

Agent Shows as Unreachable

• Confirm the Zabbix agent is running on the target host with systemctl status zabbix-agent
• Verify port 10050 is not blocked by firewall rules on the monitored host
• Check Server parameter in /​etc/​zabbix/​zabbix_agentd.​conf matches your server IP
• Test connectivity manually using zabbix_get command from the server
• Review agent logs at /​var/​log/​zabbix/​zabbix_agentd.​log for connection attempts

Web Interface Loading Slowly or Hanging

Slow dashboard performance usually points to database issues. Run maintenance tasks like housekeeping to remove old data—check Administration > Housekeeping settings. Increase PHP memory limits in php.ini if you manage many hosts. Add indexes to your database tables, especially the history and trends tables. Consider partitioning large tables or adjusting history retention periods. Check if your web server (Apache or Nginx) has sufficient worker processes configured.

Triggers Not Firing Despite Threshold Breach

Review your trigger expression syntax carefully—a single typo breaks functionality. Ensure the item is actively collecting data by checking Latest Data for recent values. Verify the host is monitored and not in maintenance mode. Check if trigger dependencies are preventing execution. Time-based functions like nodata() require correct time parameters. Test your expression using the trigger constructor in the web interface before deploying.

Notifications Not Reaching Recipients

Media type configuration mistakes cause most notification failures. Test your email server settings independently first—try sending a test email from the command line. For script-based notifications, verify the script has execute permissions and returns exit code 0. Check user media settings under Administration > Users—email addresses must match exactly. Review Actions configuration for correct trigger severity and operation conditions. Enable debug logging temporarily to trace notification attempts.