Skip to content

Latest commit

Β 

History

278 Commits

Folders and files

NameName
Last commit message
Last commit date
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

πŸ“ˆ Live Status: 🟩 All systems operational

Live status and uptime history for the Theo ecosystem β€” automated, public, and auditable by git. Status page: status.usetheo.dev

Uptime CI Response Time CI Graphs CI Static Site CI Summary CI

URL Status History Response Time Uptime
usetheo.dev (marketing site) 🟩 Up usetheo-dev-marketing-site.yml
Response time graph 251ms
Response time 217
24-hour response time 294
7-day response time 251
30-day response time 232
1-year response time 217
100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
Docs (docs.usetheo.dev) 🟩 Up docs-docs-usetheo-dev.yml
Response time graph 210ms
Response time 178
24-hour response time 222
7-day response time 210
30-day response time 179
1-year response time 178
100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
Blog (blog.usetheo.dev) 🟩 Up blog-blog-usetheo-dev.yml
Response time graph 193ms
Response time 179
24-hour response time 210
7-day response time 193
30-day response time 178
1-year response time 179
100.00%All-time uptime 100.00%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%

How this works

This repository is the status infrastructure itself β€” powered by Upptime, with no server anywhere:

  • GitHub Actions checks every monitored endpoint every 5 minutes and records response times as git commits β€” the uptime history in history/ is append-only and auditable.
  • GitHub Issues are the incident log: when an endpoint goes down, an issue opens automatically with a timeline, and closes when it recovers. Every incident this ecosystem has ever had is public in Issues.
  • GitHub Pages serves the status site at status.usetheo.dev.

By design, none of this runs on the infrastructure it monitors. If usetheo.dev or TheoCloud have a bad day, this page does not go down with them.

Why it's public

Part of Theo's honesty policy: uptime claims should be backed by accumulated, verifiable history β€” not by a badge. This repo is that history, from day one (2026-07-07). If a check fails, it lands here too.

Configuration

Everything lives in .upptimerc.yml: the monitored endpoints, the status site branding, and the custom domain. To add an endpoint, add a sites: entry and push β€” the next cron cycle picks it up. Full options: Upptime docs.

Operational notes:

  • get.usetheo.dev is intentionally not monitored yet β€” the domain doesn't resolve today. Add it the day it ships; a monitor born red is noise, not signal.
  • DNS for status.usetheo.dev is a Cloudflare-proxied CNAME to usetheodev.github.io; HTTPS is served by the Cloudflare edge (zone SSL mode full). Don't unproxy the record without a plan β€” GitHub Pages' own certificate was never issued.
  • Workflow files under .github/ are synced from the upstream Upptime template (see .templaterc.json) β€” customize behavior via .upptimerc.yml, not by editing workflows.

License

About

Public status page + uptime monitor for the Theo ecosystem (Upptime)

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

Generated from upptime/upptime