Public status page for FactChat — https://mindlogic-ai.github.io/factchat-status/
Built on Upptime: GitHub Actions probes every 5 minutes, history committed to this repo, static site published to GitHub Pages. It runs outside our own infrastructure on purpose, so it stays up when FactChat doesn't.
Edit sites: in .upptimerc.yml. Commented-out entries are waiting on health endpoints
(FTC-1957 BE, FTC-1958 SSO) — uncomment once those deploy.
Automated probes catch reachability, not correctness. Billing errors, a single broken tenant,
degraded model quality — none of those turn a monitor red. Open an issue in this repo with the
incident label and the affected site's label; it appears on the status page immediately.
Severity, who may declare, and posting SLA are defined in FTC-1960.
- Probes run from GitHub-hosted runners in the US. Response-time graphs are useful as a trend, not as a measure of what Korean users experience.
- Anything IP-allowlisted is unreachable from those runners. SGI (
sgi-factchat) is excluded for this reason. - Custom domain (
status.factchat.bot) is on hold.*.factchat.botis a wildcard CNAME to Vercel, so that name needs an explicit Cloudflare record (DNS-only) to reach GitHub Pages. - The app lives on tenant subdomains;
factchat.botapex is the landing page and is monitored separately.