The questions
that matter.
How UptimeLoop works, without jargon or promises that do not exist in the product yet.
How often does UptimeLoop check an endpoint?+
Every HTTP monitor is checked every 60 seconds. Each request has a short timeout to keep monitoring fast and lightweight.
What can I monitor?+
Public HTTP or HTTPS endpoints. You can define the expected HTTP status code, such as 200 for a page or health endpoint.
Does UptimeLoop monitor SSL certificates?+
Yes. Certificates are checked daily and their expiry date is visible in the dashboard.
Does domain monitoring work for every TLD?+
UptimeLoop queries WHOIS and displays the expiry date when the registry returns it in a usable format. Some registries limit or hide this information.
How long is data stored?+
Detailed check results are kept for 7 days, hourly availability aggregates and incidents for 90 days. This keeps the product fast without losing the useful history.
How are incidents created?+
UptimeLoop opens an incident only after two complete checks fail 10 seconds apart, each with fresh DNS resolution and a new connection. Outage and recovery emails are queued transactionally when email delivery is enabled.
Can I share a status page?+
Yes. Public status pages are built to show the components and incidents from your workspace.
Is billing available today?+
Plans are defined, but online payments are not connected yet. Create your account now and plan selection will be finalised in your workspace.
Start with one endpoint.
The dashboard shows you the rest, one minute later.