Features
An SDK can only report problems while your application is running. When the host is unreachable, the proxy answers 502 or the certificate has expired, nothing is sent. Uptime monitors close that gap by checking your endpoints from the outside.
Uptime monitoring
Buglapse requests your URL on a fixed interval from its own servers. It works for a homepage, an API health check or a webhook receiver, with nothing to install.
A monitor goes down only after several failed checks in a row, and recovers after a successful one. Each incident has a start, an end, a duration and a cause.
Choose the method, headers, body, timeout, accepted status codes and whether to follow redirects. gRPC services can be checked on plans that include it.
Uptime percentage, response times and a log of every check with its status code, duration and error, filterable by result.
How it works
Open Uptime in a project, enter the URL and choose how often to check it. The Test button runs one check before anything is saved.
Set how many failures in a row open an incident and which status codes count as up — useful for endpoints that are supposed to answer with a redirect or a 404.
When a monitor goes down and when it recovers, the team gets an alert by email or in a messenger within about a minute, without waiting for the regular digest.
In detail
Each check sends the method, headers and body you configured and waits up to the timeout, redirects included. Only the status code and the response time are kept — the response body is read up to a small limit and discarded, and no cookies are stored between checks. A response with a status code outside the accepted list is a failure, as is a timeout, a connection error or an invalid certificate.
A single failed check does not wake anyone up. The monitor is marked down after the number of consecutive failures you set, which opens an incident and sends the alert once. The first successful check after that closes the incident and sends the recovery alert. The list of monitors shows what is down first, and the same data is available to AI assistants through the MCP server.
| Free | Pro | Team | |
|---|---|---|---|
| Monitors | 1 | 10 | 50 |
| Shortest check interval | 10 minutes | 1 minute | 1 minute |
| Check history retention | 7 days | 14 days | 30 days |
| gRPC checks | Not included | Included | Included |
FAQ
Still have questions?
Drop us a line — we'll help with setup, plans or self-hosting.
Contact usor email hello@buglapse.com
See also
Alerts about new and returning errors, spikes, stability drops and downtime — by email, in Telegram and in MAX.
Learn more: AlertsEvery error grouped into one issue with a readable stack trace, breadcrumbs, the steps to the error and the affected users.
Learn more: Error trackingLet Claude Code, Cursor and other AI assistants read your issues, traces and logs.
Learn more: MCP serverCreate a project on the free plan and send your first event in a couple of minutes.
Still have questions? Email hello@buglapse.com