Know what is working—without becoming a monitoring expert.
Plain-language, step-by-step guides for setting up your account, watching important services, responding to problems, and keeping customers informed.
Add a service
Tell Uptime which website or service matters to you.
Check from multiple places
We verify the service from independent locations around the world.
Confirm a real problem
Repeated failures are checked before your team is interrupted.
Notify the right people
Your team and customers receive clear, useful updates.
Choose what you need
Start with your goal, not a feature list.
I am brand new
Learn the dashboard and create a first website monitor using safe defaults.
Start the 10-minute setupI received an alert
Understand what happened, check the evidence, and decide what to do next.
Follow the incident guideI want to inform customers
Create a clear public status page without exposing private service details.
Build a status pageGuides
Learn one practical task at a time.
Every guide explains unfamiliar terms, recommends a safe starting point, and shows what you should expect to see.
Create your first monitor
Follow a simple, no-code walkthrough to watch your website and understand the first results.
Outcome
Your website is monitored from multiple locations using safe starting settings
Take a dashboard tour
Learn where to find current health, monitor history, incidents, maintenance, reports, and account settings.
Outcome
You can find the right page quickly and understand which information needs attention
Choose the right monitor type
Pick HTTP, keyword, TCP, ICMP, or DNS based on the simple question you want Uptime to answer.
Outcome
You use the simplest check that accurately represents customer availability
Choose a regional strategy
Balance geographic evidence, confirmation confidence, and check volume.
Outcome
Coverage that reflects users without turning one bad route into an outage
Read monitor results and history
Understand health states, activity bars, response time, regions, events, and the check log without guessing.
Outcome
You can tell the difference between one failed check, a confirmed incident, and a performance trend
Troubleshoot a failed check
Follow a calm, repeatable process to understand failures before changing alert settings.
Outcome
You identify whether the issue is the service, network path, or monitor configuration
Design an alert policy
Decide when evidence becomes an incident and when an incident deserves interruption.
Outcome
A response policy that reduces false positives without hiding sustained impact
Respond to an incident
A step-by-step guide for acknowledging an alert, checking customer impact, sharing updates, and confirming recovery.
Outcome
Your team follows a consistent response from first evidence through resolution
Schedule planned maintenance
Put planned work on the calendar, choose affected services, and keep it distinct from an unexpected outage.
Outcome
Planned service work is visible to your team and customers at the correct time
Publish a useful status page
Turn internal monitor state into clear, customer-safe communication.
Outcome
A structured public page that shows impact without exposing private targets
Decide who receives notifications
Route confirmed incidents and recoveries to the right people without overwhelming the whole team.
Outcome
Every important service has an owner and every recipient understands why they are notified
Invite and manage your team
Add teammates, choose an appropriate role, manage invitations, and remove access safely.
Outcome
Teammates have the access and notifications needed for their responsibilities
Set workspace and monitoring defaults
Keep new monitors consistent, apply regional coverage intentionally, and personalize the dashboard.
Outcome
Your workspace starts new monitors with sensible settings and shows information the way your team prefers
Connect a Slack webhook
Deliver confirmed incident and recovery events to the channel where your team works.
Outcome
A tested Slack destination with explicit event preferences and visible delivery history
Use the application API
Understand the current API surface, request shape, and authentication boundary.
Outcome
Accurate API usage without assuming a public token model that is not available yet
Plain-language monitoring glossary
Understand the words used across monitors, incidents, charts, notifications, and status pages.
Outcome
You can read the dashboard and guides without unfamiliar monitoring terminology getting in the way
Signed webhooks
Send verified incident events to your own applications.
Outcome
A signed webhook destination with verified payloads and retry handling
Configuration, explained
Technical details are there when you need them.
Most customers can use Uptime entirely from the dashboard. For developers, the advanced section explains request behavior, integrations, and the current API boundaries precisely.
Read API usageconst monitor = {
name: "Public API",
type: "http",
intervalSeconds: 60,
failureThreshold: 2,
confirmationRegions: 2,
regions: ["us-east", "us-west", "eu-west"]
};Need a human?
Documentation should not be a dead end.
Visitors can contact us directly. Signed-in customers can also open a support ticket with their workspace context attached.