/upptime

⬆️ Uptime monitor and status page powered by GitHub

MIT LicenseMIT

Upptime

Upptime (https://upptime.js.org) is the open-source uptime monitor and status page, powered entirely by GitHub Actions and Issues.

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 88ms Uptime 100.00%
Wikipedia 🟩 Up wikipedia.yml Response time graph 140ms Uptime 100.00%
Hacker News 🟩 Up hacker-news.yml Response time graph 337ms Uptime 100.00%
Broken Site 🟥 Down broken-site.yml Response time graph 0ms Uptime 0.00%
Secret Site 🟩 Up secret-site.yml Response time graph 50ms Uptime 100.00%

This README is also available in 🇧🇷 Brazilian Portuguese

⭐ 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 are 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 are 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

Screenshot of status website

💝 Who's using Upptime

upptime/.github dlunch/upptime fjoker/upptime kong67/status jeongsk/upptime empmdk/upptime gwanryo/upptime phg98/upptime nhammond101/upptime theleetax/uptime tadacodes/tada-uptime godong9/gdgo bbonkr/uptime fullprofile/status_monitor Jolg42/upptime jjeaby/mew 9min/upptime ffsh/uptime JonathanTreffler/status Melangebox/status OswaldLabsOpenSource/status kyupark/upptime picchiosat/HBLink-Uptime ludicroushq/upptime brianjhanson/upptime-test jeyraof/otzil-upptime cubi-io/upptime hada-io/upptime cocktail-lucas/cocktail-upptime kt-chelsea/status koj-co/status Cleverclip/status AnandChowdhary/status chowdhary-org/status EnsembleTravelGroup/EnsembleTravelUpptime sebastianroming/status.webmonkey.io armand1m-development/status arkk4/services.arkk4.com jtprog/status.jtprog.ru classtinginc/upptime mapeaks/mapeaks.github.io intakefoods/status.intakefoods.kr r2fresh/chelsea coinsambacom/upptime rmateu/statuspage camphor-/status p1ass/status AiLingGo/mew Shulert/status Cravemob/mog-status doggy0425/monitoring kspbot/uptime amblerkr/upptime bagiduid/uptime SOLPLPARTY/upptime baealex/upptime M17-Project/upptime butteryoon/liveseeyou stethoscope-js/status belhyun/yonsei-upptime mikesprague/skydark-status snapwiki/SnapWikiUptime eartharoid-bot/status humanscape/service-status mue/status wakatime/statuspage

👩‍💻 Documentation

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

Concepts

Issues as incidents

When the GitHub Actions workflow detects that one of your URLs is down, it automatically opens a GitHub issue (example issue #15). 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 commited 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

Koj

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