tag:ignitenz.statuspage.io,2005:/historyIgnite NZ Status - Incident History2024-03-19T13:14:04+13:00Ignite NZtag:ignitenz.statuspage.io,2005:Incident/108579122022-08-18T16:17:27+12:002022-08-19T16:01:28+12:00This is an example incident<p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>16:17</var> NZST</small><br><strong>Resolved</strong> - Empathize with those affected and let them know everything is operating as normal.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>16:07</var> NZST</small><br><strong>Monitoring</strong> - Let your users know once a fix is in place, and keep communication clear and precise.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>16:13</var> NZST</small><br><strong>Identified</strong> - As you continue to work through the incident, update your customers frequently.</p><p><small>Aug <var data-var='date'>18</var>, <var data-var='time'>16:43</var> NZST</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>