Documentation
Find your bearings.
Build a calmer workflow.
From your first check to your next incident. Practical guides to help you set up, understand, and get more from Undown.
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 pageThe guide library
Find the task you need. Take it one step at a time.
20 guides
Start here
Get comfortable with your workspace and your first monitor.
Create your first monitor
Follow a simple, no-code walkthrough to watch your website and understand the first results.
Take a dashboard tour
Learn where to find current health, monitor history, incidents, maintenance, reports, and account settings.
Plain-language monitoring glossary
Understand the words used across monitors, incidents, charts, notifications, and status pages.
Monitor
Choose what to check and understand the results.
Choose the right monitor type
Pick HTTP, keyword, TCP, ICMP, or DNS based on the simple question you want Uptime to answer.
Choose a regional strategy
Balance geographic evidence, confirmation confidence, and check volume.
Read monitor results and history
Understand health states, activity bars, response time, regions, events, and the check log without guessing.
Troubleshoot a failed check
Follow a calm, repeatable process to understand failures before changing alert settings.
Review your monitoring before launch
Check coverage, alert destinations, and customer communication before relying on a new monitoring setup.
Respond
Turn a signal into a clear next step.
Design an alert policy
Decide when evidence becomes an incident and when an incident deserves interruption.
Respond to an incident
A step-by-step guide for acknowledging an alert, checking customer impact, sharing updates, and confirming recovery.
Schedule planned maintenance
Put planned work on the calendar, choose affected services, and keep it distinct from an unexpected outage.
Troubleshoot notification delivery
Work out why an expected outage or recovery notification did not reach its destination.
Communicate
Keep your team and customers in the loop.
Publish a useful status page
Turn internal monitor state into clear, customer-safe communication.
Workspace
Set up the people and defaults behind your monitoring.
Decide who receives notifications
Route confirmed incidents and recoveries to the right people without overwhelming the whole team.
Invite and manage your team
Add teammates, choose an appropriate role, manage invitations, and remove access safely.
Set workspace and monitoring defaults
Keep new monitors consistent, apply regional coverage intentionally, and personalize the dashboard.
Advanced
Connect your tools and explore the application API.
Connect a Slack webhook
Deliver confirmed incident and recovery events to the channel where your team works.
Use the application API
Understand the current API surface, request shape, and authentication boundary.
Signed webhooks
Send verified incident events to your own applications.
Choose and manage integrations
Connect a team channel or your own application to confirmed outage and recovery events.
For developers
Connect the rest of your workflow.
Explore signed webhooks, notification setup, and the current application API. Configuration details and examples, with the boundaries explained.
A little help goes a long way.
Can’t find your answer? Let’s work through it together.