<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Quantix Foundation Status - Incident history</title>
    <link>https://status.quantixfoundation.com</link>
    <description>Quantix Foundation</description>
    <pubDate>Thu, 30 Apr 2026 16:00:00 +0000</pubDate>
    
<item>
  <title>Authentication System Migration to NolarFlow</title>
  <description>
    Type: Maintenance
    Duration: 3 days, 13 hours and 28 minutes

    Affected Components: reForge Captcha, NexSub
    Apr 30, 16:00:00 GMT+0 - Identified - We will be performing scheduled maintenance to upgrade our authentication system across reForge Captcha, reForge Consent, and NexSub.

During this maintenance period, login, registration, profile management, and password reset functionality will remain available. However, you may notice ongoing changes as we roll out the new system. Some features may intermittently stop working or behave unexpectedly during the transition.

What’s changing:  
We are introducing **NolarFlow (**[**nolarflow.site**](http://nolarflow.site)**)** as our new centralized account manager. Going forward, all authentication will be handled through NolarFlow, allowing you to access all our tools—including those requiring an account—using a single unified account.

As part of this upgrade, we will also introduce **Single Sign-On (SSO)** support via NolarFlow. You will be able to connect and log in using providers such as Google, Discord, GitHub, and Twitch. This means multiple login options, all managed through one central system.

Once the migration is complete, all platforms will route authentication through NolarFlow.

We appreciate your patience while we roll out these improvements. Apr 27, 02:32:08 GMT+0 - Completed - Maintenance has completed successfully. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 3 days, 13 hours and 28 minutes</p>
    <p><strong>Affected Components:</strong> , </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 30&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;16:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing scheduled maintenance to upgrade our authentication system across reForge Captcha, reForge Consent, and NexSub.

During this maintenance period, login, registration, profile management, and password reset functionality will remain available. However, you may notice ongoing changes as we roll out the new system. Some features may intermittently stop working or behave unexpectedly during the transition.

What’s changing:  
We are introducing **NolarFlow (**[**nolarflow.site**](http://nolarflow.site)**)** as our new centralized account manager. Going forward, all authentication will be handled through NolarFlow, allowing you to access all our tools—including those requiring an account—using a single unified account.

As part of this upgrade, we will also introduce **Single Sign-On (SSO)** support via NolarFlow. You will be able to connect and log in using providers such as Google, Discord, GitHub, and Twitch. This means multiple login options, all managed through one central system.

Once the migration is complete, all platforms will route authentication through NolarFlow.

We appreciate your patience while we roll out these improvements..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 27&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;02:32:08&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  Maintenance has completed successfully..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Thu, 30 Apr 2026 16:00:00 +0000</pubDate>
  <link>https://status.quantixfoundation.com/maintenance/cmod9s92p02j6p3f43cu1gc32</link>
  <guid>https://status.quantixfoundation.com/maintenance/cmod9s92p02j6p3f43cu1gc32</guid>
</item>

<item>
  <title>Enhancing Security with AES‑256‑GCM Encryption</title>
  <description>
    Type: Maintenance
    Duration: 2 hours and 41 minutes

    Affected Components: reForge Captcha
    Apr 22, 13:00:00 GMT+0 - Identified - We will perform planned maintenance to update reForge Captcha and reForge Consent. During this window we are implementing AES‑256‑GCM encryption to protect sensitive data such as IP addresses, ensuring it remains encrypted at all times and is only decrypted for the account holder within the interface. Brief service interruptions may occur while the updates are applied. Apr 22, 13:50:00 GMT+0 - Identified - The maintenance is proceeding smoothly. We have successfully encrypted all site secret keys and are now moving on to encrypt API keys, 2FA secrets, and IP addresses. Thanks to the encrypt and decrypt helper functions we built, adding this protection is straightforward, and because reForge Consent is a fork of reForge Captcha we can reuse the same functions without any extra work. We’ve also prepared an encrypter page to migrate all existing data to the new encryption system with ease. Apr 22, 15:09:00 GMT+0 - Identified - We’re almost finished with the maintenance for reForge Captcha and will move on to reForge Consent shortly after.

In a few weeks, we will schedule one more major maintenance window focused on maximizing security across our platform. During this larger update, we will enhance protection for sensitive data and account security. We will also include NexSub in this maintenance, adding encryption for secrets, passkey support, and 2FA functionality.

Please note that passkeys and 2FA are already available for reForge Captcha and reForge Consent, so these changes will apply only to NexSub. Apr 22, 15:41:00 GMT+0 - Completed - The maintenance for reForge Captcha has been successfully completed.

We have decided to postpone the updates for reForge Consent to the upcoming major maintenance window. This allows us to first improve the system and resolve any existing bugs before making significant changes to the database structure. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 2 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:00:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will perform planned maintenance to update reForge Captcha and reForge Consent. During this window we are implementing AES‑256‑GCM encryption to protect sensitive data such as IP addresses, ensuring it remains encrypted at all times and is only decrypted for the account holder within the interface. Brief service interruptions may occur while the updates are applied..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:50:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  The maintenance is proceeding smoothly. We have successfully encrypted all site secret keys and are now moving on to encrypt API keys, 2FA secrets, and IP addresses. Thanks to the encrypt and decrypt helper functions we built, adding this protection is straightforward, and because reForge Consent is a fork of reForge Captcha we can reuse the same functions without any extra work. We’ve also prepared an encrypter page to migrate all existing data to the new encryption system with ease..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:09:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We’re almost finished with the maintenance for reForge Captcha and will move on to reForge Consent shortly after.

In a few weeks, we will schedule one more major maintenance window focused on maximizing security across our platform. During this larger update, we will enhance protection for sensitive data and account security. We will also include NexSub in this maintenance, adding encryption for secrets, passkey support, and 2FA functionality.

Please note that passkeys and 2FA are already available for reForge Captcha and reForge Consent, so these changes will apply only to NexSub..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 22&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;15:41:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The maintenance for reForge Captcha has been successfully completed.

We have decided to postpone the updates for reForge Consent to the upcoming major maintenance window. This allows us to first improve the system and resolve any existing bugs before making significant changes to the database structure..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Wed, 22 Apr 2026 13:50:00 +0000</pubDate>
  <link>https://status.quantixfoundation.com/maintenance/cmobhgtih0013ztaxcmgrmnxl</link>
  <guid>https://status.quantixfoundation.com/maintenance/cmobhgtih0013ztaxcmgrmnxl</guid>
</item>

<item>
  <title>reForge Captcha Infrastructure Migration</title>
  <description>
    Type: Maintenance
    Duration: 7 days and 20 hours

    Affected Components: reForge Captcha
    Apr 10, 10:38:00 GMT+0 - Identified - We will be performing scheduled maintenance to migrate and expand the reForge Captcha service infrastructure. During this window, reForge Captcha will be moved to Web Node 2 (EU) and Web Node 1 (US), bringing it in line with our standard multi-node deployment used by all other services. Additionally, DB 01 will be relocated to a centralized position, enabling all web nodes across EU and US regions to connect to a single unified database. We expect brief interruptions to the reForge Captcha service during this maintenance window. All other services remain unaffected. Apr 10, 11:23:00 GMT+0 - Identified - DB 01 has been successfully migrated and is now accessible to all web nodes across the EU and US regions. We are currently proceeding with the final phase of this maintenance window: migrating reForge Captcha to Web Node 2 (EU) and Web Node 1 (US) to complete the multi-node deployment. Brief interruptions to the reForge Captcha service may still occur during this phase. All other services are fully operational. Apr 10, 13:46:00 GMT+0 - Completed - The scheduled maintenance has been completed. reForge Captcha is now running on Web Node 1 (EU) and Web Node 1 (US). During this maintenance window, Web Node 2 (EU) was decommissioned due to technical issues, resulting in a single web node per region.

We have identified an increase in database latency for the US web node connecting to DB 01 (EU). Our team is currently investigating the deployment of a dedicated DB 01 instance in the US region, which would be kept in real-time sync with the EU database. This approach introduces minor replication latency between servers, however end users will experience no noticeable impact as the databases remain up to date at all times. We will provide further updates as this investigation progresses. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 7 days and 20 hours</p>
    <p><strong>Affected Components:</strong> </p>
    &lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;10:38:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  We will be performing scheduled maintenance to migrate and expand the reForge Captcha service infrastructure. During this window, reForge Captcha will be moved to Web Node 2 (EU) and Web Node 1 (US), bringing it in line with our standard multi-node deployment used by all other services. Additionally, DB 01 will be relocated to a centralized position, enabling all web nodes across EU and US regions to connect to a single unified database. We expect brief interruptions to the reForge Captcha service during this maintenance window. All other services remain unaffected..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;11:23:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Identified&lt;/strong&gt; -
  DB 01 has been successfully migrated and is now accessible to all web nodes across the EU and US regions. We are currently proceeding with the final phase of this maintenance window: migrating reForge Captcha to Web Node 2 (EU) and Web Node 1 (US) to complete the multi-node deployment. Brief interruptions to the reForge Captcha service may still occur during this phase. All other services are fully operational..&lt;/p&gt;
&lt;p&gt;&lt;small&gt;Apr &lt;var data-var=&#039;date&#039;&gt; 10&lt;/var&gt;, &lt;var data-var=&#039;time&#039;&gt;13:46:00&lt;/var&gt; GMT+0&lt;/small&gt;&lt;br&gt;&lt;strong&gt;Completed&lt;/strong&gt; -
  The scheduled maintenance has been completed. reForge Captcha is now running on Web Node 1 (EU) and Web Node 1 (US). During this maintenance window, Web Node 2 (EU) was decommissioned due to technical issues, resulting in a single web node per region.

We have identified an increase in database latency for the US web node connecting to DB 01 (EU). Our team is currently investigating the deployment of a dedicated DB 01 instance in the US region, which would be kept in real-time sync with the EU database. This approach introduces minor replication latency between servers, however end users will experience no noticeable impact as the databases remain up to date at all times. We will provide further updates as this investigation progresses..&lt;/p&gt;
]]>
  </content:encoded>
  <pubDate>Fri, 10 Apr 2026 10:38:00 +0000</pubDate>
  <link>https://status.quantixfoundation.com/maintenance/cmobgs5gz001wvadjp4xvi6z3</link>
  <guid>https://status.quantixfoundation.com/maintenance/cmobgs5gz001wvadjp4xvi6z3</guid>
</item>

  </channel>
  </rss>