tag:nossi.statuspage.io,2005:/historynossi Status - Incident History2020-11-05T22:06:02+03:00nossitag:nossi.statuspage.io,2005:Incident/54970332020-11-04T20:25:03+03:002020-11-05T20:42:53+03:00This is an example incident<p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>20:25</var> GMT+03:00</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>20:15</var> GMT+03:00</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>20:21</var> GMT+03:00</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Nov <var data-var='date'> 4</var>, <var data-var='time'>20:51</var> GMT+03:00</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>