-
Notifications
You must be signed in to change notification settings - Fork 1
/
history (5).atom (1).txt
27 lines (27 loc) · 3.79 KB
/
history (5).atom (1).txt
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
26
27
<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
<id>tag:ruzismartenterprise.statuspage.io,2005:/history</id>
<link rel="alternate" type="text/html" href="https://ruzismartenterprise.statuspage.io"/>
<link rel="self" type="application/atom+xml" href="https://ruzismartenterprise.statuspage.io/history.atom"/>
<title>ruzismart enterprise Status - Incident History</title>
<updated>2020-01-04T08:04:51Z</updated>
<author>
<name>ruzismart enterprise</name>
</author>
<entry>
<id>tag:ruzismartenterprise.statuspage.io,2005:Incident/2964322</id>
<published>2019-09-08T12:08:54Z</published>
<updated>2019-09-08T12:08:54Z</updated>
<link rel="alternate" type="text/html" href="https://ruzismartenterprise.statuspage.io/incidents/q0sv7tkwf9wl"/>
<title>Description</title>
<content type="html"><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></content>
</entry>
<entry>
<id>tag:ruzismartenterprise.statuspage.io,2005:Incident/2864876</id>
<published>2019-08-14T03:42:34Z</published>
<updated>2019-08-15T03:26:35Z</updated>
<link rel="alternate" type="text/html" href="https://ruzismartenterprise.statuspage.io/incidents/cj386ys3m7fq"/>
<title>This is an example incident</title>
<content type="html"><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></content>
</entry>
</feed>