01
HTTP, TCP, DNS, ICMP and gRPC
Check a website, an API, a mail server or a database port. Custom headers and bodies, timeouts, and assertions on the response — and HTTPS monitors also watch certificate and domain expiry.
Everything uptime actually needs
From the first check to a public status page — in one place, without handing your customers' data to a third party.
- 10 checking points
- Data stays in Lithuania
- From a 30 second interval
- Free plan, no card
02
A status page on your own domain
status.yourcompany.lt with your logo and colours. The certificate is issued automatically — you add one CNAME record.
03
Alerts where you already work
Email, SMS, Slack, Discord, Telegram, webhooks, PagerDuty, OpsGenie. Escalation when the first person does not answer.
04
Incidents, maintenance and changelog
Publish an incident or planned work in one click — subscribers get an email and the history stays on the page. The changelog tells readers what changed.
05
Latency, not just up or down
p50, p75, p95 and p99 response times per region. You see that Vilnius is fast and Western Europe is not, before the phone rings.
06
API, CLI and monitoring as code
Describe checks in a YAML file and keep them in git. REST API, Terraform and SDKs, if you would rather never touch a mouse.
Three steps
- 1
Paste the address
Add the URL, pick regions and an interval. The first result lands within seconds.
- 2
Connect your team
Say where to write: a Slack channel, a phone number, or a webhook into your own system.
- 3
Publish your status
Turn on a public page on your domain and stop answering “is it down for you too?”.
Monitors as code
Checks live in git, not in a screenshot
Describe them in a YAML file and keep it beside what they watch. One command reconciles the service with the file, and a dry run shows the difference before anything changes.
- CLI
- REST API
- Terraform
- SDK
- MCP
Read on
Start monitoring in five minutes
One URL, one email address — and you will hear about the next outage from us, not from a customer.