Troubleshooting

Your application was broken, but Uptimia opened no incident and sent no alert. Four causes explain almost every case: The failure returned HTTP 200, so the probe recorded a pass. The monitor was confi

A monitor that has gone quiet is in one of two situations: it is no longer being checked, or it is being checked and something is stopping the alert. Seven states produce it, all visible in the contro

A false positive is an alert that does not match what you see in your browser. The site is clearly up, but a site-down alert arrives; the certificate and content are fine, but an SSL-invalid or keywor

A monitor went down and nothing reached you. There are two causes, and one screen tells you which: either Uptimia decided not to send the alert, or it sent one and your mail gateway or carrier stopped

Uptimia checks your site from a network of monitoring locations, called checkpoints or probes. Which probes a given monitor uses is a saved-set question, answered in Location Profiles . Which Monitors

If your site sits behind a firewall, WAF, CDN, bot manager or antispam service, those systems can block Uptimia's probes. A blocked probe looks exactly like an outage. Allowlist the published probe ad

A heartbeat monitor arms itself on the first real ping, then alerts when the next one fails to arrive. Either your job looks like it is pinging but the monitor still says Pending first ping , or a job

A server monitor goes offline when the agent stops reporting. Uptimia never contacts the server. It waits for the agent to check in, and when the silence runs past three times the monitor's report int

A failed transaction check stops at the step it could not complete, and the incident then reads Transaction error — Error on step #N . Almost every cause of that failure is visible in the screenshot t

Your monitor is green again and the incident is still sitting on the public status page. That is deliberate. A monitor coming back up ends the incident , and the thread you published about it stays op