<?xml version="1.0" encoding="UTF-8"?>
<feed xml:lang="en-US" xmlns="http://www.w3.org/2005/Atom">
  <id>tag:332.instatus.com,2005:/history</id>
  <link rel="alternate" type="text/html" href="https://332.instatus.com"/>
  <link rel="self" type="application/atom+xml" href="https://332.instatus.com/history.atom"/>
  <title>332 Status - Incident history</title>
  <updated>2026-04-02T23:42:14.415+00:00</updated>
  <author>
    <name>332</name>
  </author>
  
<entry>
  <id>tag:332.instatus.com,2005:Incident/cmni4dbb204yknerdhbejdmkb</id>
  <published>2026-04-02T23:42:14.415+00:00</published>
  <updated>2026-04-02T23:42:14.415+00:00</updated>
  <link rel="alternate" type="text/html" href="https://332.instatus.com/incident/cmni4dbb204yknerdhbejdmkb"/>
  <title>Issues with sign up</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 minutes</p>
    <p><strong>Affected Components:</strong> App — app.order332.com</p>
    <p><small>Apr <var data-var='date'> 2</var>, <var data-var='time'>23:42:14</var> GMT+0</small><br /><strong>Investigating</strong> -
  Passkey sign up is currently not working for some or all users. Users may see &quot;Failed to start passkey registration&quot; during registration..</p>
<p><small>Apr <var data-var='date'> 3</var>, <var data-var='time'>00:01:13</var> GMT+0</small><br /><strong>Resolved</strong> -
  A fix has been pushed to the app. All PWA app users should update their client to the latest version. All affected invite codes have been reset and should be usable again..</p>

        ]]>
  </content>
</entry>

<entry>
  <id>tag:332.instatus.com,2005:Incident/cm5b4dcu30076b1e8l3n4vkxe</id>
  <published>2024-12-30T14:13:11.024+00:00</published>
  <updated>2024-12-30T14:13:11.024+00:00</updated>
  <link rel="alternate" type="text/html" href="https://332.instatus.com/incident/cm5b4dcu30076b1e8l3n4vkxe"/>
  <title>Maintainence</title>

  <content type="html">
  <![CDATA[
    <p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 hours and 16 minutes</p>
    
    <p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>14:13:11</var> GMT+0</small><br /><strong>Identified</strong> -
  Ora infrastructure is currently undergoing maintenance. The service will be unavailable for a temporary amount of time..</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>14:37:10</var> GMT+0</small><br /><strong>Monitoring</strong> -
  We implemented a fix and are currently monitoring the result..</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>17:21:20</var> GMT+0</small><br /><strong>Investigating</strong> -
  We are investigating an issue which is affecting the re-deployment of the primary Ora app instance..</p>
<p><small>Dec <var data-var='date'> 30</var>, <var data-var='time'>17:29:04</var> GMT+0</small><br /><strong>Resolved</strong> -
  This incident has been resolved..</p>

        ]]>
  </content>
</entry>

</feed>