
Upptime
A free uptime monitor and status page that runs on GitHub Actions, Issues, and Pages.
- Stars
- 17.2k
- Forks
- 1k
- Licence
- MIT
- Language
- Markdown
- Last update
- 4 days ago
- Type
- App
What it is
Upptime checks whether your websites or services are online, using scheduled GitHub Actions runs as often as every 5 minutes. It records response times in git, opens and closes GitHub Issues when downtime is detected, and publishes a status page with uptime and incident history via GitHub Pages. Its configuration lives in a single file in your repository.
- Monitor a list of website URLs and get a GitHub Issue when one goes down
- Publish a public status page with uptime percentages and response time graphs
- Keep a historical record of response times committed to git for trend charts
- Track incident history in a status page that updates automatically
Great for
- Developers who already use GitHub and want a free uptime monitor
- Small teams or startups that want a public status page without a paid service
- People who want their monitoring data under their own control in a git repository
- Anyone who wants a git-based audit trail of uptime changes and incidents
Not ideal for
- Teams that need checks more frequent than the scheduled interval GitHub Actions supports, since checks run as often as every 5 minutes
- Users who do not use GitHub, because the project depends on GitHub Actions, Issues, and Pages
- Organizations needing enterprise features like guaranteed alert routing, since the README does not describe these
How to get it
- 1
Clone and build from source
Clone the repository
git clone https://github.com/upptime/upptime - 2
Run it
- Fork or create a repository from the Upptime template on GitHub
- Edit the single configuration file to list the URLs you want to monitor
- Enable GitHub Actions and GitHub Pages for your repository
- Wait for the scheduled workflows to run, then view your status page
- 3
Get the most out of it
- Use the status page to share uptime and incident history publicly
- Use the git history to review past response times and changes
- Adjust the monitored endpoints in the single configuration file as your services change
Downloads
Strengths
- Free to run when you already use GitHub, with no external server or subscription described in the README
- All configuration is in one file, and data stays in your own repository
- Response times and incidents are recorded in git, giving a full change history
Trade-offs
- Data is tied to the repository; the README says your data is gone if you delete the repo
- Monitoring depends on GitHub Actions scheduling, so check timing is not guaranteed to be exact
- The README is truncated here, so details on alerting options and setup complexity are not fully confirmed
How it compares
| Project | Stars | Type | Level | Updated | Best for |
|---|---|---|---|---|---|
| upptime (this) | 17.2k | App | intermediate | 4 days ago | Developers who already use GitHub and want a free uptime monitor |
| uptime-kuma | 93.2k | App | beginner | 4 days ago | People who want to monitor their own websites or services without paying a hosted monitoring service |
Stats synced from GitHub. The assessment above was drafted with AI from the project's README on 2026-10-29 and may miss recent changes — check the README before relying on a command. MIT licence: free to use, modify and distribute, including commercially, as long as you keep the copyright notice.