tag:leadengines.statuspage.io,2005:/historyLeadEngines Status - Incident History2022-01-18T20:05:50ZLeadEnginestag:leadengines.statuspage.io,2005:Incident/79109312021-09-02T15:01:16Z2021-09-03T14:45:16ZThis is an example incident<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>15:01</var> UTC</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>14:51</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>Sep <var data-var='date'> 2</var>, <var data-var='time'>14:57</var> UTC</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>15:27</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>