Home / Status

Is the site up?

Loading the latest checks.

Availability, 30 days
·
target 99.5%
Error budget left
·
0.5% of checks may fail
Median response
·
homepage, from GitHub Actions
Checks recorded
·
scheduled, run by GitHub Actions

Recent checks

The latest 96 checks. Each bar is one request to the homepage and the resume. GitHub runs scheduled jobs when it has capacity, so the gaps between checks vary.

Recent builds

Every push runs Lighthouse three times on the mobile profile. These are the medians. A build that misses the budget fails the check and shows a red cross on the commit.

Loading build history.

Targets

  • Availability: 99.5% of scheduled checks succeed over 30 days. That allows about 7 failed checks a month.
  • Speed: Lighthouse performance at least 90 and largest contentful paint under 2.5 seconds on the mobile profile.
  • Accessibility: Lighthouse accessibility at least 95.
  • Weight: under 10 KB of JavaScript before the 3D. The 3D code is about 130 KB compressed and only loads on desktop.

What this does and doesn't measure

The site is hosted on Vercel and the checks run from GitHub Actions, so the checker and the thing being checked are on different providers. It's still one probe from one place, so it can't tell a real outage from a network blip near GitHub. GitHub also delays scheduled jobs when it's busy, so gaps between bars don't always mean anything.

If I needed real monitoring I'd probe from a few regions and alert on two failed checks in a row, not one.