Skip to content
StatusTick
Join the beta

Only real outages wake you up.

StatusTick checks your product from outside your stack, from regions around the world, so you hear about it even when your own tools go down too. It pages someone only when more than one region sees the failure.

Closed beta now, launching Q1 2027.

Checkout API · GET /healthExample
LHRLondonFRAFrankfurtIADVirginiaNRTTokyoSYDSydney
  • Up
  • Degraded
  • Down
  • Maintenance
  • Blocked
  • Checking
14:05:08 UTC

ConfirmedTwo regions agree. Incident opened, on‑call paged.

Confirmed. Two regions agree. Incident opened, on‑call paged.

  1. London503 · 1,188 ms
  2. Frankfurt503 · 1,204 ms
  3. Virginia200 · 208 ms
  4. Tokyo200 · 295 ms
  5. Sydney200 · 349 ms

Four products, one account

Uptime monitoring that knows a firewall from an outage.

Most monitors call every failed check Down. StatusTick reads the answer: a bot wall, a slow API and a real outage are different things, and only one of them should wake someone.

You choose how many failed checks in a row open an incident. A plain 403 from your own app still counts as down.

How StatusTick avoids false alarms
What StatusTick does with each kind of answer
The check getsShown asWho hears about it
503 from London and FrankfurtDownOn-call is paged. Incident opened.
503 from London onlyCheckingNobody yet. Another region checks again.
403 from a firewall (WAF) or a bot challenge pageBlockedYou get one notice with steps to allow our checks. No incident.
200 after 4,210 msDegradedShown as slow, not counted as down.
Any answer in a maintenance windowMaintenanceNobody. Planned work stays quiet.
503 while Stripe reports an incidentDownOn-call is paged, with Stripe’s incident on the timeline.

Set up monitoring from your coding agent.

One sentence to your agent is enough. It adds the StatusTick MCP server, the way Claude Code, Cursor and other agents connect to outside tools, asks you to sign in once, then finds your production URL, health route and scheduled jobs and plans the monitors with you. The server cannot delete anything.

Set up with an AI agent
Tell your agent
Read https://statustick.com/setup.md and follow it.
  1. 1 · It adds the server

    The steps for your client are in setup.md, from Claude Code to Claude Desktop.

  2. 2 · You sign in once

    Your browser opens StatusTick. Pick the organization and allow read and write.

  3. 3 · It plans the monitors with you

    Nothing is created until you say yes.

Agent: I found 3 things to monitor in ~/checkout-app. Example

Monitors the agent plans to create, example
TypeTargetInterval
HTTPhttps://app.example.comevery 60 s
HTTPhttps://app.example.com/api/healthevery 60 s
Heartbeatnightly-report (vercel.json cron)every 24 h

Create these 3 monitors?

  • Claude Code
  • Cursor
  • VS Code
  • Codex CLI
  • Windsurf
  • Gemini CLI
  • Claude Desktop

Prefer clicking? Paste a URL in the dashboard. How StatusTick works

Incidents and status pages, one record.

Monitor, Status, Incidents and Vendors are one system: one account, one API, one timeline. Your team gets the alert, your users get the status page, and both say the same thing. Each product works on its own too.

  1. 14:05:08MonitorCheckout API confirmed down from London and Frankfurt.HTTP(S), TCP, ping, DNS, heartbeats, SSL and domain expiry, Playwright checks.Monitor
  2. 14:05:09IncidentsIncident opened. On-call paged in Slack and PagerDuty.Acknowledge from the alert. Escalation if nobody does.Incidents
  3. 14:06:10Statusstatus.example.com shows Checkout as down, with a drafted update.Components follow your monitors, on your own domain.Status
  4. 14:06:12VendorsStripe reports no incident, so the bug is yours.Official status of the services you depend on, on your incident timeline.VendorsSee the vendors we follow
  5. 14:21:00MonitorAll regions answer 200. Resolved after 16 minutes.The timeline stays on the incident.
#ops-alerts · 14:05:09Example

Checkout API is down

Down from London and Frankfurt since 14:05 UTC. Virginia, Tokyo and Sydney are up.

GET https://api.example.com/health → 503 Service Unavailable
  • Email
  • Slack
  • Microsoft Teams
  • Discord
  • Telegram
  • PagerDuty
  • Webhooks
Example alert in a chat channel.
Example Inc. status · 14:06:10status.example.com

Checkout is down. We are looking into failed payments since 14:05 UTC.

WebsiteOperational

  1. 13 Jul: up
  2. 14 Jul: up
  3. 15 Jul: up
  4. 16 Jul: up
  5. 17 Jul: up
  6. 18 Jul: up
  7. 19 Jul: up
  8. 20 Jul: up
  9. 21 Jul: up
  10. 22 Jul: up
  11. 23 Jul: up
  12. 24 Jul: up
  13. 25 Jul: up
  14. 26 Jul: up
  15. 27 Jul: up
  16. 28 Jul: up
  17. 29 Jul: up
  18. 30 Jul: up
  19. 31 Jul: up
  20. 1 Aug: up
  21. 2 Aug: up
  22. 3 Aug: up
  23. 4 Aug: up
  24. 5 Aug: up
  25. 6 Aug: up
  26. 7 Aug: up
  27. 8 Aug: up
  28. 9 Aug: up
  29. 10 Aug: up
  30. 11 Aug: up
  31. 12 Aug: up
  32. 13 Aug: up
  33. 14 Aug: up
  34. 15 Aug: up
  35. 16 Aug: up
  36. 17 Aug: up
  37. 18 Aug: up
  38. 19 Aug: up
  39. 20 Aug: up
  40. 21 Aug: up
  41. 22 Aug: up
  42. 23 Aug: up
  43. 24 Aug: up
  44. 25 Aug: up
  45. 26 Aug: up
  46. 27 Aug: up
  47. 28 Aug: up
  48. 29 Aug: up
  49. 30 Aug: up
  50. 31 Aug: up
  51. 1 Sep: up
  52. 2 Sep: up
  53. 3 Sep: up
  54. 4 Sep: up
  55. 5 Sep: up
  56. 6 Sep: up
  57. 7 Sep: up
  58. 8 Sep: up
  59. 9 Sep: up
  60. 10 Sep: up
  61. 11 Sep: up
  62. 12 Sep: degraded
  63. 13 Sep: up
  64. 14 Sep: up
  65. 15 Sep: up
  66. 16 Sep: up
  67. 17 Sep: up
  68. 18 Sep: up
  69. 19 Sep: up
  70. 20 Sep: up
  71. 21 Sep: up
  72. 22 Sep: up
  73. 23 Sep: up
  74. 24 Sep: up
  75. 25 Sep: up
  76. 26 Sep: up
  77. 27 Sep: up
  78. 28 Sep: up
  79. 29 Sep: up
  80. 30 Sep: up
  81. 1 Oct: up
  82. 2 Oct: up
  83. 3 Oct: up
  84. 4 Oct: up
  85. 5 Oct: up
  86. 6 Oct: up
  87. 7 Oct: up
  88. 8 Oct: up
  89. 9 Oct: up
  90. 10 Oct: up

CheckoutDown

  1. 13 Jul: up
  2. 14 Jul: up
  3. 15 Jul: up
  4. 16 Jul: up
  5. 17 Jul: up
  6. 18 Jul: up
  7. 19 Jul: up
  8. 20 Jul: up
  9. 21 Jul: up
  10. 22 Jul: up
  11. 23 Jul: up
  12. 24 Jul: up
  13. 25 Jul: up
  14. 26 Jul: up
  15. 27 Jul: up
  16. 28 Jul: up
  17. 29 Jul: up
  18. 30 Jul: up
  19. 31 Jul: up
  20. 1 Aug: up
  21. 2 Aug: up
  22. 3 Aug: up
  23. 4 Aug: up
  24. 5 Aug: up
  25. 6 Aug: up
  26. 7 Aug: up
  27. 8 Aug: up
  28. 9 Aug: up
  29. 10 Aug: up
  30. 11 Aug: up
  31. 12 Aug: up
  32. 13 Aug: up
  33. 14 Aug: up
  34. 15 Aug: up
  35. 16 Aug: up
  36. 17 Aug: up
  37. 18 Aug: up
  38. 19 Aug: up
  39. 20 Aug: up
  40. 21 Aug: up
  41. 22 Aug: degraded
  42. 23 Aug: up
  43. 24 Aug: up
  44. 25 Aug: up
  45. 26 Aug: up
  46. 27 Aug: up
  47. 28 Aug: up
  48. 29 Aug: up
  49. 30 Aug: up
  50. 31 Aug: up
  51. 1 Sep: up
  52. 2 Sep: up
  53. 3 Sep: up
  54. 4 Sep: up
  55. 5 Sep: up
  56. 6 Sep: up
  57. 7 Sep: up
  58. 8 Sep: up
  59. 9 Sep: up
  60. 10 Sep: up
  61. 11 Sep: up
  62. 12 Sep: up
  63. 13 Sep: up
  64. 14 Sep: up
  65. 15 Sep: up
  66. 16 Sep: up
  67. 17 Sep: up
  68. 18 Sep: up
  69. 19 Sep: up
  70. 20 Sep: up
  71. 21 Sep: up
  72. 22 Sep: up
  73. 23 Sep: up
  74. 24 Sep: up
  75. 25 Sep: up
  76. 26 Sep: up
  77. 27 Sep: up
  78. 28 Sep: up
  79. 29 Sep: up
  80. 30 Sep: up
  81. 1 Oct: up
  82. 2 Oct: up
  83. 3 Oct: up
  84. 4 Oct: up
  85. 5 Oct: up
  86. 6 Oct: up
  87. 7 Oct: up
  88. 8 Oct: up
  89. 9 Oct: up
  90. 10 Oct: down

90 days agoToday

Example status page for a made-up company.

Know before your users do.

Launching Q1 2027. Join the closed beta and help decide what we build next.

We will write when your invite is ready.