Rownd Status - Incident history https://rownd.instatus.com Rownd Thu, 19 Feb 2026 23:58:52 +0000 Elevated API error rates Type: Incident Duration: 16 hours and 59 minutes Affected Components: API Feb 20, 00:13:20 GMT+0 - Investigating - Our services were having trouble connecting to our primary database for about 20 minutes. Services appear to be recovering. We are continuing to investigate the cause of this disruption. Feb 20, 00:15:00 GMT+0 - Monitoring - The service is operating normally and we are monitoring for further disruptions. Feb 20, 16:58:18 GMT+0 - Resolved - After extensive monitoring, the service appears to be stable. We have opened a ticket with our database provider, as it appears they had some internal issues during this outage. We'll add details to the a postmortem once we are confident in the root cause. Feb 19, 23:58:52 GMT+0 - Investigating - We are currently investigating reports of elevated error rates across the Rownd service. Type: Incident

Duration: 16 hours and 59 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>00:13:20</var> GMT+0</small><br><strong>Investigating</strong> - Our services were having trouble connecting to our primary database for about 20 minutes. Services appear to be recovering. We are continuing to investigate the cause of this disruption..</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>00:15:00</var> GMT+0</small><br><strong>Monitoring</strong> - The service is operating normally and we are monitoring for further disruptions..</p> <p><small>Feb <var data-var='date'> 20</var>, <var data-var='time'>16:58:18</var> GMT+0</small><br><strong>Resolved</strong> - After extensive monitoring, the service appears to be stable. We have opened a ticket with our database provider, as it appears they had some internal issues during this outage. We'll add details to the a postmortem once we are confident in the root cause..</p> <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>23:58:52</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating reports of elevated error rates across the Rownd service..</p> ]]> Thu, 19 Feb 2026 23:58:52 +0000 https://rownd.instatus.com/incident/cmlu4gxmm08f1ifr7uacfyg2y https://rownd.instatus.com/incident/cmlu4gxmm08f1ifr7uacfyg2y Rownd API intermittently failing Type: Incident Duration: 19 minutes Affected Components: API, Platform Feb 19, 01:09:32 GMT+0 - Investigating - We are currently investigating this incident. Feb 19, 01:28:34 GMT+0 - Resolved - This incident has been resolved. Feb 19, 15:49:49 GMT+0 - Postmortem - We take any amount of downtime very seriously, and we want to provide full transparency regarding our recent service interruption. We sincerely apologize for the inconvenience this caused to you and your users. * **Root Cause:** During a routine auto-rotation of our internal certificates, an unexpected race condition occurred. This caused the certificate trust chain to break between our internal service members, leading to the outage. * **Resolution:** Our engineering team quickly identified the issue, manually recycled the necessary certificates, and restarted the affected services. All systems have successfully recovered and are operating normally. * **Preventative Measures:** To ensure this does not happen again, we are implementing configuration changes to our infrastructure prior to our next scheduled certificate rotation. These updates will strictly enforce the proper rotation sequence and guarantee that certificates cannot fall out of sync. Type: Incident

Duration: 19 minutes

Affected Components: ,

<p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>01:09:32</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>01:28:34</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 19</var>, <var data-var='time'>15:49:49</var> GMT+0</small><br><strong>Postmortem</strong> - We take any amount of downtime very seriously, and we want to provide full transparency regarding our recent service interruption. We sincerely apologize for the inconvenience this caused to you and your users. * **Root Cause:** During a routine auto-rotation of our internal certificates, an unexpected race condition occurred. This caused the certificate trust chain to break between our internal service members, leading to the outage. * **Resolution:** Our engineering team quickly identified the issue, manually recycled the necessary certificates, and restarted the affected services. All systems have successfully recovered and are operating normally. * **Preventative Measures:** To ensure this does not happen again, we are implementing configuration changes to our infrastructure prior to our next scheduled certificate rotation. These updates will strictly enforce the proper rotation sequence and guarantee that certificates cannot fall out of sync..</p> ]]> Thu, 19 Feb 2026 01:09:32 +0000 https://rownd.instatus.com/incident/cmlsrjwjw0480lu8ar83oa35d https://rownd.instatus.com/incident/cmlsrjwjw0480lu8ar83oa35d Sign-in failures due to intermittent network timeouts Type: Incident Duration: 21 hours and 32 minutes Affected Components: API Jun 30, 20:13:59 GMT+0 - Investigating - We are seeing certain network requests timeout, which may result in a small number of sign-in failures. Our engineers are investigating this issue. Jul 1, 02:19:55 GMT+0 - Investigating - We are continuing to track these intermittent issues with sign-in completions and are working on a resolution. Jul 1, 02:57:58 GMT+0 - Monitoring - We have adjusted some settings related to database and compute performance and are monitoring the system for further anomalies. Jul 1, 17:46:06 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 21 hours and 32 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>20:13:59</var> GMT+0</small><br><strong>Investigating</strong> - We are seeing certain network requests timeout, which may result in a small number of sign-in failures. Our engineers are investigating this issue..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>02:19:55</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to track these intermittent issues with sign-in completions and are working on a resolution..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>02:57:58</var> GMT+0</small><br><strong>Monitoring</strong> - We have adjusted some settings related to database and compute performance and are monitoring the system for further anomalies..</p> <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>17:46:06</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 30 Jun 2025 20:13:59 +0000 https://rownd.instatus.com/incident/cmcjjeebf0056cfa6eqr78ubj https://rownd.instatus.com/incident/cmcjjeebf0056cfa6eqr78ubj API instability Type: Incident Duration: 3 hours and 25 minutes Affected Components: API Jun 12, 18:13:19 GMT+0 - Investigating - We are investigating issues with some Rownd APIs returning 500 errors or responding slowly. We will update this ticket as more information becomes available. Jun 12, 18:24:02 GMT+0 - Identified - One of our core vendors (Cloudflare) appears to be experiencing an outage affecting multiple services. Things seem to be working slowly or intermittently. We're continuing to dig into the root cause and will post additional updates soon. Jun 12, 18:42:02 GMT+0 - Identified - Cloudflare is now reporting outages across a broad swath of services, but has not yet identified a root cause. We are continuing to monitor the situation. You can find more information on https://cloudflarestatus.com Jun 12, 19:32:05 GMT+0 - Monitoring - Cloudflare has identified the issue and made repairs. There may continue to be some intermittent failures as services are restored, but we are seeing conditions return to normal. We will continue monitoring the situation until it is fully resolved. Jun 12, 20:37:51 GMT+0 - Monitoring - The issue affecting Rownd API services was caused by this Google Cloud outage (<https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW>), which caused major disruption to the Cloudflare services, such as Workers KV (<https://www.cloudflarestatus.com/incidents/25r9t0vz99rp>). These services are recovering, and as such, Rownd services are also returning to normal. We expect to see these intermittent disruptions dissipate over the next half hour. Jun 12, 21:37:51 GMT+0 - Resolved - Our monitoring has shown that this incident has been resolved, as do the status pages for Cloudflare and Google Cloud. Thanks for your patience. Type: Incident

Duration: 3 hours and 25 minutes

Affected Components:

<p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:13:19</var> GMT+0</small><br><strong>Investigating</strong> - We are investigating issues with some Rownd APIs returning 500 errors or responding slowly. We will update this ticket as more information becomes available..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:24:02</var> GMT+0</small><br><strong>Identified</strong> - One of our core vendors (Cloudflare) appears to be experiencing an outage affecting multiple services. Things seem to be working slowly or intermittently. We're continuing to dig into the root cause and will post additional updates soon..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>18:42:02</var> GMT+0</small><br><strong>Identified</strong> - Cloudflare is now reporting outages across a broad swath of services, but has not yet identified a root cause. We are continuing to monitor the situation. You can find more information on https://cloudflarestatus.com.</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>19:32:05</var> GMT+0</small><br><strong>Monitoring</strong> - Cloudflare has identified the issue and made repairs. There may continue to be some intermittent failures as services are restored, but we are seeing conditions return to normal. We will continue monitoring the situation until it is fully resolved..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>20:37:51</var> GMT+0</small><br><strong>Monitoring</strong> - The issue affecting Rownd API services was caused by this Google Cloud outage (<https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW>), which caused major disruption to the Cloudflare services, such as Workers KV (<https://www.cloudflarestatus.com/incidents/25r9t0vz99rp>). These services are recovering, and as such, Rownd services are also returning to normal. We expect to see these intermittent disruptions dissipate over the next half hour..</p> <p><small>Jun <var data-var='date'> 12</var>, <var data-var='time'>21:37:51</var> GMT+0</small><br><strong>Resolved</strong> - Our monitoring has shown that this incident has been resolved, as do the status pages for Cloudflare and Google Cloud. Thanks for your patience..</p> ]]> Thu, 12 Jun 2025 18:13:19 +0000 https://rownd.instatus.com/incident/cmbtp5vli000av2dd4wd98wdg https://rownd.instatus.com/incident/cmbtp5vli000av2dd4wd98wdg Intermittent API failures Type: Incident Duration: 1 hour and 58 minutes Affected Components: API May 24, 21:37:00 GMT+0 - Investigating - The Rownd API is returning 503 errors approximately 25%-30% of the time. We are investigating this issue. May 24, 22:40:00 GMT+0 - Monitoring - Some of our load balancers failed to retrieve an updated certificate during our normal automated refresh cycle. We manually recycled the load balancing system and new certificates were retrieved successfully. We are monitoring this situation to ensure that the system is not encountering other certificate-related issues and we are implementing processes to provide better visibility and awareness when such an issue arises in the future. We are also working on improvements to our infrastructure that will prevent this type of problem from occurring in the future. May 24, 23:35:00 GMT+0 - Resolved - During our monitoring, we noticed a significant drop in traffic to some of our backend services. Upon further investigation, we discovered that the internal TLS trust chain had broken due to the renewal of our private intermediate CA. This caused leaf certificates that depended on the previous intermediate CA cert to lose their trusted status, and so traffic to various internal services was affected. The result is that users may have experienced issues signing in and some platform accounts may have seemed like they were missing data. Rest assured that no data was lost during this incident. Moving forward, we will implement improved monitoring and processes that ensure the expiration of an internal root or intermediate CA is a) known well in advance, and b) automatically triggers the necessary processes that will refresh leaf certificates such that they tie back to the updated cert chain. This should prevent further incidents like this one. We understand how important authentication is to every product, and we are committed to ensuring that our customers can depend on Rownd as a service with near 100% uptime. We apologize for this incident and we will do better. If you have any further questions or concerns, please don't hesitate to reach out. We're happy to answer any inquiry. Type: Incident

Duration: 1 hour and 58 minutes

Affected Components:

<p><small>May <var data-var='date'> 24</var>, <var data-var='time'>21:37:00</var> GMT+0</small><br><strong>Investigating</strong> - The Rownd API is returning 503 errors approximately 25%-30% of the time. We are investigating this issue..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>22:40:00</var> GMT+0</small><br><strong>Monitoring</strong> - Some of our load balancers failed to retrieve an updated certificate during our normal automated refresh cycle. We manually recycled the load balancing system and new certificates were retrieved successfully. We are monitoring this situation to ensure that the system is not encountering other certificate-related issues and we are implementing processes to provide better visibility and awareness when such an issue arises in the future. We are also working on improvements to our infrastructure that will prevent this type of problem from occurring in the future..</p> <p><small>May <var data-var='date'> 24</var>, <var data-var='time'>23:35:00</var> GMT+0</small><br><strong>Resolved</strong> - During our monitoring, we noticed a significant drop in traffic to some of our backend services. Upon further investigation, we discovered that the internal TLS trust chain had broken due to the renewal of our private intermediate CA. This caused leaf certificates that depended on the previous intermediate CA cert to lose their trusted status, and so traffic to various internal services was affected. The result is that users may have experienced issues signing in and some platform accounts may have seemed like they were missing data. Rest assured that no data was lost during this incident. Moving forward, we will implement improved monitoring and processes that ensure the expiration of an internal root or intermediate CA is a) known well in advance, and b) automatically triggers the necessary processes that will refresh leaf certificates such that they tie back to the updated cert chain. This should prevent further incidents like this one. We understand how important authentication is to every product, and we are committed to ensuring that our customers can depend on Rownd as a service with near 100% uptime. We apologize for this incident and we will do better. If you have any further questions or concerns, please don't hesitate to reach out. We're happy to answer any inquiry..</p> ]]> Sat, 24 May 2025 21:37:00 +0000 https://rownd.instatus.com/incident/cmb2tsmzs002f11rp2rf7qvfm https://rownd.instatus.com/incident/cmb2tsmzs002f11rp2rf7qvfm Android users may be unable to sign in with an Apple account Type: Incident Duration: 4 days, 18 hours and 4 minutes Affected Components: Embedded UI components Apr 18, 04:34:39 GMT+0 - Identified - We've identified an issue preventing Android users from signing into a mobile app with their Apple accounts. The root cause has been identified and a fix is in progress. Apr 22, 22:38:34 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 4 days, 18 hours and 4 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>04:34:39</var> GMT+0</small><br><strong>Identified</strong> - We've identified an issue preventing Android users from signing into a mobile app with their Apple accounts. The root cause has been identified and a fix is in progress..</p> <p><small>Apr <var data-var='date'> 22</var>, <var data-var='time'>22:38:34</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 18 Apr 2025 04:34:39 +0000 https://rownd.instatus.com/incident/cm9map7nq0005119dn14sbv2m https://rownd.instatus.com/incident/cm9map7nq0005119dn14sbv2m Users are unable to sign in Type: Incident Duration: 20 hours and 2 minutes Affected Components: API May 23, 09:00:00 GMT+0 - Investigating - We are currently investigating this incident. May 23, 13:11:25 GMT+0 - Investigating - We're continuing to investigate this issue. We've isolated the problem to our primary database provider and we are working with them to identify the root cause. May 23, 15:40:42 GMT+0 - Monitoring - We identified that our main API services were experiencing issues querying the primary datastore. We've taken steps to distribute these queries across other infrastructure and services appear to be recovering. May 23, 19:11:43 GMT+0 - Monitoring - We continue to see vastly improved response times from services across our infrastructure. We believe access has been restored for all customers and services are operating normally. We'll keep monitoring the situation for any residual effects and will post a more formal root-cause analysis in the coming days. May 23, 19:30:00 GMT+0 - Resolved - We're marking this incident as closed as services continue to operate normally. Please contact support if you experience any lingering issues. A full RCA will be published in the coming days. Type: Incident

Duration: 20 hours and 2 minutes

Affected Components:

<p><small>May <var data-var='date'> 23</var>, <var data-var='time'>09:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>13:11:25</var> GMT+0</small><br><strong>Investigating</strong> - We're continuing to investigate this issue. We've isolated the problem to our primary database provider and we are working with them to identify the root cause..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>15:40:42</var> GMT+0</small><br><strong>Monitoring</strong> - We identified that our main API services were experiencing issues querying the primary datastore. We've taken steps to distribute these queries across other infrastructure and services appear to be recovering..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>19:11:43</var> GMT+0</small><br><strong>Monitoring</strong> - We continue to see vastly improved response times from services across our infrastructure. We believe access has been restored for all customers and services are operating normally. We'll keep monitoring the situation for any residual effects and will post a more formal root-cause analysis in the coming days..</p> <p><small>May <var data-var='date'> 23</var>, <var data-var='time'>19:30:00</var> GMT+0</small><br><strong>Resolved</strong> - We're marking this incident as closed as services continue to operate normally. Please contact support if you experience any lingering issues. A full RCA will be published in the coming days..</p> ]]> Thu, 23 May 2024 09:00:00 +0000 https://rownd.instatus.com/incident/clwj7lh9r7363bfn3o9jv13ql https://rownd.instatus.com/incident/clwj7lh9r7363bfn3o9jv13ql Intermittent sign-in issues Type: Incident Duration: 2 hours and 7 minutes Affected Components: API Jan 9, 07:47:00 GMT+0 - Resolved - Our database partner has resolved this issue. Jan 9, 05:40:00 GMT+0 - Investigating - Customers may experience issues signing in due to an issue with one of our database partners. See this incident for more information: https://status.fauna.com/incidents/qc7zmz5qp5f8 Type: Incident

Duration: 2 hours and 7 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>07:47:00</var> GMT+0</small><br><strong>Resolved</strong> - Our database partner has resolved this issue..</p> <p><small>Jan <var data-var='date'> 9</var>, <var data-var='time'>05:40:00</var> GMT+0</small><br><strong>Investigating</strong> - Customers may experience issues signing in due to an issue with one of our database partners. See this incident for more information: https://status.fauna.com/incidents/qc7zmz5qp5f8.</p> ]]> Tue, 9 Jan 2024 05:40:00 +0000 https://rownd.instatus.com/incident/clr5xuxck22086bjoctne5bfy9 https://rownd.instatus.com/incident/clr5xuxck22086bjoctne5bfy9 Sign-in unavailable for mobile clients Type: Incident Duration: 25 minutes Affected Components: Embedded UI components Oct 30, 20:09:44 GMT+0 - Identified - Due to an issue with Cloudflare, one of our upstream cloud providers, mobile users are currently unable to sign-in. We are monitoring this incident and will provide updates as they become available. We apologize for the inconvenience Oct 30, 20:32:31 GMT+0 - Monitoring - Cloudflare appears to have mitigated the issue on their end. Mobile users should now be able to sign in. We are continuing to monitor the situation and will provide additional updates if needed. Oct 30, 20:35:00 GMT+0 - Resolved - Cloudflare has completely corrected the underlying issue, so this incident has been resolved. Type: Incident

Duration: 25 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:09:44</var> GMT+0</small><br><strong>Identified</strong> - Due to an issue with Cloudflare, one of our upstream cloud providers, mobile users are currently unable to sign-in. We are monitoring this incident and will provide updates as they become available. We apologize for the inconvenience.</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:32:31</var> GMT+0</small><br><strong>Monitoring</strong> - Cloudflare appears to have mitigated the issue on their end. Mobile users should now be able to sign in. We are continuing to monitor the situation and will provide additional updates if needed..</p> <p><small>Oct <var data-var='date'> 30</var>, <var data-var='time'>20:35:00</var> GMT+0</small><br><strong>Resolved</strong> - Cloudflare has completely corrected the underlying issue, so this incident has been resolved..</p> ]]> Mon, 30 Oct 2023 20:09:44 +0000 https://rownd.instatus.com/incident/clodc356v78244bwolmuyoax8y https://rownd.instatus.com/incident/clodc356v78244bwolmuyoax8y Token API delays Type: Incident Duration: 7 days and 12 hours Affected Components: API May 18, 10:10:00 GMT+0 - Investigating - Authenticated users are experiencing delays when opening apps, visiting websites, etc. In some cases, they are being signed out, though they are able to sign in successfully after the fact. We are currently investigating this incident. May 18, 12:15:00 GMT+0 - Identified - We've identified the root issue that is delaying or preventing token refreshes from client SDKs on the web and mobile devices. We are working on a fix for this incident. May 18, 13:10:00 GMT+0 - Resolved - This incident has been resolved. Beginning at approximately 10:10 UTC, the Rownd token API began experiencing increased latency. Authenticated users may have felt impacts due to timeouts when attempting to refresh an access token that had expired. The root cause was identified and tracked to a non-critical, downstream, third-party component failure. A fix was implemented to bypass the downstream component in the event of failure, which would resolve the issue and prevent it from recurring. The fix was deployed at approximately 13:00 UTC and token refresh response times began to improve immediately. We are monitoring the situation throughout the day to ensure that the API continues to operate as expected. Type: Incident

Duration: 7 days and 12 hours

Affected Components:

<p><small>May <var data-var='date'> 18</var>, <var data-var='time'>10:10:00</var> GMT+0</small><br><strong>Investigating</strong> - Authenticated users are experiencing delays when opening apps, visiting websites, etc. In some cases, they are being signed out, though they are able to sign in successfully after the fact. We are currently investigating this incident..</p> <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>12:15:00</var> GMT+0</small><br><strong>Identified</strong> - We've identified the root issue that is delaying or preventing token refreshes from client SDKs on the web and mobile devices. We are working on a fix for this incident..</p> <p><small>May <var data-var='date'> 18</var>, <var data-var='time'>13:10:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Beginning at approximately 10:10 UTC, the Rownd token API began experiencing increased latency. Authenticated users may have felt impacts due to timeouts when attempting to refresh an access token that had expired. The root cause was identified and tracked to a non-critical, downstream, third-party component failure. A fix was implemented to bypass the downstream component in the event of failure, which would resolve the issue and prevent it from recurring. The fix was deployed at approximately 13:00 UTC and token refresh response times began to improve immediately. We are monitoring the situation throughout the day to ensure that the API continues to operate as expected..</p> ]]> Thu, 18 May 2023 10:10:00 +0000 https://rownd.instatus.com/incident/clhtanklo4138564om31a5f4uk https://rownd.instatus.com/incident/clhtanklo4138564om31a5f4uk