Multi-region checks
HTTP, TCP, ICMP and TLS certificate checks from four European regions, with confirmation from a second region before anything pages you.
Uptime monitoring
Know your service is down
Know your service is down
before your customers tell you.
Plamb checks your endpoints from four European regions, confirms every failure from a second location, and publishes a status page your customers can actually read. No agents to install.
14-day trial on every plan · no card required · cancel from the dashboard.
What you get
Monitoring without the dashboard sprawl
One place for checks, alert routing, incident history and the public status page — instead of three tools that disagree with each other.
Alerts that respect on-call
Route by service and time of day to email, Slack, Telegram or a webhook. Repeat alerts are grouped so one bad deploy is one notification.
Status pages in minutes
A hosted status page per environment, on your own domain, with incident history, subscriber notifications and an embeddable badge.
Certificate expiry watch
Every TLS endpoint is inspected daily. You get a warning 30, 14 and 3 days before a certificate expires, including intermediates.
Maintenance windows
Schedule windows so planned work never counts against uptime and subscribers are told in advance instead of after the fact.
Reports you can hand over
Monthly uptime and latency summaries per service, exportable as CSV or PDF for customers who ask for SLA evidence.
How it works
Three steps
Most teams have their first monitor running in under five minutes, usually straight from CI.
1. Add a monitor
Create it in the dashboard or POST it to the API. A monitor is a URL, an interval, the regions to probe from and the response you expect.
2. Point alerts at the right people
Attach notification rules per service. Office hours to Slack, out-of-hours to the on-call rotation, everything else to email.
3. Publish a status page
Group monitors into public components, add your logo and a domain, and let subscribers follow incidents instead of emailing support.
curl -X POST https://api.91831082026.site/v1/monitors \
-H "Authorization: Bearer $PLAMB_TOKEN" \
-H "Content-Type: application/json" \
-d '{"name":"api","url":"https://api.example.com/healthz",
"interval":60,"regions":["fra","ams"]}'
Live
Our own status, on our own tooling
The page below is a Plamb status page. We run the platform on it too.
-
API
Operational -
Probe network
Operational -
Status pages & CDN
Operational
Recorded webinar
Monitoring from scratch
A recorded 26-minute walkthrough: first check, alert routing, status page. We set up an account from an empty dashboard, add the first checks, route the alerts and publish a status page — in real time, without cuts.
26:09 · recorded 20 August 2026 · no sign-up, no email wall
26:09
How often are checks run?
Checks run every 60 seconds on the Team plan and every 30 seconds on Business. Each check is confirmed from a second region before an alert is sent, which keeps single-region noise out of your inbox.
Where do checks run from?
Probes run from four regions: Frankfurt, Amsterdam, Warsaw and Helsinki. You can pin a monitor to a single region if a service is only reachable from one network.
Can I use my own domain for a status page?
Yes. Point a CNAME at your status page and Plamb issues and renews the certificate automatically. Custom domains are included on every paid plan.
How long is history kept?
Raw check results are kept for 30 days and daily aggregates for 24 months, so annual uptime reports stay available after the raw data expires.
Start monitoring today
Add your first monitor in five minutes. Keep the plan that fits, drop it whenever you like.