Uptime checks your URLs from every region, runs the sign-in behind them on a schedule and alerts your team the moment a step breaks — with every control open to agents over MCP.
No account needed. We'll run one check and show you exactly what a monitor would report.
Three things that stay true however much you end up monitoring.
Uptime, latency, certificates, DNS, cron jobs and multi-step flows, with the alert in the channel your team already reads.
Skip writing one-off scripts. Give an agent a scoped API key and let it operate Uptime the same way the REST API does.
curl https://uptime.sergiodxa.com/api/v1/monitors \ -H "Authorization: Bearer uptime_your_api_key" \ -H "Content-Type: application/json" \ -d '{ "name": "Production API", "url": "https://api.example.com/health", "method": "GET", "expectedStatus": 200, "intervalSeconds": 60 }'
{ "command": "npx", "args": [ "-y", "@sdxc/mcp@latest", "https://uptime.sergiodxa.com/mcp", "--header", "Authorization:Bearer ${UPTIME_MCP_TOKEN}" ] }
A flow monitor runs a short executable spec on a schedule: sign in, read the token, call the endpoint it authorises, and assert on every response. Run it over HTTP, or in a real browser.
http.post "/api/sessions" form { … }session.json.tokenhttp.get "/v1/account" bearer session.json.tokenexpect account.status 200Maintenance windows, cooldowns and content checks save the alert for a real outage.
The same checks cover a landing page, a payment API and the jobs behind them.
Tailored solutions for:
One subscription, no tiers. Pay only for what you use with our straightforward pricing model
Estimate monthly ping cost from monitor frequency. Browser flow runs bill separately at $2.5 per 1,000.
Includes first 100,000 pings
0 × $1 per 10,000 pings (0 over)
$5/month includes your first 100,000 pings
$1 per 10,000 pings after that, billed in whole blocks
$2.5 per 1,000 browser runs on a separate meter — none included in the subscription
No seat or feature add-ons. Pay for the pings and browser runs you use.
Find answers to common questions about Uptime
Uptime sends regular HTTP or HTTPS requests to your endpoints. We check response codes and response times to determine if your service is available and responsive.
When Uptime detects an outage, it immediately sends an alert through your configured channels.
Yes, as long as your internal services are accessible from the internet. You can also configure custom headers to authenticate requests.
Just sign up, create your first monitor, and configure your alert preferences. You’ll be up and running in under a minute.
Yes! You can create unlimited monitors and trigger pings manually for free, forever. Scheduled automatic monitoring requires a subscription.
We store your ping results for 365 days. After that, they are automatically deleted.
Yes. You can set custom headers with tokens or credentials to authenticate your requests.
Yes. Just create a separate monitor for each URL. Each monitor can have its own check frequency, HTTP method, expected status code, and more.
Absolutely. Uptime is designed to monitor both websites and APIs. You can set the endpoint, method, headers, and expected responses to monitor your API effectively.
Yes. You can configure a timeout for each monitor. If the response takes longer than expected, it’s considered a failure. This helps detect slow services.
Yes. You can pause any monitor at any time, individually.
Yes. A ping is automatically triggered right after you create a monitor.
Yes! Create customizable public status pages to share your service health with users. Include any monitors you want and add your branding.
We store all past results so you get a full history. Performance trend charts are planned for a future release.
Email, Slack, Discord, and webhooks. Native integrations make it easy to get alerts where your team already works. Webhooks let you connect to any other service.
Yes! Each user starts with a team. Invite team members with different roles (Owner, Admin, Member). Domain auto-provisioning automatically adds users with verified company email domains.
Usage above the 100,000 pings included in your subscription is billed in whole blocks of 10,000 at $1 each — a single ping over starts a new block. Browser flow runs are metered separately from the first one at $2.5 per 1,000 — none are included in the subscription.
No. We never store body data. For extra privacy and efficiency, we recommend using the `HEAD` method.
Uptime supports monitoring from multiple regions: Africa, Asia-Pacific, Eastern and Western Europe, Eastern and Western North America, Middle East, Oceania, and South America. You can choose one region per monitor. The region is treated as a hint, the actual ping will originate from a server in or near that region.
Yes. A flow monitor runs several steps in order with assertions between them. An HTTP flow can sign in, read the token back, and call the endpoint that token authorises. A browser flow opens a real Browser Run session, fills and clicks the way a visitor would, and asserts on what the live page exposes after JavaScript runs. Both run only against domains your team has verified.
Each browser run bills one event on a separate flow-run meter at $2.5 per 1,000 runs — nothing folded into the ping allowance. HTTP-only flows still bill one ping per request from the shared 100,000 included in your subscription.
Create your first monitor in under 2 minutes. No credit card required to start.