← How this site is run

Reliability

This site runs one small scheduled job and is checked from outside every 5 minutes. Below is how that is going, straight from its own records.

Only 1 day of data so far (since 2026-09-30). The 30-day figures become meaningful once a full window exists.

Right now

Operating normally

Last check
4 min ago
Last shipped
2 h ago (a14f787)
Build
success

Heartbeat freshness

100%

124 of 124 checks good

Objective: 99% over 30 days

Error budget: 0 of 86 allowed failures used · 86 left

Every 5 minutes an outside monitor asks whether this site's status snapshot is less than 30 minutes old.

Scheduled job success

100%

61 of 61 checks good

Objective: 98% over 30 days

Error budget: 0 of 86 allowed failures used · 86 left

Every 10 minutes a job fetches this site's latest commit and build status from GitHub and saves a snapshot.

Last 30 days

Heartbeat freshness

  1. 2026-09-01: no data
  2. 2026-09-02: no data
  3. 2026-09-03: no data
  4. 2026-09-04: no data
  5. 2026-09-05: no data
  6. 2026-09-06: no data
  7. 2026-09-07: no data
  8. 2026-09-08: no data
  9. 2026-09-09: no data
  10. 2026-09-10: no data
  11. 2026-09-11: no data
  12. 2026-09-12: no data
  13. 2026-09-13: no data
  14. 2026-09-14: no data
  15. 2026-09-15: no data
  16. 2026-09-16: no data
  17. 2026-09-17: no data
  18. 2026-09-18: no data
  19. 2026-09-19: no data
  20. 2026-09-20: no data
  21. 2026-09-21: no data
  22. 2026-09-22: no data
  23. 2026-09-23: no data
  24. 2026-09-24: no data
  25. 2026-09-25: no data
  26. 2026-09-26: no data
  27. 2026-09-27: no data
  28. 2026-09-28: no data
  29. 2026-09-29: no data
  30. 2026-09-30: 124 of 124 good

Scheduled job success

  1. 2026-09-01: no data
  2. 2026-09-02: no data
  3. 2026-09-03: no data
  4. 2026-09-04: no data
  5. 2026-09-05: no data
  6. 2026-09-06: no data
  7. 2026-09-07: no data
  8. 2026-09-08: no data
  9. 2026-09-09: no data
  10. 2026-09-10: no data
  11. 2026-09-11: no data
  12. 2026-09-12: no data
  13. 2026-09-13: no data
  14. 2026-09-14: no data
  15. 2026-09-15: no data
  16. 2026-09-16: no data
  17. 2026-09-17: no data
  18. 2026-09-18: no data
  19. 2026-09-19: no data
  20. 2026-09-20: no data
  21. 2026-09-21: no data
  22. 2026-09-22: no data
  23. 2026-09-23: no data
  24. 2026-09-24: no data
  25. 2026-09-25: no data
  26. 2026-09-26: no data
  27. 2026-09-27: no data
  28. 2026-09-28: no data
  29. 2026-09-29: no data
  30. 2026-09-30: 61 of 61 good

2026-09-01today

no failures some failures, objective met objective missed that day no data

Speed

95% of runs were at least this fast. Times are rounded up to the nearest band (50, 100, 200, 400, 800, 1,600, 3,200 ms).

DayScheduled job (GitHub check)Probe check (site's answer)
2026-09-30≤ 1,600 ms≤ 200 ms

Failures

No failures in the last 30 days.

1 slow but successful run (over half the time budget) also recorded as early warnings.

Client path (Pulse run)

A 30-second browser game on this site reports its own errors and frame times. Jank = a frame slower than 50 ms. 60 fps needs about 16 ms.

Sessions
2 (2 played)
Game error rate
0%
p95 frame time
≤ 25 ms
Sessions with jank
50%

Client-only signal. Does not prove server capacity or ITSM readiness.

How to read this

  • Objective (SLO): the share of checks that must succeed over 30 days.
  • Error budget: how many failures the objective allows in 30 days. Spending it is fine; overspending means reliability work comes before new features.
  • The official external number is the outside monitor's 30-day uptime, reported monthly. The figures here are the site's own records of the same checks.
  • All times and days are Toronto time (ET: EDT in summer, EST in winter).

Page requests served in this window: 213 (bots included) · served without the live status line: 0.

Updated 2026-09-30 22:34 EDT · raw data (JSON)