Website uptime monitoring with down alerts
Lampwick requests your URL every 30 seconds to 1 hour and sends a down alert after 2 failed checks in a row. Free plan: 3 monitors every 5 minutes.
An uptime monitor requests one public URL on a fixed interval, from Lampwick's servers, and tells your team when it stops answering. After 2 failed checks in a row the monitor is Down and everyone on the team gets Down: MONITOR by push and e-mail, with the reason first. You add it by pasting a URL; your app needs no code.
What you get
- Checks every 30 seconds to 1 hour. The shortest interval depends on the plan: as often as every 5 minutes on Free, every minute on Pro, every 30 seconds on Team and Business.
- A quick second look. After a first failure, Lampwick checks again within 15 seconds. One dropped request alerts no one; a real outage is noticed within one interval plus about 15 seconds.
- The reason in the alert.
HTTP 503,timed out after 10 s, a DNS or TLS error: the alert says which, and shows the host and path of the URL, never the query string. - Up again. Up again: MONITOR after the first successful check, only after a down alert.
- Response times. The monitor's page shows uptime for the selected range, average and p95 response time, and the latest checks with status, duration and error.
- SSL, domain and DNS on the same monitor. Every monitor also checks its certificate and domain, with no extra setup.
- Alerts where your team works. Push in the Lampwick iOS app, e-mail, and alert channels for Slack, Discord, Microsoft Teams or a signed webhook.
- Fewer alerts on purpose. At most one down alert per monitor per 30 minutes when a site flaps, and a mute switch per monitor.
How a check decides up or down
| Rule | Value |
|---|---|
| Up | The final response, after redirects, has status 2xx or 3xx. |
| Failed check | Any other status, no response headers within 10 seconds, a DNS, connection or TLS error, or more than 5 redirects. |
| Down | 2 failed checks in a row. |
| Back up | 1 successful check. |
| Request | GET, User-Agent lampwick-uptime/<version> |
Check if your website is down, then stop checking by hand
To check by hand, open the site in a private window or run curl -I https://example.com; how to know when your app is down goes through the usual causes. An uptime monitor does that check for you, all day, and alerts when it fails twice in a row.
Set it up in a minute
- Create an account and a project.
- Go to Uptime in the sidebar and paste the URL under Add monitor, such as
https://example.com/up. - Pick Check every and click Add monitor. The first check runs within seconds.
Monitor a light health endpoint (Laravel's /up route, for example) rather than a heavy page. Behind Cloudflare or another WAF, allow the User-Agent lampwick-uptime. Details: the uptime docs. An AI agent can add monitors too, over the MCP server.
What it doesn't do
- Checks come from one place, Lampwick's own servers. There is no confirmation from a second location.
- It checks the status code, not the page's content: no keyword checks, no
POST, no custom headers. - No ping, TCP port or Lighthouse checks.
- Alerts go by push, e-mail, Slack, Discord, Microsoft Teams or webhook. No SMS, phone calls or PagerDuty.
- Only public
http://andhttps://URLs. Private and loopback addresses are refused.
If you need several locations or more check types, read Lampwick vs Oh Dear.
What it costs
| Plan | Price per team | Uptime monitors |
|---|---|---|
| Free | €0 | 3, every 5 min |
| Pro | €29 / month | 20, every minute |
| Team | €79 / month | 100, every 30 s |
| Business | €199 / month | 300, every 30 s |
SSL, domain and DNS checks come with every monitor on every plan. The plans also include error and request monitoring: see pricing.
Related
- Show your monitors to customers: status pages.
- Find broken links on the same site: broken link checker.
- Comparing tools: UptimeRobot alternatives.
- Built with Lovable, Replit or v0: monitoring for AI-built apps.
Start free and paste your URL.