For agencies, developers and businesses
Monitoring and client reporting for the websites your business depends on.
HTTP availability, TLS expiry, DNS drift and heartbeat checks in one place, with incident evidence you can explain, measurement coverage you can trust, branded status pages and scheduled reports for every client.
No credit card. First real observation within one check interval. Clear limits on every plan.
| Monitor | State | Latency | Availability (30d) | Coverage |
|---|---|---|---|---|
Marketing site https://www.example.com/ | UP | 212 ms | 99.982% | 99.6% |
Checkout API https://api.example.com/health | UP | 87 ms | 99.995% | 100% |
Nightly backup heartbeat every 24h | UP | n/a | 100% | 100% |
Client: Acme shop https://shop.acme.example/ | DOWN | n/a | 99.41% | 99.8% |
Mail DNS example.com MX | DEGRADED | 31 ms | 100% | 100% |
Try it now
Is your website reachable right now?
One real request from our probe, with status, timing, redirects and certificate facts. One observation from one location is a useful signal, not proof of worldwide availability.
What we monitor
Six check types, one honest measurement model
Every check records when it was scheduled, when it ran, from where and under which configuration version. Missing observations are unknown, not successful.
HTTP and API
GET and HEAD by default, expected status codes, keyword presence or absence, bounded JSON assertions, custom headers and encrypted credentials. Timeouts, redirect and size caps on every request.
TLS certificates
Trust, hostname and chain validation on every HTTPS check, plus a daily expiry inspection with 30, 14, 7, 3 and 1-day warnings. A failed validation stays a failure.
DNS records
A, AAAA, CNAME, MX, TXT, NS, SOA and CAA with expected values and change history. Ordering and TTL differences never count as changes.
Heartbeats
Your cron jobs and workers ping a secret URL. We alert when they stop, run too long or report failure, and handle duplicates and late signals deterministically.
TCP and domains
Connection checks to explicitly permitted ports and registration-expiry lookups through RDAP where registries publish it.
Incidents with evidence
Incidents open after a configurable number of consecutive failures, keep the original measurements immutable and record every human annotation separately.
Availability is time-weighted over evaluable time and always shown next to measurement coverage. Maintenance windows are excluded from the adjusted figure while the unadjusted figure stays available. A 30-second interval is not a 30-second notification: detection, timeout, confirmation and delivery latency are reported separately. Read the methodology.
Built for agencies and hosting providers
One account, a workspace per client, scoped access and reports that write themselves
Monitors and seats are pooled across the account, so another client workspace never multiplies your bill.
Client workspaces
Separate monitors, incidents, channels and status pages per client with a quick switcher and client-specific notification routing.
Scoped client viewers
Give clients read access to their own workspace only. Client viewers never see other clients, team settings or billing.
Bulk import with preview
Upload a CSV, see every row validated, deduplicated and checked against your limit before anything is created. Export is one click.
Branded client reports
Weekly or monthly reports from stored measurements: availability with coverage, downtime, incidents and latency, sent to the recipients you choose.
White-label status pages
Your logo, colours and domain. Only the components you select are public; targets and credentials never are.
Audit trail
Every change to monitors, channels, members and billing is recorded with the actor, redacted of secrets.
Status pages
Tell customers what is happening without exposing how you monitor
Published pages show component states, daily history bars that distinguish no-data days from uptime, planned maintenance and the public updates you choose to post.
- WebsiteOperational
- Customer portalOperational
- Email deliveryDegraded performance
Grey days mean no data, not uptime. Availability is time-weighted over evaluable time.
- Opt-in indexing. Pages are private by default; password-protected pages are never indexable.
- Custom domains verified through DNS before they serve anything.
- Stale data is labelled. If the control plane cannot refresh a page, visitors see the last known state and its timestamp, not a green lie.
- Email subscribers confirm before they receive anything and can unsubscribe from every message.
- More about status pages
Pricing
Clear limits, predictable billing, prices in EUR
The pricing page and the product read the same catalog. No setup fees, no overage charges, annual plans charge ten months for twelve.
Free
€0.00/mo
5 monitors · 300s · 1 seat · 1 workspace
Starter
€9.00/mo
20 monitors · 60s · 1 seat · 1 workspace
Business
€29.00/mo
100 monitors · 60s · 5 seats · 5 workspaces
Agency
€79.00/mo
300 monitors · 60s · 10 seats · 30 workspaces
Scale
€199.00/mo
1000 monitors · 30s · 25 seats · 100 workspaces
Security
Built so the monitoring service cannot become a weapon
Every outbound request from monitors, tools, crawlers and webhooks passes one safe network client.
No private destinations
Private, loopback, link-local, metadata and reserved addresses are refused for IPv4 and IPv6, including mapped and embedded forms, on every hop of every redirect.
Pinned connections
Hostnames are resolved once, every answer is validated and the connection is pinned to the validated address while Host and SNI keep the original name. No rebinding, no pooled bypass.
Bounded everything
10-second deadlines, 3-second connects, five redirects, 128 KiB bodies and capped decompression by default. Probes have no database access and submit results with per-run lease tokens.
Encrypted credentials
Monitor and channel secrets are encrypted with versioned keys, redacted from logs, exports and the API, and never shown again after creation.
MFA on every plan
Time-based codes with recovery codes, session revocation, verified email, rate-limited sign-in and short-lived invitation and reset tokens.
Tenant-scoped by construction
Workspace and account ids are never trusted from the client; every service call resolves permissions from memberships first.
Questions
Frequently asked questions
- What counts as a monitor?
- One configured HTTP/API, TCP, DNS, heartbeat or standalone TLS/domain check. The daily certificate inspection attached to an HTTPS monitor does not use another slot. Selecting a region is not another monitor.
- Does a 30-second interval mean I am alerted within 30 seconds?
- No. Detection depends on the interval and timeout, confirmation adds one more check where enabled, and delivery depends on the channel. Each of these latencies is shown separately.
- Do you run checks from many regions?
- Each check runs once per interval from one primary location. Where an independent probe location is deployed, failures are confirmed from a second location before an incident opens. The regions actually deployed are published on the security page; we do not claim global coverage.
- What happens when I downgrade and have too many monitors?
- Nothing is deleted. Creating new monitors is blocked while you are over the limit and, after a 14-day grace period, the newest excess monitors are paused until you remove some or upgrade.
- Can UptimeMonitor360 fix my website?
- No. Detection and notification are not remediation. We tell you what failed, when, from where and with which evidence.
- How is availability calculated?
- Time-weighted over evaluable time, from recorded state transitions. Unknown and paused time is excluded and reported as coverage. Maintenance is excluded from the adjusted figure and the unadjusted figure is also available.
Start monitoring in minutes
Five monitors, email alerts and a status page free. Upgrade when the limits actually matter to you.