Skip to content
Uptime monitoring

Uptime monitoring that shows what broke

Spectate checks your websites, APIs, ports, DNS records and mail servers every 30s or 60s, rechecks before it alerts, and keeps a screenshot and the response when a website goes down.

8 protocols
HTTP(S), ping, TCP, DNS, SMTP, IMAP and POP3.
Rechecked before it alerts
One dropped packet never pages anyone.
Evidence, not a red dot
A screenshot and the response for every outage.
What you can monitor

Websites, APIs, ports, DNS and mail servers

HTTP(S) monitors check the status code and can require a keyword, with your own method, headers and auth. Ping, TCP, DNS and mail monitors cover the rest.

  • Expected status codes, keyword present or missing
  • Custom headers with basic, bearer or digest auth
  • SMTP, IMAP and POP3 without logging in
Create monitor

Websites and APIs, ping, TCP ports, DNS records and mail servers. Headers, keywords, authentication and thresholds live in the monitor settings afterwards.

Type
Web
HTTPSHTTP
Network
PingTCPDNS
Mail
SMTPIMAPPOP3
Status code, keyword, response times and the certificate.
Target
https://api.kestrel.eu/checkout/health
Name
Checkout API
Interval
30 seconds ⌄
esc to closeCreate pausedCreate and start
Where we check from

Four regions to check from

Checkers run in Amsterdam, New York, Singapore and Sydney. Each monitor is checked from the region you pick, and a failed check is repeated from the same region before anyone is alerted.

  • One region per monitor, chosen by you
  • Every failure rechecked before the monitor goes down
  • Every 30s on Team and Business, 60s on Starter
Create monitor

Pick the region closest to your users. A failed check is rechecked from the same region before anyone is alerted.

Primary region
EuropeNorth AmericaAsiaOceania
Notify
Team default · Production critical
Checks every 30s from AmsterdamCreate and start
When it goes down

See what the checker saw

Spectate keeps the response the checker got and, if the page answered, a screenshot from the same region. The alert explains the error in plain words and what to check first.

  • Screenshot from the region that saw the failure
  • Response body and headers, credentials redacted
  • Kept for 90 days
  1. Kestrel
  2. Alerts
  3. Checkout API is down

What we saw

From Europe,

api.kestrel.eu/checkout/health
503 Service Temporarily Unavailablenginx
Screenshot from Europe (Amsterdam)
The server is up but couldn't handle the request
HTTP 503 Service Unavailable
Status
503 · HTTP/2
URL
https://api.kestrel.eu/checkout/health
Answered by
185.42.204.36:443
Response time
38 ms
Body
197 B · text/html
Page title
503 Service Temporarily Unavailable
Response time

Response time down to each request phase

Every check times DNS, connect, TLS, first byte and transfer. Alert on a hard limit, or when responses get slower than their own recent average.

  • Timings per phase of the request
  • Hard threshold or deviation from the baseline
  • Response time chart in the alert itself
  1. Kestrel
  2. Monitors
  3. Checkout API
  4. Performance
Timings from Europe
Average
192ms
p50
184ms
p95
236ms

Waterfall

Average phase durations over successful checks

  • DNS11ms
  • Connect23ms
  • TLS41ms
  • Waiting96ms
  • Transfer21ms
In detail

Everything in uptime monitoring

Intervals from 30s to 1 hour

30s on Team and Business, 60s on Starter, longer on every plan.

Redirects and timeouts

Follow up to 10 redirects, with a timeout of 1 to 60 seconds.

Certificate checks included

HTTPS and TLS monitors watch the whole certificate chain too.

Uptime history

Every check for 90 days, hourly rollups for 13 months.

Pause and resume

Pause during planned work without losing history.

Routing per monitor

Use the project's escalation path, the default or specific paths.

Included on every plan. See pricing

FAQ

Uptime monitoring: questions

How often does Spectate check my website?

Every 30 seconds on the Team and Business plans and every 60 seconds on Starter. You can also choose longer intervals of 2, 3, 5, 10, 15 or 30 minutes, or 1 hour, per monitor. A failed check is repeated a few seconds later before the monitor is marked down.

What happens when my site goes down?

The checker repeats the check a few seconds later from the same region. If it fails again, Spectate marks the monitor down, records the response and a screenshot, and starts the escalation path: it notifies channels such as email, Slack or SMS, pages whoever is on call and can open an incident. When the site recovers, the alert resolves itself.

Which locations does Spectate monitor from?

Spectate has checkers in four regions: Europe (Amsterdam), North America (New York), Asia (Singapore) and Oceania (Sydney). Each monitor is checked from one region that you choose, so pick the region closest to your users or your servers. You can change the region at any time in the monitor's settings.

Can Spectate monitor APIs and not just websites?

Yes. HTTP(S) monitors can send GET, POST, PUT, PATCH, DELETE or HEAD requests with custom headers and basic, bearer or digest authentication. They check the status code, can require or forbid a keyword in the response, and measure each phase of the request, so they work for JSON health endpoints as well as web pages.

Does Spectate take screenshots of my site when it is down?

Yes, on every plan. When an HTTP(S) monitor goes down and the server still sends a response, the checker opens the page in a headless browser from the same region and stores a screenshot next to the response body and headers. Screenshots are kept for 90 days and shown on the alert page.

Is there a free plan?

No. Spectate has no free plan, but every new team gets a 14-day trial of the Team plan without payment details. After that, Starter costs €0.75 per monitor a month with a minimum of 20 monitors, Team €0.60 with a minimum of 80, and Business €0.50 with a minimum of 250. Prices exclude VAT.

Know about it first.

Set up your first monitor in under a minute. 14 days free, no credit card.