Better Stack (Uptime)
Uptime monitoring and incident management service that alerts teams when websites or services go down
Upptime
Self‑hosted uptime monitor and status page powered by GitHub Actions
Self‑hosted uptime monitor and status page that runs entirely on GitHub Actions, Issues, and Pages—no extra servers, fully version‑controlled, and provides instant incident tracking.
Overview
What Upptime Does
Upptime turns GitHub Actions into a lightweight uptime monitor. Every five minutes (or on a custom schedule) a workflow pings each configured endpoint, records response time, and commits the data to the repository. When a check fails, an incident GitHub Issue is opened, comments can be added, and the issue closes automatically once the service recovers.
Features and Deployment
All configuration lives in a single YAML file in the repo, so changes are version‑controlled and auditable. Response‑time history is stored as git commits, enabling long‑term trend charts displayed on a status page built with Svelte and served via GitHub Pages. Optional Slack notifications keep teams informed, and the entire system requires no external servers—just a GitHub repository and Actions.
Who Should Use It
Developers, open‑source projects, and small‑to‑medium teams that already host code on GitHub can add reliable monitoring and a public status page with minimal effort and zero hosting cost.
Highlights
GitHub Actions runs checks as often as every 5 minutes
Automatic GitHub Issue creation for downtime incidents
Status page hosted on GitHub Pages with Svelte‑generated UI
Response‑time history stored in git for audit‑trail and charts
Pros
- Zero hosting cost for GitHub users
- Full audit trail via git commits
- Customizable via a single YAML configuration file
- Built‑in Slack notifications for team alerts
Considerations
- Relies on GitHub service availability
- Minimum check interval limited to 5 minutes
- Private repositories required for confidential data
- Limited to GitHub ecosystem for alerts and hosting
Managed products teams compare with
When teams consider Upptime, these hosted platforms usually appear on the same shortlist.
Looking for a hosted option? These are the services engineering teams benchmark against before choosing open source.
Fit guide
Great for
- Developers who already use GitHub for code
- Small to medium teams needing a free status page
- Open‑source projects wanting transparent incident logs
- Startups looking for low‑cost monitoring
Not ideal when
- Enterprises requiring guaranteed SLA monitoring
- Use cases needing sub‑minute check intervals
- Organizations without GitHub access
- Teams needing on‑premise data residency
How teams use it
Public website uptime monitoring
Automated checks detect downtime, open issues, and update a public status page instantly.
Internal API health dashboard
Team receives Slack alerts and can view response‑time trends directly in the repository.
Open‑source project incident transparency
All incidents are recorded as GitHub issues, providing a public audit trail for contributors.
Startup service status communication
Customers access a branded status page while the team manages incidents through GitHub.
Tech snapshot
JSON51%
Markdown44%
YAML5%
Frequently asked questions
What do I need to run Upptime?
A GitHub repository (public or private) and GitHub Actions enabled.
How often are checks performed?
The default schedule runs every five minutes, but the interval can be customized in the workflow.
Where is the status page hosted?
The status page is generated with Svelte and served via GitHub Pages.
Can I receive alerts outside of GitHub?
Yes, Upptime supports Slack notifications and can be extended to other services via custom actions.
Is my monitoring data private?
If the repository is private, all monitoring data and incident issues remain private.
Project at a glance
Active- Stars
- 16,806
- Watchers
- 16,806
- Forks
- 1,016
LicenseMIT
Repo age5 years old
Last commit15 hours ago
Primary languageJSON
Last synced 3 hours ago