tag:podtext.statuspage.io,2005:/historypodtext Status - Incident History2022-02-08T15:24:57Zpodtexttag:podtext.statuspage.io,2005:Incident/92660272022-02-07T14:50:46Z2022-02-08T14:34:47ZThis is an example incident<p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>14:50</var> UTC</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>14:40</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>Feb <var data-var='date'> 7</var>, <var data-var='time'>14:46</var> UTC</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Feb <var data-var='date'> 7</var>, <var data-var='time'>15:16</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>