tag:craftcoders1.statuspage.io,2005:/historyCraft Coders Status - Incident History2022-02-07T10:25:31+00:00Craft Coderstag:craftcoders1.statuspage.io,2005:Incident/91749332022-01-26T10:05:32+00:002022-01-27T09:49:34+00:00This is an example incident<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>10:05</var> GMT</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>09:55</var> GMT</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>10:01</var> GMT</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>10:31</var> GMT</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>