-
Notifications
You must be signed in to change notification settings - Fork 1
/
Copy pathhistory (3) (1).rss
25 lines (25 loc) · 3.69 KB
/
history (3) (1).rss
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>ruzismart enterprise Status - Incident History</title>
<link>https://ruzismartenterprise.statuspage.io</link>
<description>Statuspage</description>
<pubDate>Sat, 04 Jan 2020 08:04:51 +0000</pubDate>
<item>
<title>Description</title>
<description>
<p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>12:08</var> UTC</small><br><strong>Resolved</strong> - Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.</p><p><small>Sep <var data-var='date'> 8</var>, <var data-var='time'>12:04</var> UTC</small><br><strong>Update</strong> - Our data processing infrastructure is running behind which is causing inaccuracies in the reporting tools. No data has been lost and the system should be caught up shortly.</p><p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>19:01</var> UTC</small><br><strong>Update</strong> - We are continuing to investigate this issue.</p><p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>18:58</var> UTC</small><br><strong>Update</strong> - Update new incident</p><p><small>Sep <var data-var='date'> 5</var>, <var data-var='time'>18:57</var> UTC</small><br><strong>Investigating</strong> - Status and incident</p> </description>
<pubDate>Sun, 08 Sep 2019 12:08:54 +0000</pubDate>
<link>https://ruzismartenterprise.statuspage.io/incidents/q0sv7tkwf9wl</link>
<guid>https://ruzismartenterprise.statuspage.io/incidents/q0sv7tkwf9wl</guid>
</item>
<item>
<title>This is an example incident</title>
<description>
<p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>03:42</var> UTC</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>03:32</var> UTC</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>03:38</var> UTC</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Aug <var data-var='date'>14</var>, <var data-var='time'>04:08</var> UTC</small><br><strong>Investigating</strong> - When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.</p> </description>
<pubDate>Wed, 14 Aug 2019 03:42:34 +0000</pubDate>
<link>https://ruzismartenterprise.statuspage.io/incidents/cj386ys3m7fq</link>
<guid>https://ruzismartenterprise.statuspage.io/incidents/cj386ys3m7fq</guid>
</item>
</channel>
</rss>