Monitor · Status · Incidents · Vendors
Only real outages wake you up.
Keep the tools you already use. StatusTick checks your product from regions around the world and confirms a failure before anyone is paged, even when your own stack goes down with it.
- Checkout APIhttps://api.example.com/healthUp212 ms99.97%
- Marketing sitehttps://www.example.comBlocked—99.99%
- Nightly backupHeartbeat · every 24 hUp—100.00%
- Search APIhttps://search.example.comDegraded1,204 ms99.81%
Why StatusTick
Checked from around the world.
StatusTick is your independent second view. It checks your product the way your users reach it, and tells you, and your users, when production really fails.
Around the world
StatusTick checks from regions around the world, the way your users reach you, so a failure is seen even when your own tools go down with it.
Confirmed first
A failure is checked from more than one region before anyone is paged. Firewall blocks, slow answers and maintenance are shown as what they are, not as outages.
Calm when it matters
The incident, the status page and your vendors’ status are in one place, so the team fixes and your users stay informed.
The platform
The complete reliability platform.
Monitoring, status pages, incident response and vendor status work as one system: one account, one API and one record of what happened.
- MonitorUpKnow when something breaks.
- Websites, APIs, TCP, ping and DNS
- Cron jobs and heartbeats
- SSL and domain expiry
- Playwright checks and private agents
- StatusOperationalTell your users, on your own domain.
- Components that follow your monitors
- Incident posts drafted for you
- 90 days of uptime per component
- Email subscribers
- IncidentsResolvedGet the right person on it.
- Acknowledge from the alert
- Escalation and on-call
- Alerts from the tools you already use
- A timeline of what happened
- VendorsOperationalKnow when it is them.
- Official status of OpenAI, Stripe and GitHub
- Alerts when a vendor posts an incident
- Vendor problems shown on your incidents
- A vendor group on your status page
False alarms
Confirmed before anyone is paged.
A network blip, a firewall challenge or a short deploy should not wake anyone. StatusTick checks again from other regions and pages only when the failure is real.
- 01Down only when two regions agree
- 02You choose how many failed checks open an incident
- 03Blocked, degraded and maintenance are not down
- FrankfurtDown503 · 1,204 ms
- LondonDown503 · 1,188 ms
- VirginiaUp200 · 212 ms
- TokyoUp200 · 301 ms
- SydneyUp200 · 356 ms
Confirmed from 2 regions. Incident opened, on-call paged.
Keep users informed
A status page that keeps itself current.
Components follow your monitors, incident posts are drafted from your incidents, and your users see the same truth you do, on your own domain.
Degraded performance on the API. We are looking into slower responses.
- WebsiteOperational
- APIDegraded performance
- DashboardOperational
Third-party services
Payments APIOperational
Subscribe to updatesRSS · JSON
Vendors
Know when it is them.
Follow the official status of OpenAI, Stripe and GitHub. When a vendor posts an incident, you get an alert and see it next to your own.
- Payments APIOfficial statusUp
- AI model APIOfficial statusDegraded
- Code hostingOfficial statusUp
Alerts
Alerts that say what broke.
Every alert names the monitor, the failing regions, the error and the start time, with one link to acknowledge. If nobody reacts, StatusTick escalates.
- Slack
- Microsoft Teams
- Discord
- Telegram
- PagerDuty
- Webhooks
DownCheckout API
Down from Frankfurt and London since 14:05 UTC.
GET https://api.example.com/health → 503 Service Unavailable
Closed beta
Know before your users do.
Find problems before your customers do, and ship with more confidence. Launching Q1 2027: join the closed beta and help decide what we build next.