HTTP & HTTPS monitoring
Know the moment your website or API goes down.
An HTTP/S monitor requests a URL on a schedule and checks the response status code, so you hear about an outage before your visitors do.
How it works
UptimeAlien sends a request from our servers at your chosen interval, follows redirects, and marks the monitor down after a configurable number of consecutive failures. You can also alert on slow responses above a latency threshold.
When to use it
- Public websites and landing pages where every minute of downtime is visible
- REST APIs and webhook endpoints other systems depend on
- Health-check endpoints like /healthz that your deployment already ships
- Sites behind a CDN or load balancer, where the origin can fail while the cache keeps serving
- As a response-time watchdog: set a threshold and hear about “degraded” instead of waiting for the outage
What you get
Up/down status, response-time history, uptime ratios over 24h/7/30/90 days, and an incident timeline.
Example
https://api.acme.com/health: expect 200, alert if slower than 1000 ms
Frequently asked questions
What is HTTP monitoring?
HTTP monitoring sends a request to your website or API on a fixed interval and checks that it answers with an expected status code in acceptable time. It is the most common form of uptime monitoring and covers websites, APIs and any HTTPS endpoint.
How does UptimeAlien avoid false alarms?
A monitor is only marked down after a configurable number of consecutive failed checks. A single dropped packet or a one-off timeout therefore does not page anyone.
Does it follow redirects?
Yes. The check follows redirects, so a monitor on your apex domain still works when it redirects to www or from HTTP to HTTPS.
Can I get alerted on slow responses too?
Yes. Set a latency threshold on the monitor and it switches to “degraded” when responses exceed it, even while the status code is still fine.