From 61307b9059d8484fa30a38e575a2f899f308311f Mon Sep 17 00:00:00 2001 From: Upptime Bot <73812536+upptime-bot@users.noreply.github.com> Date: Sat, 12 Nov 2022 02:31:25 +0000 Subject: [PATCH] :pencil: Update summary in README [skip ci] [upptime] --- README.md | 133 ++++++++++++++---------------------------------------- 1 file changed, 33 insertions(+), 100 deletions(-) diff --git a/README.md b/README.md index 2ea74f54fb..0fedc8d9ae 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://status.piped.video): **🟧 Partial outage** - +This repository contains the open-source uptime monitor and status page for [Team Piped](https://piped.kavin.rocks/), 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 your friends at [Koj](https://koj.co). +[![Uptime CI](https://github.com/TeamPiped/piped-uptime/workflows/Uptime%20CI/badge.svg)](https://github.com/TeamPiped/piped-uptime/actions?query=workflow%3A%22Uptime+CI%22) +[![Response Time CI](https://github.com/TeamPiped/piped-uptime/workflows/Response%20Time%20CI/badge.svg)](https://github.com/TeamPiped/piped-uptime/actions?query=workflow%3A%22Response+Time+CI%22) +[![Graphs CI](https://github.com/TeamPiped/piped-uptime/workflows/Graphs%20CI/badge.svg)](https://github.com/TeamPiped/piped-uptime/actions?query=workflow%3A%22Graphs+CI%22) +[![Static Site CI](https://github.com/TeamPiped/piped-uptime/workflows/Static%20Site%20CI/badge.svg)](https://github.com/TeamPiped/piped-uptime/actions?query=workflow%3A%22Static+Site+CI%22) +[![Summary CI](https://github.com/TeamPiped/piped-uptime/workflows/Summary%20CI/badge.svg)](https://github.com/TeamPiped/piped-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/TeamPiped/piped-uptime/issues) as incident reports, [Actions](https://github.com/TeamPiped/piped-uptime/actions) as uptime monitors, and [Pages](https://status.piped.video) for the status page. @@ -24,94 +16,35 @@ 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 100ms
Response time 103
24-hour response time 123
7-day response time 100
30-day response time 103
1-year response time 96
|
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/upptime/upptime/commits/HEAD/history/wikipedia.yml) |
Response time graph 247ms
Response time 224
24-hour response time 235
7-day response time 247
30-day response time 220
1-year response time 213
|
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%
-| [Hacker News](https://news.ycombinator.com) | 🟩 Up | [hacker-news.yml](https://github.com/upptime/upptime/commits/HEAD/history/hacker-news.yml) |
Response time graph 351ms
Response time 358
24-hour response time 422
7-day response time 351
30-day response time 304
1-year response time 352
|
100.00%All-time uptime 99.93%
24-hour uptime 100.00%
7-day uptime 100.00%
30-day uptime 100.00%
1-year uptime 99.90%
-| [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 0.00%
1-year uptime 0.00%
+| [kavin.rocks (Official)](https://pipedapi.kavin.rocks/healthcheck) | 🟩 Up | [kavin-rocks-official.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/kavin-rocks-official.yml) |
Response time graph 320ms
Response time 320
24-hour response time 320
7-day response time 320
30-day response time 320
1-year response time 320
|
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%
+| [tokhmi.xyz](https://pipedapi.tokhmi.xyz/healthcheck) | 🟥 Down | [tokhmi-xyz.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/tokhmi-xyz.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
|
22.89%All-time uptime 22.89%
24-hour uptime 22.89%
7-day uptime 22.89%
30-day uptime 22.89%
1-year uptime 22.89%
+| [moomoo.me](https://pipedapi.moomoo.me/healthcheck) | 🟥 Down | [moomoo-me.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/moomoo-me.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
|
29.72%All-time uptime 29.72%
24-hour uptime 29.72%
7-day uptime 29.72%
30-day uptime 29.72%
1-year uptime 29.72%
+| [syncpundit.io](https://pipedapi.syncpundit.io/healthcheck) | 🟥 Down | [syncpundit-io.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/syncpundit-io.yml) |
Response time graph 95ms
Response time 95
24-hour response time 95
7-day response time 95
30-day response time 95
1-year response time 95
|
0.49%All-time uptime 0.49%
24-hour uptime 0.49%
7-day uptime 0.49%
30-day uptime 0.49%
1-year uptime 0.49%
+| [mha.fi](https://api-piped.mha.fi/healthcheck) | 🟩 Up | [mha-fi.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/mha-fi.yml) |
Response time graph 646ms
Response time 646
24-hour response time 646
7-day response time 646
30-day response time 646
1-year response time 646
|
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%
+| [whatever.social](https://watchapi.whatever.social/healthcheck) | 🟩 Up | [whatever-social.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/whatever-social.yml) |
Response time graph 421ms
Response time 421
24-hour response time 421
7-day response time 421
30-day response time 421
1-year response time 421
|
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%
+| [garudalinux.org](https://piped-api.garudalinux.org/healthcheck) | 🟩 Up | [garudalinux-org.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/garudalinux-org.yml) |
Response time graph 482ms
Response time 482
24-hour response time 482
7-day response time 482
30-day response time 482
1-year response time 482
|
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%
+| [rivo.lol](https://pipedapi.rivo.lol/healthcheck) | 🟥 Down | [rivo-lol.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/rivo-lol.yml) |
Response time graph 348ms
Response time 348
24-hour response time 348
7-day response time 348
30-day response time 348
1-year response time 348
|
0.11%All-time uptime 0.11%
24-hour uptime 0.11%
7-day uptime 0.11%
30-day uptime 0.11%
1-year uptime 0.11%
+| [aeong.one](https://pipedapi.aeong.one/healthcheck) | 🟥 Down | [aeong-one.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/aeong-one.yml) |
Response time graph 185ms
Response time 185
24-hour response time 185
7-day response time 185
30-day response time 185
1-year response time 185
|
0.41%All-time uptime 0.41%
24-hour uptime 0.41%
7-day uptime 0.41%
30-day uptime 0.41%
1-year uptime 0.41%
+| [kavin.rocks libre (Official)](https://pipedapi-libre.kavin.rocks/healthcheck) | 🟩 Up | [kavin-rocks-libre-official.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/kavin-rocks-libre-official.yml) |
Response time graph 716ms
Response time 716
24-hour response time 716
7-day response time 716
30-day response time 716
1-year response time 716
|
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%
+| [jae.fi](https://api.yt.jae.fi/healthcheck) | 🟩 Up | [jae-fi.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/jae-fi.yml) |
Response time graph 519ms
Response time 519
24-hour response time 519
7-day response time 519
30-day response time 519
1-year response time 519
|
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%
+| [mint.lgbt](https://pa.mint.lgbt/healthcheck) | 🟩 Up | [mint-lgbt.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/mint-lgbt.yml) |
Response time graph 547ms
Response time 547
24-hour response time 547
7-day response time 547
30-day response time 547
1-year response time 547
|
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%
+| [il.ax](https://pa.il.ax/healthcheck) | 🟩 Up | [il-ax.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/il-ax.yml) |
Response time graph 385ms
Response time 385
24-hour response time 385
7-day response time 385
30-day response time 385
1-year response time 385
|
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%
+| [privacy.com.de](https://piped-api.privacy.com.de/healthcheck) | 🟥 Down | [privacy-com-de.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/privacy-com-de.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
|
44.29%All-time uptime 44.29%
24-hour uptime 44.29%
7-day uptime 44.29%
30-day uptime 44.29%
1-year uptime 44.29%
+| [esmailelbob.xyz](https://pipedapi.esmailelbob.xyz/healthcheck) | 🟩 Up | [esmailelbob-xyz.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/esmailelbob-xyz.yml) |
Response time graph 685ms
Response time 685
24-hour response time 685
7-day response time 685
30-day response time 685
1-year response time 685
|
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%
+| [projectsegfau.lt](https://api.piped.projectsegfau.lt/healthcheck) | 🟥 Down | [projectsegfau-lt.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/projectsegfau-lt.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
|
81.21%All-time uptime 81.21%
24-hour uptime 81.21%
7-day uptime 81.21%
30-day uptime 81.21%
1-year uptime 81.21%
+| [privacydev.net](https://api.piped.privacydev.net/healthcheck) | 🟩 Up | [privacydev-net.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/privacydev-net.yml) |
Response time graph 927ms
Response time 927
24-hour response time 927
7-day response time 927
30-day response time 927
1-year response time 927
|
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%
+| [palveluntarjoaja.eu](https://pipedapi.palveluntarjoaja.eu/healthcheck) | 🟩 Up | [palveluntarjoaja-eu.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/palveluntarjoaja-eu.yml) |
Response time graph 627ms
Response time 627
24-hour response time 627
7-day response time 627
30-day response time 627
1-year response time 627
|
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%
+| [plibre.com](https://p.plibre.com/healthcheck) | 🟥 Down | [plibre-com.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/plibre-com.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
|
7.88%All-time uptime 7.88%
24-hour uptime 7.88%
7-day uptime 7.88%
30-day uptime 7.88%
1-year uptime 7.88%
+| [smnz.de](https://pipedapi.smnz.de/healthcheck) | 🟩 Up | [smnz-de.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/smnz-de.yml) |
Response time graph 1337ms
Response time 1337
24-hour response time 1337
7-day response time 1337
30-day response time 1337
1-year response time 1337
|
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%
+| [adminforge.de](https://pipedapi.adminforge.de/healthcheck) | 🟩 Up | [adminforge-de.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/adminforge-de.yml) |
Response time graph 895ms
Response time 895
24-hour response time 895
7-day response time 895
30-day response time 895
1-year response time 895
|
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%
+| [qdi.fi](https://pipedapi.qdi.fi/healthcheck) | 🟩 Up | [qdi-fi.yml](https://github.com/TeamPiped/piped-uptime/commits/HEAD/history/qdi-fi.yml) |
Response time graph 91ms
Response time 91
24-hour response time 91
7-day response time 91
30-day response time 91
1-year response time 91
|
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://status.piped.video) ## 📄 License -- Code: [MIT](./LICENSE) © [Koj](https://koj.co) +- Powered by: [Upptime](https://github.com/upptime/upptime) +- Code: [MIT](./LICENSE) © [Team Piped](https://piped.kavin.rocks/) - Data in the `./history` directory: [Open Database License](https://opendatacommons.org/licenses/odbl/1-0/) - - -

- - Koj - -

-

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

-