Unverified Commit ed55a18a authored by anarcat's avatar anarcat 💥
Browse files

expand on the project, fix existing sites

parent 70fe917e

service/status.md

+31 −14
Original line number Diff line number Diff line
@@ -83,11 +83,26 @@ There is no issue tracker specifically for this project, [File][] or 


## Overview



<!-- describe the overall project. should include a link to a ticket -->

<!-- that has a launch checklist -->

This project comes from two places:



 1. during the [2020 TPA user survey](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40061), some respondents suggested

    to document "downtimes of 1h or longer" and better communicate

    about service statuses



 2. seperately, following a major outage in the Tor network due to a

    DDOS, the network team and network health teams [asked for a

    dashboard to inform tor users about such problems in the

    future](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40138)



This is therefore a project spanning multiple teams, with different

stakeholders. The general idea is to have a site (say

status.torproject.org) that simply shows users how things are going,

in an easy to understand form.



## Goals

<!-- include bugs to be fixed -->



In general, the goal is to provide a simple interface to provide users

with status updates.



### Must have
@@ -196,16 +211,18 @@ experience: 


### example sites



  * [État des services gandi](https://www.gandi.net/servstat)

  * [Amazon Service Health Dashboard](http://status.aws.amazon.com/)

  * [Disqus.com service status](http://status.disqus.com) - based on [statuspage.io](https://www.statuspage.io/)

  * [Github status](https://status.github.com/) - "Battle station fully operational",

    auto-refresh, twitter-connected, simple color coded (see [this

    blog post for more details](https://github.com/blog/1240-new-status-site)), not open-source (confirmed in

    personnal email between github support and anarcat on 2013-05-02)

  * [Wikimedia status page](http://status.wikimedia.org/) - based on [proprietary nimsoft

    software](http://www.nimsoft.com/solutions/nimsoft-cloud-user-experience/key-features/public-status-page.html?m=41159&c=pspfoot), deprecated in favor of Grafana

  * [Riseup](https://status.riseup.net/) - RSS feeds

  * [Disqus](http://status.disqus.com) - based on [statuspage.io](https://www.statuspage.io/)

  * [GitLab](https://status.gitlab.com) - based on [status.io](https://status.io/)

  * [Github](https://status.github.com/) - "Battle station fully operational", auto-refresh,

    twitter-connected, simple color coded (see [this blog post for

    more details](https://github.com/blog/1240-new-status-site)), not open-source (confirmed in personnal email

    between github support and anarcat on 2013-05-02)

  * [Potager.org](https://meteo.potager.org/) - ikiwiki based

  * [Twilio status](https://status.twilio.com/) - email, slack, RSS subscriptions, lots of

    services shown
 
  * [Riseup.net](https://status.riseup.net/) - RSS feeds

  * [Signal](https://status.signal.org/) - simple, plain HTML page

  * [sr.ht](https://status.sr.ht/) - cstate

  * [Twilio](https://status.twilio.com/) - email, slack, RSS subscriptions, lots of services

    shown

  * [Wikimedia](http://status.wikimedia.org/) - based on [proprietary nimsoft software](http://www.nimsoft.com/solutions/nimsoft-cloud-user-experience/key-features/public-status-page.html?m=41159&c=pspfoot),

    deprecated in favor of Grafana