Sign inJoin the waiting list

Uptime monitoring developers love

Every incident arrives with the request, the response and a traceroute. An API for you, an MCP server for your AI assistant. Nothing gated behind a plan.

Join the waiting listSee the six checks
Evidence on every incident: captured request and response, secrets redacted, and a traceroute that says where the loss begins
REST API with a published OpenAPI spec, and an MCP server your assistant uses with the same keys
Six check types, status pages on your own domain, seven alert channels, every feature for every team
Alerts arrive in Slack Discord Telegram Teams PagerDuty Email Webhooks

Catch downtime before your customers do

Six kinds of check share one engine, one incident model and one set of alert rules. Pick the interval yourself; the scheduler ticks every second.

Know more than up or down

The details that turn a green dot into something you can act on, and the mechanism that keeps false alarms out of your night.

Tell your customers, wake the right person, keep the evidence

Status pages on your own domain

status.yourcompany.com points at gostatus; the certificate is issued and renewed for you. Your logo and colour, announcements, response-time charts and a monthly uptime calendar.

  • Email subscribers with double opt-in
  • SVG badges and a password gate for private pages
  • English and Hungarian
Explore status pages

Incidents with the evidence attached

Incidents open and resolve off monitor state. Each one carries the request and response from every region, secrets redacted, and a traceroute that says where the loss begins.

  • Acknowledge, set priority, add notes
  • Storm grouping: one summary instead of a flood
  • Hide an incident from the public page
Explore incidents

Alerts where your team already talks

Route each monitor to Slack, Discord, Telegram, Microsoft Teams, PagerDuty, email or a webhook with your own payload. Failure, recovery and reminder thresholds are per monitor.

Explore alerting

An API for you, an MCP server for your assistant

Everything the dashboard does, the REST API does, with a published OpenAPI spec. AI assistants read and manage the same monitors through the built-in MCP server.

list_monitors({ status: "down" })
list_incidents({ open: true })
Explore the API and MCP

Questions we get asked

How does gostatus avoid false alarms?
A monitor runs from Europe and the US. When one region sees a failure the other re-checks, and an incident opens only when the majority agree. A checker that has lost its own uplink stays quiet instead of paging you.
How often are checks run?
You set the interval per monitor. The scheduler ticks every second, and there are no plan tiers while the waiting list is open.
What can I monitor?
HTTP and HTTPS endpoints with JSON assertions, a keyword that must appear or must not, ping, any TCP port, ten DNS record types, and cron jobs or backups through a heartbeat URL. SSL and domain expiry warnings come with HTTP monitors.
Can I keep my status page on my own domain?
Yes. Point a CNAME at gostatus and the certificate is issued and renewed automatically. Branding, announcements, subscribers and a password gate are included.
Can I import from UptimeRobot?
Upload its CSV export as it is. Monitors, groups and intervals come across in one step.
Is there an API?
A REST API with a published OpenAPI spec and keys scoped to read or write, plus an MCP server so Claude and other assistants can work with your monitors using the same keys.

Join the waiting list

We open gostatus to a few teams at a time. Leave your email and we will write when it is your turn.

A confirmation now, and one email when your seat is ready. Nothing else. Privacy Policy