⬆️ Uptime monitor and status page powered by GitHub Actions, Issues, and Pages
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Upptime Bot 43c5e3b41a
🟥 Test Broken Site is down (0 in 0 ms) [skip ci] [upptime]
5 hours ago
.github ⬆️ Update @upptime to v1.29.0 1 month ago
api 🍱 Update graphs [skip ci] 1 day ago
assets 🚚 Rename static to assets 2 years ago
graphs 🍱 Update graphs [skip ci] 1 day ago
history 🟥 Test Broken Site is down (0 in 0 ms) [skip ci] [upptime] 5 hours ago
.gitattributes 📝 Update summary in README [skip ci] [upptime] 6 months ago
.templaterc.json 🔧 Add .templaterc.json config file 2 years ago
.upptimerc.yml 🔧 Update test site URLs 2 years ago
LICENSE 📄 Add MIT license 3 years ago
README.md 📝 Update summary in README [skip ci] [upptime] 16 hours ago



Upptime (https://upptime.js.org) is the open-source uptime monitor and status page, powered entirely by GitHub Actions, Issues, and Pages. It's made with 💚 by your friends at Koj.

I find Upptime an incredible clever usage of [GitHub Actions]. You essentially get a free configurable uptime monitor for whatever you want. CSS Tricks

Upptime is used by 1,000+ people and teams to ensure they know when their endpoints go down.

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

📈 Live Status: 🟧 Partial outage

URL Status History Response Time Uptime
Google 🟩 Up google.yml
Response time graph 131ms
Response time 95
24-hour response time 80
7-day response time 131
30-day response time 104
1-year response time 95
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%
Wikipedia 🟩 Up wikipedia.yml
Response time graph 276ms
Response time 211
24-hour response time 119
7-day response time 276
30-day response time 254
1-year response time 210
100.00%All-time uptime 99.99%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
Hacker News 🟩 Up hacker-news.yml
Response time graph 313ms
Response time 309
24-hour response time 164
7-day response time 313
30-day response time 317
1-year response time 302
98.73%All-time uptime 97.99%
24-hour uptime 99.54%
7-day uptime 98.73%
30-day uptime 99.71%
1-year uptime 94.75%
Test Broken Site 🟥 Down test-broken-site.yml
Response time graph 0ms
Response time 0
24-hour response time 0
7-day response time 0
30-day response time 0
1-year response time 0
0.00%All-time uptime 0.00%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 1.38%
1-year uptime 0.00%

How it works

  • GitHub Actions is used as an uptime monitor
    • Every 5 minutes, a workflow visits your website to make sure it's up
    • Response time is recorded every 6 hours and committed to git
    • Graphs of response time are generated every day
  • GitHub Issues is used for incident reports
    • An issue is opened if an endpoint is down
    • People from your team are assigned to the issue
    • Incidents reports are posted as issue comments
    • Issues are locked so non-members cannot comment on them
    • Issues are closed automatically when your site comes back up
    • Slack notifications are sent on updates
  • GitHub Pages is used for the status website
    • A simple, beautiful, and accessible PWA is generated
    • Built with Svelte and Sapper
    • Fetches data from this repository using the GitHub API

Upptime is not affiliated to or endorsed by GitHub.

Screenshot of status website

👩‍💻 Documentation

  1. How it works
  2. Getting started
  3. Configuration
  4. Triggers
  5. Notifications
  6. Badges
  7. Packages
  8. Contributing
  9. Frequently Asked Questions


Issues as incidents

When the GitHub Actions workflow detects that one of your URLs is down, it automatically opens a GitHub issue (example issue #67). You can add incident reports to this issue by adding comments. When your site comes back up, the issue will be closed automatically as well.

Screenshot of GitHub issue Screenshot of incident page

Commits for response time

Four times per day, another workflow runs and records the response time of your websites. This data is committed to GitHub, so it's available in the commit history of each file (example commit history). Then, the GitHub API is used to graph the response time history of each endpoint and to track when a site went down.

Screenshot of GitHub commits Screenshot of live status

📄 License


An open source project by Koj.
Furnish your home in style, for as low as CHF175/month →