Initial commit as status.adast.dk

6 files changed, 0 insertions, 93 deletions

diff --git a/content/issues/2018-01-17-sending-dms-impacted.md b/content/issues/2018-01-17-sending-dms-impacted.md
deleted file mode 100644
index b96139f..0000000
--- a/content/issues/2018-01-17-sending-dms-impacted.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Issues Sending DMs
-date: 2017-12-17 16:24:00
-resolved: true
-resolvedWhen: 2017-12-17 16:58:00
-# Possible severity levels: down, disrupted, notice
-severity: disrupted
-affected:
-  - API
-section: issue
----
-
-*Update* - This incident has been resolved.
-
-*Investigating* - We're aware of an issue affecting sending DMs and viewing online friends. We're online and working on a resolution.
diff --git a/content/issues/2018-04-13-unavailable-guilds-connection-issues.md b/content/issues/2018-04-13-unavailable-guilds-connection-issues.md
deleted file mode 100644
index 170bd1f..0000000
--- a/content/issues/2018-04-13-unavailable-guilds-connection-issues.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Unavailable Guilds & Connection Issues
-date: 2018-04-13 15:54:00
-resolved: true
-resolvedWhen: 2018-04-13 17:30:00
-# Possible severity levels: down, disrupted, notice
-severity: down
-affected:
-  - API
-  - Media Proxy
-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/content/issues/2018-05-25-us-east-conn-issues.md b/content/issues/2018-05-25-us-east-conn-issues.md
deleted file mode 100644
index 8d56cf2..0000000
--- a/content/issues/2018-05-25-us-east-conn-issues.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: US East Connection Issues
-date: 2018-04-25 04:13:00
-resolved: true
-resolvedWhen: 2018-04-25 04:13:59
-# Possible severity levels: down, disrupted, notice
-severity: down
-affected:
-  - API
-  - Media Proxy
-  - Gateway
-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" >}}
diff --git a/content/issues/2019-10-08-testing-new-pipeline.md b/content/issues/2019-10-08-testing-new-pipeline.md
deleted file mode 100644
index 4e9da4f..0000000
--- a/content/issues/2019-10-08-testing-new-pipeline.md
+++ /dev/null
@@ -1,14 +0,0 @@
----
-title: New Pipeline Rollout
-date: 2019-10-05 16:24:00 
-resolved: true
-resolvedWhen: 2019-10-05 16:58:00 
-# Possible severity levels: down, disrupted, notice
-severity: disrupted
-affected:
-  - API
-section: issue
----
-
-There may be disruptions in the rollout.
- 
\ No newline at end of file
diff --git a/content/issues/2024-02-24-maintenance-window.md b/content/issues/2024-02-24-maintenance-window.md
deleted file mode 100644
index e5a5b14..0000000
--- a/content/issues/2024-02-24-maintenance-window.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Maintenance Announcement 
-date: 2024-02-24 10:35:00 
-informational: true
-pin: true 
-section: issue
----
-
-We will shut down our network at midnight UTC on Feb 24. This does not affect the current status.
diff --git a/content/issues/i-testing-cstate-functions.md b/content/issues/i-testing-cstate-functions.md
deleted file mode 100644
index cf833ac..0000000
--- a/content/issues/i-testing-cstate-functions.md
+++ /dev/null
@@ -1,10 +0,0 @@
----
-title: Testing New cState Features
-date: 2019-10-04 18:05:00
-informational: true
-section: issue
----
-
-There is a new feature in cState version 4 that lets you make what are called _informational_ posts. The main difference is that there will be no _Unresolved_ or _Resolved in under a minute_ text on the pages.
-
-This is essentially a page with a date and title that shows up in the incident history.
\ No newline at end of file