tag:prism1.statuspage.io,2005:/historyPrism Status - Incident History2024-03-25T16:13:20ZPrismtag:prism1.statuspage.io,2005:Incident/93074622022-02-12T22:14:09Z2022-02-13T21:58:09ZThis is an example incident<p><small>Feb <var data-var='date'>12</var>, <var data-var='time'>22:14</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'>12</var>, <var data-var='time'>22:04</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'>12</var>, <var data-var='time'>22:10</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'>12</var>, <var data-var='time'>22:40</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>