The on-call OSS space has a problem. Of the three self-hostable PagerDuty alternatives our directory recommends, zero are currently alive . Last week's first repo-health snapshot flagged ~11% of all listed self-host alternatives as not-alive. This week we're zooming in on the worst-affected single category: on-call rotation and incident paging. It's not 11%. It's 100%. If you're paying $21–41/user/month for PagerDuty and were planning the self-host escape hatch, the directories you're staring at — including ours — are largely out of date. Here's what May 2026 actually looks like, and what to do instead. The three we listed (and what their health pill says today) Repo Stars Last commit Archived State grafana/oncall 3,881 2026-03-24 yes dead linkedin/oncall 1,249 2025-08-20 no stale cabotapp/cabot — — — 404 from GitHub API Three projects, three different ways of being not-alive. Worth taking each one in turn — the failure modes generalize to any OSS-buying decision in 2026.…