Statusloop is an all-in-one monitoring and alerting platform that brings uptime monitoring, server metrics, Cron checks, and on-call alerting together in a single workspace, helping teams find problems before users notice them.
Purpose Statusloop is designed for teams that need to monitor websites, APIs, servers, scheduled tasks, and background workers, and is especially suitable for engineering teams that already have an on-call process and want to integrate monitoring into their deployment pipeline.
Main capabilities
- Monitor types: Supports HTTP, TCP, and DNS checks, providing uptime, status code, and response time history; a lightweight agent can be used to collect CPU, memory, and disk metrics from servers; it can monitor Cron jobs and workers, where tasks send heartbeats on time and silence triggers an incident.
- Check intervals: every 5 minutes on the free version, every 1 minute on Essentials, every 30 seconds on Pro, every 10 seconds on Business, and customizable on Scale.
- Incidents and alerts: When a check fails, an incident is automatically opened and the selected channels are notified, supporting email, Slack, Telegram, Discord, SMS, and configurable escalation policies (for example, notifying the on-call person by SMS if not acknowledged). Every alert links back to the corresponding incident.
- Incident timeline: From detection to acknowledgment to resolution, a complete timeline shared with the team is generated.
- Status pages: A public status page automatically updated by monitors can be published on your own domain.
- Scripting and integrations: Everything in the dashboard is available over HTTP, with a REST API for creating monitors from CI and Webhooks with a stable JSON payload for every status change. A heartbeat requires only one request each time, and any HTTP client (cURL, wget, fetch, or a single line of code in a worker) can send it.
How to use No YAML, no agent installation for HTTP, and no lengthy pager configuration. Add a URL, server, or Cron job: paste an endpoint, install the server agent on the host, or provide a ping URL for the task to create a monitor.
Use cases Suitable for trying out a personal project, small teams with a few services, production environments and on-call teams, and large infrastructure that needs monitoring at scale with custom check intervals and invoicing.
Limitations and notes Websites, APIs, TCP, and DNS checks require no agent and can go live by simply pasting a URL; server metrics require a lightweight agent on the host; health checks are initiated by the task with a singleNext HTTP request. The free plan includes 10 monitors, 1 health check, 1 server, 1 status page and email alerts, with no credit card required and no time limit. Paid plans are billed annually, and all plans include all monitor types, incidents and status pages; large-scale plans support custom limits, check intervals and invoices. The platform is hosted in the EU and processes data in accordance with the GDPR, storing only the data necessary to run checks and send alerts, and does not sell data. Billing can be monthly or annual, cancel anytime, cancellation takes effect at the end of the billing period, and there is no setup fee. Phone calls, Webhooks and PagerDuty are marked as coming soon in the official materials. No VAT is charged under Section 19 of the German VAT Act (small business). Content not provided in the source materials is not yet available.
