diff --git a/README.md b/README.md index b8de38e1..89616c05 100644 --- a/README.md +++ b/README.md @@ -1,14 +1,6 @@ -# [![Upptime](https://raw.githubusercontent.com/upptime/upptime.js.org/master/static/img/logo.svg)](https://upptime.js.org) +# [📈 Live Status](https://demo.upptime.js.org): **🟧 Partial outage** - - -**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 [Anand Chowdhary](https://anandchowdhary.com), supported by [Pabio](https://pabio.com). - -> I find Upptime an incredible clever usage of \[GitHub Actions]. You essentially get a free configurable uptime monitor for whatever you want. – [CSS Tricks](https://css-tricks.com/upptime/) - -Upptime is used by [**1,000+**](https://github.com/topics/upptime) people and teams to ensure they know when their endpoints go down. - - +This repository contains the open-source uptime monitor and status page for [Upptime](https://upptime.js.org), powered by [Upptime](https://github.com/upptime/upptime). [![Uptime CI](https://github.com/upptime/upptime/workflows/Uptime%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Uptime+CI%22) [![Response Time CI](https://github.com/upptime/upptime/workflows/Response%20Time%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Response+Time+CI%22) @@ -16,7 +8,7 @@ Upptime is used by [**1,000+**](https://github.com/topics/upptime) people and te [![Static Site CI](https://github.com/upptime/upptime/workflows/Static%20Site%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Static+Site+CI%22) [![Summary CI](https://github.com/upptime/upptime/workflows/Summary%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Summary+CI%22) -## [📈 Live Status](https://demo.upptime.js.org): **🟧 Partial outage** +With [Upptime](https://upptime.js.org), you can get your own unlimited and free uptime monitor and status page, powered entirely by a GitHub repository. We use [Issues](https://github.com/upptime/upptime/issues) as incident reports, [Actions](https://github.com/upptime/upptime/actions) as uptime monitors, and [Pages](https://demo.upptime.js.org) for the status page. @@ -24,84 +16,21 @@ Upptime is used by [**1,000+**](https://github.com/topics/upptime) people and te | URL | Status | History | Response Time | Uptime | | --- | ------ | ------- | ------------- | ------ | -| [Google](https://www.google.com) | 🟩 Up | [google.yml](https://github.com/upptime/upptime/commits/HEAD/history/google.yml) |
Response time graph 142ms
Response time 106
24-hour response time 95
7-day response time 142
30-day response time 112
1-year response time 110
|
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 99.98%
-| [Wikipedia](https://en.wikipedia.org) | 🟩 Up | [wikipedia.yml](https://github.com/upptime/upptime/commits/HEAD/history/wikipedia.yml) |
Response time graph 278ms
Response time 222
24-hour response time 113
7-day response time 278
30-day response time 177
1-year response time 230
|
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%
-| [Hacker News](https://news.ycombinator.com) | 🟩 Up | [hacker-news.yml](https://github.com/upptime/upptime/commits/HEAD/history/hacker-news.yml) |
Response time graph 244ms
Response time 348
24-hour response time 117
7-day response time 244
30-day response time 321
1-year response time 303
|
100.00%All-time uptime 98.83%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 100.00%
-| [Test Broken Site](https://thissitedoesnotexist.koj.co) | 🟥 Down | [test-broken-site.yml](https://github.com/upptime/upptime/commits/HEAD/history/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 7.96%
1-year uptime 0.00%
-| [IPv6 test](forwardemail.net) | 🟥 Down | [i-pv6-test.yml](https://github.com/upptime/upptime/commits/HEAD/history/i-pv6-test.yml) |
Response time graph 0ms
Response time 4
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.01%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 7.96%
1-year uptime 0.00%
+| [PWS Homepage](https://www.whitney.rip) | 🟩 Up | [pws-homepage.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/pws-homepage.yml) |
Response time graph 509ms
Response time 509
24-hour response time 509
7-day response time 509
30-day response time 509
1-year response time 509
|
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%
+| [Jake Runyan Portfolio](https://jake.runyan.dev) | 🟩 Up | [jake-runyan-portfolio.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/jake-runyan-portfolio.yml) |
Response time graph 368ms
Response time 368
24-hour response time 368
7-day response time 368
30-day response time 368
1-year response time 368
|
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%
+| [Jake Runyan Photography](https://jakesphotos.whitney.rip) | 🟥 Down | [jake-runyan-photography.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/jake-runyan-photography.yml) |
Response time graph 551ms
Response time 551
24-hour response time 551
7-day response time 551
30-day response time 551
1-year response time 551
|
11.75%All-time uptime 11.75%
24-hour uptime 11.75%
7-day uptime 11.75%
30-day uptime 11.75%
1-year uptime 11.75%
+| [Google](https://www.google.com) | 🟩 Up | [google.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/google.yml) |
Response time graph 278ms
Response time 278
24-hour response time 278
7-day response time 278
30-day response time 278
1-year response time 278
|
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](https://en.wikipedia.org) | 🟩 Up | [wikipedia.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/wikipedia.yml) |
Response time graph 39ms
Response time 39
24-hour response time 39
7-day response time 39
30-day response time 39
1-year response time 39
|
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%
+| [Hacker News](https://news.ycombinator.com) | 🟩 Up | [hacker-news.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/hacker-news.yml) |
Response time graph 357ms
Response time 357
24-hour response time 357
7-day response time 357
30-day response time 357
1-year response time 357
|
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%
+| [Test Broken Site](https://thissitedoesnotexist.koj.co) | 🟥 Down | [test-broken-site.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/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
|
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%
+| [IPv6 test](forwardemail.net) | 🟥 Down | [i-pv6-test.yml](https://github.com/whitney-server/upptime/commits/HEAD/history/i-pv6-test.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
|
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 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](https://raw.githubusercontent.com/upptime/upptime.js.org/master/static/img/screenshot-status.png)](https://upptime.js.org) - -## 👩‍💻 [Documentation](https://upptime.js.org) - -1. [How it works](https://upptime.js.org/docs) -1. [Getting started](https://upptime.js.org/docs/get-started) -1. [Configuration](https://upptime.js.org/docs/configuration) -1. [Triggers](https://upptime.js.org/docs/triggers) -1. [Notifications](https://upptime.js.org/docs/notifications) -1. [Badges](https://upptime.js.org/docs/badges) -1. [Packages](https://upptime.js.org/docs/packages) -1. [Contributing](https://upptime.js.org/docs/contributing) -1. [Frequently Asked Questions](https://upptime.js.org/docs/faq) - -### 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 #67](https://github.com/upptime/upptime/issues/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](https://github.com/koj-co/upptime/commits/master/history/wikipedia.yml)). 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 -
- +[**Visit our status website →**](https://demo.upptime.js.org) ## 📄 License +- Powered by: [Upptime](https://github.com/upptime/upptime) - Code: [MIT](./LICENSE) © [Anand Chowdhary](https://anandchowdhary.com), supported by [Pabio](https://pabio.com) - Data in the `./history` directory: [Open Database License](https://opendatacommons.org/licenses/odbl/1-0/)