tag:bidverse.statuspage.io,2005:/historyBidverse Status - Incident History2023-09-02T21:39:59ZBidversetag:bidverse.statuspage.io,2005:Incident/64212912021-02-27T20:17:33Z2021-02-28T20:01:34ZThis is an example incident<p><small>Feb <var data-var='date'>27</var>, <var data-var='time'>20:17</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'>27</var>, <var data-var='time'>20:07</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'>27</var>, <var data-var='time'>20:13</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'>27</var>, <var data-var='time'>20:43</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>