tag:fullriverred2023jaerjamban.statuspage.io,2005:/historyfullriverred2023jaerjamban Status - Incident History2023-01-27T17:24:40Zfullriverred2023jaerjambantag:fullriverred2023jaerjamban.statuspage.io,2005:Incident/159533042023-01-26T16:49:36Z2023-01-27T16:33:37ZThis is an example incident<p><small>Jan <var data-var='date'>26</var>, <var data-var='time'>16:49</var> UTC</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'>16:39</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>Jan <var data-var='date'>26</var>, <var data-var='time'>16:45</var> UTC</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'>17:15</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>