generated from meaz/Test_theme
70 lines
5.1 KiB
XML
70 lines
5.1 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||
<channel>
|
||
<link rel="alternate" type="text/html" href="https://example.com"/>
|
||
<title>Media Proxy on DISROOT</title>
|
||
<link>https://example.com/affected/media-proxy/</link>
|
||
<description>Incident history</description>
|
||
<generator>github.com/cstate</generator>
|
||
<language>en</language>
|
||
|
||
<lastBuildDate>2018-04-25T04:13:00+00:00</lastBuildDate>
|
||
<updated>2018-04-25T04:13:00+00:00</updated>
|
||
|
||
|
||
|
||
<atom:link href="https://example.com/affected/media-proxy/index.xml" rel="self" type="application/rss+xml" />
|
||
|
||
|
||
<item>
|
||
<title>[Resolved] US East Connection Issues</title>
|
||
<link>https://example.com/issues/2018-05-25-us-east-conn-issues/</link>
|
||
<pubDate>Wed, 25 Apr 2018 04:13:00 +0000</pubDate>
|
||
<guid>https://example.com/issues/2018-05-25-us-east-conn-issues/</guid>
|
||
<category>2018-04-25 04:13:59</category>
|
||
<description>Resolved - We believe all users experiencing issues have been able to connect at this time. (05:54 UTC — May 25) Monitoring - We believe the connectivity issues are being caused by an isolated ISP issue. We&rsquo;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. (04:40 UTC — May 25) Investigating - We&rsquo;re aware of reports that users are experiencing connection issues on the East coast of the United States.</description>
|
||
<content type="html"><p><em>Resolved</em> -
|
||
We believe all users experiencing issues have been able to connect at this time.
|
||
<span class="faded">(05:54 UTC — May 25)</span>
|
||
|
||
</p>
|
||
<p><em>Monitoring</em> - We believe the connectivity issues are being caused by an isolated ISP issue. We&rsquo;ve had reports that swapping to Google DNS servers (see here; <a href="https://developers.google.com/speed/public-dns/docs/using">https://developers.google.com/speed/public-dns/docs/using</a>) resolves the problem for users.
|
||
<span class="faded">(04:40 UTC — May 25)</span>
|
||
|
||
</p>
|
||
<p><em>Investigating</em> - We&rsquo;re aware of reports that users are experiencing connection issues on the East coast of the United States. We&rsquo;re currently investigating these issues, and apologize for any inconvenience it may be causing you.
|
||
<span class="faded">(04:13 UTC — May 25)</span>
|
||
|
||
</p>
|
||
</content>
|
||
</item>
|
||
|
||
<item>
|
||
<title>[Resolved] Unavailable Guilds & Connection Issues</title>
|
||
<link>https://example.com/issues/2018-04-13-unavailable-guilds-connection-issues/</link>
|
||
<pubDate>Fri, 13 Apr 2018 15:54:00 +0000</pubDate>
|
||
<guid>https://example.com/issues/2018-04-13-unavailable-guilds-connection-issues/</guid>
|
||
<category>2018-04-13 17:30:00</category>
|
||
<description>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.</description>
|
||
<content type="html"><p><em>Post-mortem</em></p>
|
||
<p>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.</p>
|
||
<hr>
|
||
<p><em>Update</em> - A fix has been implemented and we are monitoring the results. Looks like this has been fixed.
|
||
<span class="faded">(17:30 UTC — Apr 13)</span>
|
||
|
||
</p>
|
||
<p><em>Monitoring</em> - After hitting the ole reboot button Example Chat App is now recovering. We&rsquo;re going to continue to monitor as everyone reconnects.
|
||
<span class="faded">(16:50 UTC — Apr 13)</span>
|
||
|
||
</p>
|
||
<p><em>Investigating</em> - We&rsquo;re aware of users experiencing unavailable guilds and issues when attempting to connect. We&rsquo;re currently investigating.
|
||
<span class="faded">(15:54 UTC — Apr 13)</span>
|
||
|
||
</p>
|
||
</content>
|
||
</item>
|
||
|
||
</channel>
|
||
</rss>
|