From dccc5e9864bb8e5923d633848860d39e4d92e46c Mon Sep 17 00:00:00 2001
From: Mantas <11616378+mistermantas@users.noreply.github.com>
Date: Thu, 5 Jul 2018 14:45:24 +0300
Subject: v2 Dev Preview 1

---
 .../issues/unavailable-guilds-connection-issues.md | 24 ++++++++++++++++++++++
 exampleSite/content/issues/us-east-conn-issues.md  | 18 ++++++++++++++++
 2 files changed, 42 insertions(+)
 create mode 100644 exampleSite/content/issues/unavailable-guilds-connection-issues.md
 create mode 100644 exampleSite/content/issues/us-east-conn-issues.md

(limited to 'exampleSite/content/issues')

diff --git a/exampleSite/content/issues/unavailable-guilds-connection-issues.md b/exampleSite/content/issues/unavailable-guilds-connection-issues.md
new file mode 100644
index 0000000..eba61b2
--- /dev/null
+++ b/exampleSite/content/issues/unavailable-guilds-connection-issues.md
@@ -0,0 +1,24 @@
+---
+Title: Unavailable Guilds & Connection Issues
+Date: 2018-04-13 15:54:00
+Resolved: true
+ResolvedWhen: 2018-04-13 17:30:00
+# down, disrupted, notice
+Severity: down
+Affected:
+  - API
+Section: issue
+---
+
+*Post-mortem*
+
+At approximately 14:01, a Redis instance acting as the primary for a highly-available cluster used by our API services was migrated automatically by Google’s Cloud Platform. This migration caused the node to incorrectly drop offline, forcing the cluster to rebalance and trigger known issues with the way our API instances handle Redis failover. After resolving this partial outage, unnoticed issues on other services caused a cascading failure through Example Chat App’s real time system. These issues caused enough critical impact that Example Chat App’s engineering team was forced to fully restart the service, reconnecting millions of clients over a period of 20 minutes.
+
+
+---
+
+*Update* - A fix has been implemented and we are monitoring the results. Looks like this has been fixed. {{< track "2018-04-13 17:30:00" >}}
+
+*Monitoring* - After hitting the ole reboot button Example Chat App is now recovering. We're going to continue to monitor as everyone reconnects. {{< track "2018-04-13 16:50:00" >}}
+
+*Investigating* - We're aware of users experiencing unavailable guilds and issues when attempting to connect. We're currently investigating. {{< track "2018-04-13 15:54:00" >}}
diff --git a/exampleSite/content/issues/us-east-conn-issues.md b/exampleSite/content/issues/us-east-conn-issues.md
new file mode 100644
index 0000000..5431bef
--- /dev/null
+++ b/exampleSite/content/issues/us-east-conn-issues.md
@@ -0,0 +1,18 @@
+---
+Title: US East Connection Issues
+Date: 2018-05-25 04:13:00
+Resolved: true
+ResolvedWhen: 2018-05-25 04:40:00
+# down, disrupted, notice
+Severity: disrupted
+Affected:
+  - API
+Section: issue
+---
+
+*Resolved* -
+We believe all users experiencing issues have been able to connect at this time. {{< track "2018-05-25 05:54:00" >}}
+
+*Monitoring* - We believe the connectivity issues are being caused by an isolated ISP issue. We've had reports that swapping to Google DNS servers (see here; https://developers.google.com/speed/public-dns/docs/using) resolves the problem for users. {{< track "2018-05-25 04:40:00" >}}
+
+*Investigating* - We're aware of reports that users are experiencing connection issues on the East coast of the United States. We're currently investigating these issues, and apologize for any inconvenience it may be causing you. {{< track "2018-05-25 04:13:00" >}}
-- 
cgit v1.2.3-70-g09d2