Skip to content
yourwebsite.com3 sitesIV

Demo Example data for one website. Tenvey is not running yet — nothing here is being measured live.

0Score

yourwebsite.comchecked 40 seconds ago

Your site answered 129,523 of the last 129,600 checks.

That is 99.94% availability over 90 days. The critical issue open here is an endpoint failure rather than an outage — /checkout returns an error while the site itself keeps answering.

Availability

Rolling 90 days

Uptime
99.94%over 90 days
Checks run
129,600one every 60 s
Checks failed
770.06% of the window
Regions in rotation
4one each per 4 min
Incidents
1in 90 days
Longest incident
47 minutes12 June

Open issues

Monitoring

Checkout returns a server error

Critical

128 requests to /checkout returned a 500 in the last 24 hours, starting 14 minutes after deployment v2.4.1.

Next step

Roll back v2.4.1 or fix the payment handler it changed. This blocks every purchase.

Evidence

POST /checkout → 500 Internal Server Error · 128 occurrences · first at 16:38, last at 23:51

/checkout128 occurrencesfirst seen 16:38

No warnings or notices in monitoring.

A single failed check never opens one: Tenvey waits for two consecutive failures from the same region before it files anything below critical.

Checks by region

Every 60 s

  • Answering: Zurich186 mslast check 14:32:04HTTP 200
  • Answering: Frankfurt201 mslast check 14:31:04HTTP 200
  • Answering: Virginia243 mslast check 14:30:04HTTP 200
  • Last check failed: Singaporeno responselast check 14:29:04HTTP 500

Last five checks

  • 14:32:04 Zurich200186 ms
  • 14:31:04 Frankfurt200201 ms
  • 14:30:04 Virginia200243 ms
  • 14:29:04 Singapore500—
  • 14:28:04 Zurich200192 ms

The failed check from Singapore did not open an incident. Tenvey waits for a second consecutive failure from the same region before it calls a site down.

Incident history

90 days

  1. Yesterday · 16:38

    Ongoing

    /checkout started returning 500

    128 requests have failed since. The homepage check keeps passing, which is why this never opened an outage — it is an endpoint failure, and it is still open.

  2. Yesterday · 16:24

    Deployment

    Deployment v2.4.1 went live

    14 minutes before the first 500, and the same moment the response curve steps up. Everything that changed on this site yesterday changed here.

  3. 12 June · 47 minutes

    Resolved

    The site was unreachable from every region

    The only full outage in the 90-day window, and the reason uptime reads 99.94% rather than 100%.