[tor-commits] [status-site/main] use the date field to indicate start of issue

[gk@xxxxxxxxxxxxxx]

commit 1ac76efc0549b63317b145603b072b978a2df306
Author: Antoine Beaupré <anarcat@xxxxxxxxxx>
Date:   Thu Jan 28 12:10:33 2021 -0500

    use the date field to indicate start of issue
    
    That's what that date field is for! :) when the incident closes, you
    can use the `resolvedWhen` field and cState does all sorts of nice
    stuff with this (like count how long the service was down).
---
 content/issues/2021-01-28-dir-auth.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/content/issues/2021-01-28-dir-auth.md b/content/issues/2021-01-28-dir-auth.md
index d326c09..64494cd 100644
--- a/content/issues/2021-01-28-dir-auth.md
+++ b/content/issues/2021-01-28-dir-auth.md
@@ -1,6 +1,6 @@
 ---
 title: Disruption of v3 onion services and consensus building
-date: 2021-01-28 13:23:00
+date: 2021-01-27 23:00:00
 resolved: false
 # Possible severity levels: down, disrupted, notice
 severity: disrupted
@@ -11,5 +11,3 @@ section: issue
 ---
 
 We're currently facing [stability issues](https://lists.torproject.org/pipermail/network-health/2021-January/000661.html) with respect to our v3 onion services and consensus building. We are actively working on resolving those issues as soon as possible.
-
-Start time of this incident was around 2300 UTC on 01/27/2021.

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits