From 49f0074d38711aec6142ce12e55d192ef24c3f2d Mon Sep 17 00:00:00 2001 From: Upptime Bot <73812536+upptime-bot@users.noreply.github.com> Date: Fri, 18 Oct 2024 06:59:22 +0000 Subject: [PATCH] :pencil: Update summary in README [skip ci] [upptime] --- README.md | 105 +++++++++--------------------------------------------- 1 file changed, 16 insertions(+), 89 deletions(-) diff --git a/README.md b/README.md index 5359a087..6f7c6db1 100644 --- a/README.md +++ b/README.md @@ -1,22 +1,14 @@ -# [![Upptime](https://raw.githubusercontent.com/upptime/upptime.js.org/master/static/img/logo.svg)](https://upptime.js.org) +# [📈 Live Status](https://ivuorinen.net): **🟧 Partial outage** - +This repository contains the open-source uptime monitor and status page for [Ismo Vuorinen](https://ivuorinen.net/), powered by [Upptime](https://github.com/upptime/upptime). -**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). +[![Uptime CI](https://github.com/ivuorinen/uptime/workflows/Uptime%20CI/badge.svg)](https://github.com/ivuorinen/uptime/actions?query=workflow%3A%22Uptime+CI%22) +[![Response Time CI](https://github.com/ivuorinen/uptime/workflows/Response%20Time%20CI/badge.svg)](https://github.com/ivuorinen/uptime/actions?query=workflow%3A%22Response+Time+CI%22) +[![Graphs CI](https://github.com/ivuorinen/uptime/workflows/Graphs%20CI/badge.svg)](https://github.com/ivuorinen/uptime/actions?query=workflow%3A%22Graphs+CI%22) +[![Static Site CI](https://github.com/ivuorinen/uptime/workflows/Static%20Site%20CI/badge.svg)](https://github.com/ivuorinen/uptime/actions?query=workflow%3A%22Static+Site+CI%22) +[![Summary CI](https://github.com/ivuorinen/uptime/workflows/Summary%20CI/badge.svg)](https://github.com/ivuorinen/uptime/actions?query=workflow%3A%22Summary+CI%22) -> 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. - - - -[![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) -[![Graphs CI](https://github.com/upptime/upptime/workflows/Graphs%20CI/badge.svg)](https://github.com/upptime/upptime/actions?query=workflow%3A%22Graphs+CI%22) -[![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/ivuorinen/uptime/issues) as incident reports, [Actions](https://github.com/ivuorinen/uptime/actions) as uptime monitors, and [Pages](https://ivuorinen.net) for the status page. @@ -24,84 +16,19 @@ 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 136ms
Response time 111
24-hour response time 208
7-day response time 136
30-day response time 122
1-year response time 105
|
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.99%
-| [Wikipedia](https://en.wikipedia.org) | 🟩 Up | [wikipedia.yml](https://github.com/upptime/upptime/commits/HEAD/history/wikipedia.yml) |
Response time graph 233ms
Response time 242
24-hour response time 172
7-day response time 233
30-day response time 230
1-year response time 243
|
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 383ms
Response time 400
24-hour response time 307
7-day response time 383
30-day response time 321
1-year response time 441
|
100.00%All-time uptime 98.72%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.95%
-| [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 1.38%
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 4
|
0.00%All-time uptime 0.01%
24-hour uptime 0.00%
7-day uptime 0.00%
30-day uptime 1.38%
1-year uptime 0.01%
+| [antiprocess.net](https://antiprocess.net) | 🟩 Up | [antiprocess-net.yml](https://github.com/ivuorinen/uptime/commits/HEAD/history/antiprocess-net.yml) |
Response time graph 963ms
Response time 963
24-hour response time 963
7-day response time 963
30-day response time 963
1-year response time 963
|
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%
+| [demons: paimon](http://paimon.antiprocess.net) | 🟥 Down | [demons-paimon.yml](https://github.com/ivuorinen/uptime/commits/HEAD/history/demons-paimon.yml) |
Response time graph 645ms
Response time 645
24-hour response time 645
7-day response time 645
30-day response time 645
1-year response time 645
|
20.03%All-time uptime 20.03%
24-hour uptime 20.03%
7-day uptime 20.03%
30-day uptime 20.03%
1-year uptime 20.03%
+| [Google](https://www.google.com) | 🟥 Down | [google.yml](https://github.com/ivuorinen/uptime/commits/HEAD/history/google.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%
+| [Wikipedia](https://en.wikipedia.org) | 🟥 Down | [wikipedia.yml](https://github.com/ivuorinen/uptime/commits/HEAD/history/wikipedia.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%
+| [Hacker News](https://news.ycombinator.com) | 🟥 Down | [hacker-news.yml](https://github.com/ivuorinen/uptime/commits/HEAD/history/hacker-news.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/ivuorinen/uptime/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://ivuorinen.net) ## 📄 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/)