tag:status.kubric.io,2005:/historyKubric Status - Incident History2024-03-28T21:17:32+05:30Kubrictag:status.kubric.io,2005:Incident/43510192020-06-11T23:23:55+05:302020-06-13T12:12:10+05:30This is an example incident<p><small>Jun <var data-var='date'>11</var>, <var data-var='time'>23:23</var> IST</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Jun <var data-var='date'>11</var>, <var data-var='time'>23:13</var> IST</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Jun <var data-var='date'>11</var>, <var data-var='time'>23:19</var> IST</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Jun <var data-var='date'>11</var>, <var data-var='time'>23:49</var> IST</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>