Skip to content
Get started

Uptime monitoring

Know your API is down before your customers tell you

Uptime monitoring is in development. ROOKON checks your API routes and pages around the clock, opens an incident when one fails twice in a row, alerts your team and keeps a public status page current. Because it is part of ROOKON, every outage also becomes an issue with a diagnosis and, where it fits, a proposed fix.

Get started Try the live demos

The problem

An outage alert is the start of the work, not the end

Classic uptime tools tell you that something is down. Then the investigation starts somewhere else: logs, errors, recent deploys. Meanwhile customers find out first and support tickets pile up.

  • Customers notice outages before the team does
  • Alerts arrive without any context about the cause
  • Status updates are written by hand in the middle of an incident
  • One-off monitoring scripts that nobody maintains

Live demo 1 of 2

Watch a monitor go down and come back

Simulated checks of a fictional API. One monitor fails, an incident opens, alerts go out, ROOKON creates an issue and diagnoses it within the AI budget, then the service recovers.

  • Add a suggested route
  • Try to monitor https://example.org/

rookon · uptime · acme-cloud

Simulated data

Monitors · checked every 60 s

Live
  • Websitehttps://acme.example/up243 ms
  • API healthhttps://api.acme.example/healthup121 ms
  • Invoices APIhttps://api.acme.example/v1/invoicesup317 ms
  • Checkout APIhttps://api.acme.example/v1/checkout/sessionup315 ms

We found these routes on your domains

  • https://acme.example/healthhealth endpoint
  • https://acme.example/healthzhealth endpoint
  • https://acme.example/api/healthhealth endpoint
  • https://acme.example/statushealth endpoint

Try https://example.org/ to see the own-domains rule.

What happened

All monitors are up. This simulation scripts an outage in a moment.

Alert channels

  • Email · ops@acme.example
  • Webhook · your endpoint
  • Slack and Discord · coming soon

Simulated checks. One failed check never pages anyone: a monitor goes down after two in a row.

How ROOKON helps

What you get

  • Unlimited monitors for your own routes

    Monitors are unlimited on every plan, under a fair-use limit per project. Check pages and API endpoints every 1, 5 or 15 minutes; only hosts that belong to your project can be monitored.

  • Suggested routes

    ROOKON suggests health endpoints, routes from your OpenAPI spec and API paths seen in real traffic, so the important checks exist from day one.

  • No page for a single blip

    A monitor goes down only after consecutive failures and recovers on the first success. Slow responses are flagged as degraded before they become outages.

  • Alerts where you look

    Email and signed webhooks first. Slack and Discord are planned.

  • A status page that updates itself

    Show components and 90 days of uptime on a public page. Incidents open and resolve with your monitors, and you can add updates in plain language.

  • From outage to diagnosis

    Every incident creates a ROOKON issue, so diagnosis runs within your AI budget and a fix can arrive as a commit request.

Live demo 2 of 2

The status page your customers see

A simulated public status page: 90 days of uptime per component and an incident that moves from investigating to resolved.

  • Hover a day in the uptime bars

status.acme.example

Simulated data

Acme Cloud status

Live

All systems operational

Everything is up and responding normally.

24 h
100%
30 days
99.91%
90 days
99.87%
Badge: 99.87% uptime over 90 days, measured by ROOKON (simulated)
Earned from ROOKON’s checks. Embed it in your README.

Website

  • WebsiteOperational99.95%
    90 days ago 117 mstoday
  • DashboardOperational100%
    90 days ago 101 mstoday

API

  • Invoices APIOperational99.90%
    90 days ago 165 mstoday
  • Checkout APIOperational99.81%
    90 days ago 166 mstoday
  • WebhooksOperational99.72%
    90 days ago 104 mstoday

Incident history

  1. ResolvedWebhooks delayedDegraded · 40 days ago · lasted 2 h 10 min
  2. ResolvedInvoices API errorsOutage · 33 days ago · lasted 38 min
  3. ResolvedCheckout API errorsOutage · 12 days ago · lasted 1 h 4 min

Simulated data. Public pages show only the monitors you mark public, never URLs, headers or error details.Powered by ROOKON

What happens when a check fails

  1. 01

    Two failures in a row

    The monitor goes down; one failed check alone never pages anyone.

  2. 02

    Incident and alerts

    An incident opens and your email or webhook channels are notified.

  3. 03

    Issue and diagnosis

    ROOKON creates an issue and diagnoses it, inside your AI budget.

  4. 04

    Recovery

    The first successful check resolves the incident and updates the status page.

FAQ

Common questions

Is uptime monitoring available now?

Not yet. It is in development, and this page will be updated when it is available.

Which alert channels are supported?

Email and signed webhooks first. Slack and Discord are planned and marked as such in the product.

Can I monitor any URL?

No. Only your project’s own domains and their subdomains can be monitored, and ROOKON refuses private, loopback and cloud metadata addresses, so it can’t be used to probe other sites or internal networks.

How many monitors can I create?

Monitors are unlimited on every plan. A fair-use limit per project, shown openly in the product, protects the service from abuse.

How often are checks run?

Every 1, 5 or 15 minutes per monitor. One minute is the minimum, so monitoring never floods your own servers.

What appears on the public status page?

Only the monitors you mark public, their current state, 90 days of uptime and incident updates. URLs, headers and error details are never shown.

Related

Find out about outages first

Sign up and add your first monitor in the setup journey.

Get started with ROOKONExplore live demo