Fluxer Status - Incident history https://fluxerstatus.com Fluxer Thu, 30 Apr 2026 02:12:54 +0000 Issues with connecting to the gateway Type: Incident Duration: 10 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Apr 30, 02:12:54 GMT+0 - Investigating - We are currently investigating this incident. Apr 30, 02:23:19 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>02:12:54</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 30</var>, <var data-var='time'>02:23:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 30 Apr 2026 02:12:54 +0000 https://fluxerstatus.com/incident/cmokun2zm03kol849qcv3926o https://fluxerstatus.com/incident/cmokun2zm03kol849qcv3926o Issues with sending messages Type: Incident Duration: 4 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 29, 19:07:15 GMT+0 - Investigating - We are currently investigating this incident. Apr 29, 19:11:12 GMT+0 - Resolved - This incident has been resolved. Apr 29, 19:21:31 GMT+0 - Postmortem - At 19:01:58 UTC, our Valkey instance was OOM-killed by the kernel. The pod's memory limit was set to 512 MiB — a low default carried over from initial setup — and Valkey itself had no eviction ceiling configured, so under normal application growth its working set crept past the pod's limit before the configured LRU eviction policy ever had a chance to engage. Valkey came back \~1 second later, but because it's an in-memory store, all ephemeral state (including the snowflake node-ID leases held by every API pod) was wiped on restart. Starting around 19:04:30 UTC — roughly the renewal interval after the restart — every API pod tried to renew its lease, found it gone, and treated the loss as terminal instead of recoverable. From that point until mitigation, 100% of message sends and webhook deliveries returned 500 across the fleet. We mitigated at \~19:09 UTC by rolling both API deployments, which let pods acquire fresh leases on startup. Total user-visible impact: \~5 minutes of fleet-wide message-send failures. Type: Incident

Duration: 4 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>19:07:15</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>19:11:12</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 29</var>, <var data-var='time'>19:21:31</var> GMT+0</small><br><strong>Postmortem</strong> - At 19:01:58 UTC, our Valkey instance was OOM-killed by the kernel. The pod's memory limit was set to 512 MiB — a low default carried over from initial setup — and Valkey itself had no eviction ceiling configured, so under normal application growth its working set crept past the pod's limit before the configured LRU eviction policy ever had a chance to engage. Valkey came back \~1 second later, but because it's an in-memory store, all ephemeral state (including the snowflake node-ID leases held by every API pod) was wiped on restart. Starting around 19:04:30 UTC — roughly the renewal interval after the restart — every API pod tried to renew its lease, found it gone, and treated the loss as terminal instead of recoverable. From that point until mitigation, 100% of message sends and webhook deliveries returned 500 across the fleet. We mitigated at \~19:09 UTC by rolling both API deployments, which let pods acquire fresh leases on startup. Total user-visible impact: \~5 minutes of fleet-wide message-send failures..</p> ]]> Wed, 29 Apr 2026 19:07:15 +0000 https://fluxerstatus.com/incident/cmokffoyf02d5z8ri6k1rcvtx https://fluxerstatus.com/incident/cmokffoyf02d5z8ri6k1rcvtx Issues with embedding URLs in chat Type: Incident Duration: 44 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 24, 22:29:28 GMT+0 - Investigating - We are currently investigating this incident. Apr 24, 23:13:32 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 44 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>22:29:28</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 24</var>, <var data-var='time'>23:13:32</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 24 Apr 2026 22:29:28 +0000 https://fluxerstatus.com/incident/cmodhghe003vux6jep6pyzqaf https://fluxerstatus.com/incident/cmodhghe003vux6jep6pyzqaf Issues with connecting to the gateway Type: Incident Duration: 12 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Apr 23, 18:27:48 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 23, 18:39:36 GMT+0 - Resolved - This incident has been resolved. Apr 23, 18:40:32 GMT+0 - Postmortem - A brief production outage was caused when troubleshooting production state in the gateway and triggering a node failure. We are working towards better redundancy and protection against this class of failures in the future. Thanks for your patience! Type: Incident

Duration: 12 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>18:27:48</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>18:39:36</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 23</var>, <var data-var='time'>18:40:32</var> GMT+0</small><br><strong>Postmortem</strong> - A brief production outage was caused when troubleshooting production state in the gateway and triggering a node failure. We are working towards better redundancy and protection against this class of failures in the future. Thanks for your patience!.</p> ]]> Thu, 23 Apr 2026 18:27:48 +0000 https://fluxerstatus.com/incident/cmobtdub60014yl8raddwgrbs https://fluxerstatus.com/incident/cmobtdub60014yl8raddwgrbs Issues with connecting to the gateway due to maintenance cluster operations Type: Incident Duration: 13 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Apr 20, 16:35:42 GMT+0 - Investigating - We are currently investigating this incident. Apr 20, 16:48:25 GMT+0 - Resolved - Sorry about the brief downtime. We'd been putting off a downscaling of our Kubernetes cluster for a while, and I finally went ahead with it. During the process, the gateway exceeded its memory limit and rolled, which forced everyone to reconnect — a process that takes a little time. Now that we've ripped the bandaid off, this shouldn't be needed again in the near future. Type: Incident

Duration: 13 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>16:35:42</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 20</var>, <var data-var='time'>16:48:25</var> GMT+0</small><br><strong>Resolved</strong> - Sorry about the brief downtime. We'd been putting off a downscaling of our Kubernetes cluster for a while, and I finally went ahead with it. During the process, the gateway exceeded its memory limit and rolled, which forced everyone to reconnect — a process that takes a little time. Now that we've ripped the bandaid off, this shouldn't be needed again in the near future..</p> ]]> Mon, 20 Apr 2026 16:35:42 +0000 https://fluxerstatus.com/incident/cmo7f24tb00649sxct69uuzdl https://fluxerstatus.com/incident/cmo7f24tb00649sxct69uuzdl Issues connecting to the platform Type: Incident Affected Components: Fluxer API (api.fluxer.app) Apr 19, 11:21:54 GMT+0 - Investigating - We are currently investigating this incident. Apr 19, 11:47:41 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 19, 12:00:23 GMT+0 - Postmortem - Between **2026-04-19 06:16 UTC and 11:44 UTC (\~5h 28m)**, the public API returned errors on every Cassandra-backed request. A Cassandra container log grew unbounded (no Docker log rotation) and filled the disk on a database node, which tripped Cassandra's `disk_failure_policy=stop` and took the database offline. We truncated the log, restarted Cassandra, rolled the API pods, then added Docker log rotation, silenced the noisy logger, and installed a daily cron that truncates any runaway container log as a safety net. We apologise for how long this took to remediate. We're setting up alerting for this class of failure that bypasses do-not-disturb so it can't happen again. Apr 19, 12:09:57 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Affected Components:

<p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>11:21:54</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>11:47:41</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>12:00:23</var> GMT+0</small><br><strong>Postmortem</strong> - Between **2026-04-19 06:16 UTC and 11:44 UTC (\~5h 28m)**, the public API returned errors on every Cassandra-backed request. A Cassandra container log grew unbounded (no Docker log rotation) and filled the disk on a database node, which tripped Cassandra's `disk_failure_policy=stop` and took the database offline. We truncated the log, restarted Cassandra, rolled the API pods, then added Docker log rotation, silenced the noisy logger, and installed a daily cron that truncates any runaway container log as a safety net. We apologise for how long this took to remediate. We're setting up alerting for this class of failure that bypasses do-not-disturb so it can't happen again..</p> <p><small>Apr <var data-var='date'> 19</var>, <var data-var='time'>12:09:57</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 19 Apr 2026 11:21:54 +0000 https://fluxerstatus.com/incident/cmo5oepyd0ytengl5j7b733vb https://fluxerstatus.com/incident/cmo5oepyd0ytengl5j7b733vb Issues connecting to the platform. Type: Incident Duration: 39 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app), Fluxer API (api.fluxer.app) Apr 16, 12:06:47 GMT+0 - Investigating - We are currently investigating this incident. Apr 16, 12:42:23 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 16, 12:46:01 GMT+0 - Resolved - This incident has been resolved. Apr 16, 12:50:15 GMT+0 - Postmortem - This incident has been resolved. The traffic between two services (the API and database) was getting caught up in filters. We've taken this time to quickly move the database to be closer to the rest of the infrastructure too. Type: Incident

Duration: 39 minutes

Affected Components: ,

<p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>12:06:47</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>12:42:23</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>12:46:01</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 16</var>, <var data-var='time'>12:50:15</var> GMT+0</small><br><strong>Postmortem</strong> - This incident has been resolved. The traffic between two services (the API and database) was getting caught up in filters. We've taken this time to quickly move the database to be closer to the rest of the infrastructure too..</p> ]]> Thu, 16 Apr 2026 12:06:47 +0000 https://fluxerstatus.com/incident/cmo1fow5q0azyu46h6k2zyi86 https://fluxerstatus.com/incident/cmo1fow5q0azyu46h6k2zyi86 Issues with connecting to the gateway for some users Type: Incident Duration: 1 hour and 20 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Apr 15, 13:23:54 GMT+0 - Investigating - We are currently investigating this incident. Apr 15, 14:44:19 GMT+0 - Resolved - This incident has been resolved. Apr 15, 14:44:42 GMT+0 - Postmortem - Around 378 users were getting stuck because of a bug in our internal session counter. It wasn't decrementing properly in all cases, so it would incorrectly flag users as having too many active sessions and reject new connections. We've unblocked everyone affected and have fixed the underlying bug. Apologies for the trouble! Type: Incident

Duration: 1 hour and 20 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>13:23:54</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>14:44:19</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>14:44:42</var> GMT+0</small><br><strong>Postmortem</strong> - Around 378 users were getting stuck because of a bug in our internal session counter. It wasn't decrementing properly in all cases, so it would incorrectly flag users as having too many active sessions and reject new connections. We've unblocked everyone affected and have fixed the underlying bug. Apologies for the trouble!.</p> ]]> Wed, 15 Apr 2026 13:23:54 +0000 https://fluxerstatus.com/incident/cmo0307iy02llqteawv10xq88 https://fluxerstatus.com/incident/cmo0307iy02llqteawv10xq88 Issues with creating new accounts, confirming your email Type: Incident Duration: 3 hours and 26 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 14, 16:08:48 GMT+0 - Investigating - We are currently investigating this incident. Apr 14, 19:34:28 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 26 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>16:08:48</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>19:34:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Apr 2026 16:08:48 +0000 https://fluxerstatus.com/incident/cmnytgfh000azd5mz2wd64six https://fluxerstatus.com/incident/cmnytgfh000azd5mz2wd64six Issues with starting new sessions, maintaining existing sessions, and accessing some communities Type: Incident Duration: 1 day, 17 hours and 47 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Apr 14, 12:56:55 GMT+0 - Investigating - We are currently investigating this incident. Apr 14, 13:38:42 GMT+0 - Resolved - This incident has been resolved. Apr 14, 14:09:24 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day, 17 hours and 47 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>12:56:55</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>13:38:42</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>14:09:24</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 14 Apr 2026 12:56:55 +0000 https://fluxerstatus.com/incident/cmnymlnbf000o91ua0qjf7ui4 https://fluxerstatus.com/incident/cmnymlnbf000o91ua0qjf7ui4 Issues with connecting and using the platform. Type: Incident Duration: 1 day, 19 hours and 46 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app), Fluxer API (api.fluxer.app) Apr 13, 15:00:58 GMT+0 - Investigating - We are currently investigating this incident. Apr 13, 15:12:20 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 13, 15:20:03 GMT+0 - Postmortem - On April 13, 2026, the API intermittently served 503 because a risk-data sync emptied its Cassandra table during a failed rewrite, causing the API to fail closed. We restored service by repopulating the table and restarting the API, then fixed the underlying issue by removing duplicate cache-refresh work, adding sync locking, and changing the risk-list update flow so failed syncs can no longer wipe entire datasets. Apr 13, 15:38:49 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 13, 15:44:43 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 day, 19 hours and 46 minutes

Affected Components: ,

<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>15:00:58</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>15:12:20</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>15:20:03</var> GMT+0</small><br><strong>Postmortem</strong> - On April 13, 2026, the API intermittently served 503 because a risk-data sync emptied its Cassandra table during a failed rewrite, causing the API to fail closed. We restored service by repopulating the table and restarting the API, then fixed the underlying issue by removing duplicate cache-refresh work, adding sync locking, and changing the risk-list update flow so failed syncs can no longer wipe entire datasets..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>15:38:49</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>15:44:43</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 13 Apr 2026 15:00:58 +0000 https://fluxerstatus.com/incident/cmnxblbk1010pczlev8v9rfm3 https://fluxerstatus.com/incident/cmnxblbk1010pczlev8v9rfm3 Issues with all uploaded media being classified as NSFW Type: Incident Duration: 33 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 13, 08:24:15 GMT+0 - Investigating - We are currently investigating this incident. Apr 13, 08:57:38 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 33 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>08:24:15</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 13</var>, <var data-var='time'>08:57:38</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 13 Apr 2026 08:24:15 +0000 https://fluxerstatus.com/incident/cmnwxf5ph002hqyls8l5oo7jl https://fluxerstatus.com/incident/cmnwxf5ph002hqyls8l5oo7jl Issues with interacting with the platform following intentional restrictions imposed by trust & safety Type: Incident Duration: 9 hours and 46 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 12, 04:27:56 GMT+0 - Resolved - This incident has been resolved. Apr 11, 18:41:34 GMT+0 - Investigating - You will experience degraded platform functionality while our trust & safety team is actively stopping ongoing platform-wide abuse. Apr 11, 21:08:18 GMT+0 - Investigating - We are preparing to bring registrations back online with improved safeguards designed to better prevent abuse. We strongly condemn all illegal activity on our platform and are actively cooperating with law enforcement and other relevant authorities. Type: Incident

Duration: 9 hours and 46 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>04:27:56</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>18:41:34</var> GMT+0</small><br><strong>Investigating</strong> - You will experience degraded platform functionality while our trust & safety team is actively stopping ongoing platform-wide abuse..</p> <p><small>Apr <var data-var='date'> 11</var>, <var data-var='time'>21:08:18</var> GMT+0</small><br><strong>Investigating</strong> - We are preparing to bring registrations back online with improved safeguards designed to better prevent abuse. We strongly condemn all illegal activity on our platform and are actively cooperating with law enforcement and other relevant authorities..</p> ]]> Sat, 11 Apr 2026 18:41:34 +0000 https://fluxerstatus.com/incident/cmnuolbop01or91qmrrtjdahh https://fluxerstatus.com/incident/cmnuolbop01or91qmrrtjdahh Issues with connecting to the gateway Type: Incident Duration: 43 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Apr 10, 23:14:02 GMT+0 - Investigating - We are currently investigating this incident. Apr 10, 23:50:46 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. There will be some intermittent errors and latency until everyone has fully reconnected. Thanks for your understanding! Apr 10, 23:56:33 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 43 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>23:14:02</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>23:50:46</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result. There will be some intermittent errors and latency until everyone has fully reconnected. Thanks for your understanding!.</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>23:56:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 10 Apr 2026 23:14:02 +0000 https://fluxerstatus.com/incident/cmntivwsc0400mnmyqf2xhli4 https://fluxerstatus.com/incident/cmntivwsc0400mnmyqf2xhli4 Issues with accepting invites Type: Incident Duration: 16 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 10, 16:22:06 GMT+0 - Investigating - We are currently investigating this incident. Apr 10, 16:28:16 GMT+0 - Identified - The issue has been identified and a fix is being deployed. Apr 10, 16:38:03 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 16 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>16:22:06</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>16:28:16</var> GMT+0</small><br><strong>Identified</strong> - The issue has been identified and a fix is being deployed..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>16:38:03</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 10 Apr 2026 16:22:06 +0000 https://fluxerstatus.com/incident/cmnt464io000141tnas4orkdp https://fluxerstatus.com/incident/cmnt464io000141tnas4orkdp Issues with loading the platform. Type: Incident Duration: 16 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app), Fluxer API (api.fluxer.app) Apr 10, 00:35:13 GMT+0 - Investigating - We are currently investigating this incident. Apr 10, 00:51:03 GMT+0 - Resolved - This incident has been resolved, we encountered an issue between two of our providers; one of which we are moving off of. Type: Incident

Duration: 16 minutes

Affected Components: ,

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>00:35:13</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>00:51:03</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved, we encountered an issue between two of our providers; one of which we are moving off of..</p> ]]> Fri, 10 Apr 2026 00:35:13 +0000 https://fluxerstatus.com/incident/cmns6cf9903r1rzdfk7rke2mq https://fluxerstatus.com/incident/cmns6cf9903r1rzdfk7rke2mq Issues with receiving Plutonium after subscribing or buying gifts Type: Incident Duration: 10 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 9, 22:12:19 GMT+0 - Investigating - We are currently investigating this incident. You will receive it as soon as possible! Apr 9, 22:22:37 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 10 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>22:12:19</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. You will receive it as soon as possible!.</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>22:22:37</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 9 Apr 2026 22:12:19 +0000 https://fluxerstatus.com/incident/cmns18n2j04jfzilvi9z2f6w4 https://fluxerstatus.com/incident/cmns18n2j04jfzilvi9z2f6w4 Issues with accessing Fluxer Type: Incident Duration: 26 minutes Affected Components: Web Client (web.fluxer.app), Media Proxy (fluxerusercontent.com), Static Assets (fluxerstatic.com), Fluxer Gateway (gateway.fluxer.app), Fluxer API (api.fluxer.app), Website (fluxer.app) Apr 8, 13:43:21 GMT+0 - Investigating - We are currently investigating this incident. Apr 8, 14:01:48 GMT+0 - Investigating - We are continuing to investigate this incident. Apr 8, 14:05:45 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 8, 14:09:23 GMT+0 - Resolved - This incident has been resolved. Apr 8, 14:22:27 GMT+0 - Postmortem - At approximately 13:42 UTC, a networking issue at our upstream hosting provider Vultr caused all inbound traffic to be dropped, resulting in a complete outage across all Fluxer domains. We mitigated by rerouting traffic directly to instances under our control, bypassing the affected Vultr infrastructure. The root cause lies squarely with Vultr, and we're in contact with them to find out what went wrong. On the bright side, the workaround also resolved a pre-existing IPv6 issue we'd already filed with them; so, thanks for that, we guess! Type: Incident

Duration: 26 minutes

Affected Components: , , , , ,

<p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>13:43:21</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>14:01:48</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate this incident..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>14:05:45</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>14:09:23</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>14:22:27</var> GMT+0</small><br><strong>Postmortem</strong> - At approximately 13:42 UTC, a networking issue at our upstream hosting provider Vultr caused all inbound traffic to be dropped, resulting in a complete outage across all Fluxer domains. We mitigated by rerouting traffic directly to instances under our control, bypassing the affected Vultr infrastructure. The root cause lies squarely with Vultr, and we're in contact with them to find out what went wrong. On the bright side, the workaround also resolved a pre-existing IPv6 issue we'd already filed with them; so, thanks for that, we guess!.</p> ]]> Wed, 8 Apr 2026 13:43:21 +0000 https://fluxerstatus.com/incident/cmnq3m9w5005izytt35j1vujz https://fluxerstatus.com/incident/cmnq3m9w5005izytt35j1vujz Issues with accessing Fluxer over IPv6 Type: Incident Duration: 1 day, 11 hours and 31 minutes Affected Components: Web Client (web.fluxer.app), Fluxer Gateway (gateway.fluxer.app), Fluxer API (api.fluxer.app), Website (fluxer.app) Apr 7, 02:37:55 GMT+0 - Identified - We identified an issue with IPv6 not working on our upstream provider. We are working with them to to resolve this issue. Apr 8, 14:08:28 GMT+0 - Resolved - We have applied a fix for our other ongoing incident which in turn also fixed IPv6. Type: Incident

Duration: 1 day, 11 hours and 31 minutes

Affected Components: , , ,

<p><small>Apr <var data-var='date'> 7</var>, <var data-var='time'>02:37:55</var> GMT+0</small><br><strong>Identified</strong> - We identified an issue with IPv6 not working on our upstream provider. We are working with them to to resolve this issue..</p> <p><small>Apr <var data-var='date'> 8</var>, <var data-var='time'>14:08:28</var> GMT+0</small><br><strong>Resolved</strong> - We have applied a fix for our other ongoing incident which in turn also fixed IPv6..</p> ]]> Tue, 7 Apr 2026 02:37:55 +0000 https://fluxerstatus.com/incident/cmno0ene000gg4r71oh2xy0nz https://fluxerstatus.com/incident/cmno0ene000gg4r71oh2xy0nz Issues with embedded media and attachments, downloading files Type: Incident Duration: 16 minutes Affected Components: Media Proxy (fluxerusercontent.com), Static Assets (fluxerstatic.com), Fluxer API (api.fluxer.app) Apr 1, 15:04:45 GMT+0 - Investigating - We are currently investigating this incident. Apr 1, 15:14:39 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 1, 15:21:02 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 16 minutes

Affected Components: , ,

<p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>15:04:45</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>15:14:39</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>15:21:02</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 1 Apr 2026 15:04:45 +0000 https://fluxerstatus.com/incident/cmng6fzhd011k9jbl1drqzsob https://fluxerstatus.com/incident/cmng6fzhd011k9jbl1drqzsob Issues with sending media attachments in API requests from bot users Type: Incident Duration: 28 minutes Affected Components: Fluxer API (api.fluxer.app) Apr 1, 00:34:33 GMT+0 - Identified - We are continuing to work on a fix for this incident. Apr 1, 00:58:25 GMT+0 - Monitoring - We implemented a fix and are currently monitoring the result. Apr 1, 01:02:21 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 28 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>00:34:33</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>00:58:25</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix and are currently monitoring the result..</p> <p><small>Apr <var data-var='date'> 1</var>, <var data-var='time'>01:02:21</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Wed, 1 Apr 2026 00:34:33 +0000 https://fluxerstatus.com/incident/cmnfbcw6004zn12o7eexww5f9 https://fluxerstatus.com/incident/cmnfbcw6004zn12o7eexww5f9 Issues with browsing discovery, listing members, searching messages Type: Incident Duration: 35 minutes Affected Components: Fluxer API (api.fluxer.app) Mar 31, 22:15:31 GMT+0 - Identified - We are continuing to work on a fix for this incident. Mar 31, 22:32:16 GMT+0 - Identified - A patch is being rolled out. This will take 5-10 minutes. Mar 31, 22:50:53 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 35 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>22:15:31</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>22:32:16</var> GMT+0</small><br><strong>Identified</strong> - A patch is being rolled out. This will take 5-10 minutes..</p> <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>22:50:53</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 31 Mar 2026 22:15:31 +0000 https://fluxerstatus.com/incident/cmnf6e3db0tv412ny2cjpyyrz https://fluxerstatus.com/incident/cmnf6e3db0tv412ny2cjpyyrz Issues with receiving any sort of emails from Fluxer Type: Incident Duration: 1 hour and 28 minutes Affected Components: Fluxer API (api.fluxer.app) Mar 29, 19:00:42 GMT+0 - Resolved - Our upstream provider has resolved the outage on their end and email sending works again. You'll need to resend the verification email if you didn't receive it by pressing the button in the banner at the top of the screen. Thanks for giving Fluxer a go! Mar 29, 17:33:01 GMT+0 - Identified - We are continuing to work on a fix for this incident. Type: Incident

Duration: 1 hour and 28 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 29</var>, <var data-var='time'>19:00:42</var> GMT+0</small><br><strong>Resolved</strong> - Our upstream provider has resolved the outage on their end and email sending works again. You'll need to resend the verification email if you didn't receive it by pressing the button in the banner at the top of the screen. Thanks for giving Fluxer a go!.</p> <p><small>Mar <var data-var='date'> 29</var>, <var data-var='time'>17:33:01</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> ]]> Sun, 29 Mar 2026 17:33:01 +0000 https://fluxerstatus.com/incident/cmnc1f2zp00t311o23yxewdda https://fluxerstatus.com/incident/cmnc1f2zp00t311o23yxewdda Loading discovery and searching for messages Type: Incident Duration: 12 minutes Affected Components: Fluxer API (api.fluxer.app) Mar 29, 05:49:04 GMT+0 - Identified - We've identified the root cause and are deploying a fix. Mar 29, 06:01:28 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 12 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 29</var>, <var data-var='time'>05:49:04</var> GMT+0</small><br><strong>Identified</strong> - We've identified the root cause and are deploying a fix..</p> <p><small>Mar <var data-var='date'> 29</var>, <var data-var='time'>06:01:28</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Sun, 29 Mar 2026 05:49:04 +0000 https://fluxerstatus.com/incident/cmnbc9szf01m9y84oyq9dv09k https://fluxerstatus.com/incident/cmnbc9szf01m9y84oyq9dv09k Issues with connecting to the gateway Type: Incident Duration: 1 minute Affected Components: Fluxer Gateway (gateway.fluxer.app) Mar 26, 21:17:39 GMT+0 - Investigating - We are currently investigating this incident. Mar 26, 21:18:48 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 1 minute

Affected Components:

<p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>21:17:39</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Mar <var data-var='date'> 26</var>, <var data-var='time'>21:18:48</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 26 Mar 2026 21:17:39 +0000 https://fluxerstatus.com/incident/cmn7z4f7700aobyix2895x0tp https://fluxerstatus.com/incident/cmn7z4f7700aobyix2895x0tp Improving hardware allocation to the real-time gateway Type: Maintenance Duration: 21 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Mar 24, 17:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during this time. You may be frequently disconnected from the service. Mar 24, 17:51:18 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 21 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>17:30:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during this time. You may be frequently disconnected from the service..</p> <p><small>Mar <var data-var='date'> 24</var>, <var data-var='time'>17:51:18</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Tue, 24 Mar 2026 17:30:00 +0000 https://fluxerstatus.com/maintenance/cmn4w3607005x24xvzznkrqbb https://fluxerstatus.com/maintenance/cmn4w3607005x24xvzznkrqbb Fixing intermittent failures when sending messages in large communities Type: Maintenance Duration: 19 minutes Affected Components: Fluxer Gateway (gateway.fluxer.app) Mar 20, 17:45:00 GMT+0 - Identified - Communities may disappear and come back. We apologise for the inconvenience. Mar 20, 18:03:33 GMT+0 - Completed - Maintenance has completed successfully. Type: Maintenance

Duration: 19 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>17:45:00</var> GMT+0</small><br><strong>Identified</strong> - Communities may disappear and come back. We apologise for the inconvenience..</p> <p><small>Mar <var data-var='date'> 20</var>, <var data-var='time'>18:03:33</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> ]]> Fri, 20 Mar 2026 17:45:00 +0000 https://fluxerstatus.com/maintenance/cmmz70n94017257qzow3bvpcq https://fluxerstatus.com/maintenance/cmmz70n94017257qzow3bvpcq Upgrading the real-time and media infrastructure Type: Maintenance Duration: 15 hours and 25 minutes Affected Components: Web Client (web.fluxer.app) Mar 11, 18:41:20 GMT+0 - Identified - If your client crashed just recently, that was our fault, not yours! Everyone received a bad payload over their WebSocket connection and was forced to reload. Sorry! Mar 11, 13:40:00 GMT+0 - Identified - <https://bsky.app/profile/did:plc:tgm3isug3dbipufep4durid5/post/3mgrz7nqoms2o> Member lists have been disabled globally to shed some load to make the platform a bit more usable (the member list is the bane of my existence) in preparation for the next deploy that will let us bring them back, HQ back, improve loading times of media, eliminate random failures and intermittent latency, and a lot of other cool things! Mar 11, 21:39:31 GMT+0 - Identified - We're finishing up some remaining things caught in testing before rolling this out to everyone! Stay tuned 👀 Mar 12, 05:04:47 GMT+0 - Completed - We're still working on this! Member lists will remain disabled for a bit longer. Thanks for your patience — we want this upgrade to go as smoothly as possible so we're taking extra care to work out the remaining issues found during testing. Type: Maintenance

Duration: 15 hours and 25 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>18:41:20</var> GMT+0</small><br><strong>Identified</strong> - If your client crashed just recently, that was our fault, not yours! Everyone received a bad payload over their WebSocket connection and was forced to reload. Sorry!.</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>13:40:00</var> GMT+0</small><br><strong>Identified</strong> - <https://bsky.app/profile/did:plc:tgm3isug3dbipufep4durid5/post/3mgrz7nqoms2o> Member lists have been disabled globally to shed some load to make the platform a bit more usable (the member list is the bane of my existence) in preparation for the next deploy that will let us bring them back, HQ back, improve loading times of media, eliminate random failures and intermittent latency, and a lot of other cool things!.</p> <p><small>Mar <var data-var='date'> 11</var>, <var data-var='time'>21:39:31</var> GMT+0</small><br><strong>Identified</strong> - We're finishing up some remaining things caught in testing before rolling this out to everyone! Stay tuned 👀.</p> <p><small>Mar <var data-var='date'> 12</var>, <var data-var='time'>05:04:47</var> GMT+0</small><br><strong>Completed</strong> - We're still working on this! Member lists will remain disabled for a bit longer. Thanks for your patience — we want this upgrade to go as smoothly as possible so we're taking extra care to work out the remaining issues found during testing..</p> ]]> Wed, 11 Mar 2026 13:40:00 +0000 https://fluxerstatus.com/maintenance/cmmm3biyt0b6hn9qfezhx0l5b https://fluxerstatus.com/maintenance/cmmm3biyt0b6hn9qfezhx0l5b API Migration (Part 2!) Type: Maintenance Duration: 4 days, 23 hours and 4 minutes Affected Components: Web Client (web.fluxer.app), Media Proxy (fluxerusercontent.com), Static Assets (fluxerstatic.com), Fluxer Gateway (gateway.fluxer.app), Fluxer API (api.fluxer.app), Website (fluxer.app) Feb 28, 04:22:34 GMT+0 - Identified - We're still in the process of working on the migration, but we've flipped over all of the infrastructure to the new stuff now! We're working on some bugs still, but we should still be on track for 10 AM UTC on Saturday. Mar 1, 11:04:26 GMT+0 - Completed - Maintenance has completed successfully. Feb 26, 14:34:25 GMT+0 - Identified - We're still working on fixing some some bugs with the updated gateway, which are causing all guilds to become unavailable on certain changes and making the platform unstable for brief periods of time before we roll it out to a wider audience. Feb 26, 19:41:15 GMT+0 - Identified - The media proxy and the static assets remain stable on the new infrastructure, so both are being marked operational now. We are continuing to have a subset of traffic hitting the new infrastructure and hope to fully cut it over soon. Feb 24, 12:00:00 GMT+0 - Identified - We are planning for a scheduled maintenance during this time to complete the migration of the infrastructure. We hope to keep the platform online as much as possible throughout this transition. Feb 24, 12:00:01 GMT+0 - Identified - Maintenance is now in progress Feb 24, 14:21:09 GMT+0 - Identified - The infrastructure migration is still in progress and the maintenance window has been extended by an hour to accommodate needs. Feb 24, 20:01:47 GMT+0 - Identified - We're finally ready to start cutting over traffic! Things will continue to be a little bumpy as we sort out and scale up the new infrastructure, and may become unavailable entirely for some users for a short period. If you are using the official client and you're not let back in, please try to hit \[CTRL\] + \[R\] (or \[**⌘**\] + \[R\] if you're a Mac user) to reload it to see if that solves the issue. Feb 25, 09:26:13 GMT+0 - Identified - Sorry for the lack of updates, we've been heads down working on getting everything online and haven't had time to get the status page properly updated. We're almost to the point where things are in working order, however, there's an existing issue with the client not loading properly that we are working on fixing. Feb 27, 21:46:29 GMT+0 - Identified - Just wanted to share an update here for everyone watching alongside at home that we're still working on things behind the scenes. Feb 25, 20:20:57 GMT+0 - Identified - The maintenance is still underway, however preliminary testing with the new infrastructure has been well! We hope to be fully online again with a little treat for everyone soon. 👀 Type: Maintenance

Duration: 4 days, 23 hours and 4 minutes

Affected Components: , , , , ,

<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>04:22:34</var> GMT+0</small><br><strong>Identified</strong> - We're still in the process of working on the migration, but we've flipped over all of the infrastructure to the new stuff now! We're working on some bugs still, but we should still be on track for 10 AM UTC on Saturday..</p> <p><small>Mar <var data-var='date'> 1</var>, <var data-var='time'>11:04:26</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>14:34:25</var> GMT+0</small><br><strong>Identified</strong> - We're still working on fixing some some bugs with the updated gateway, which are causing all guilds to become unavailable on certain changes and making the platform unstable for brief periods of time before we roll it out to a wider audience..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>19:41:15</var> GMT+0</small><br><strong>Identified</strong> - The media proxy and the static assets remain stable on the new infrastructure, so both are being marked operational now. We are continuing to have a subset of traffic hitting the new infrastructure and hope to fully cut it over soon..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>12:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are planning for a scheduled maintenance during this time to complete the migration of the infrastructure. We hope to keep the platform online as much as possible throughout this transition..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>12:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>14:21:09</var> GMT+0</small><br><strong>Identified</strong> - The infrastructure migration is still in progress and the maintenance window has been extended by an hour to accommodate needs..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>20:01:47</var> GMT+0</small><br><strong>Identified</strong> - We're finally ready to start cutting over traffic! Things will continue to be a little bumpy as we sort out and scale up the new infrastructure, and may become unavailable entirely for some users for a short period. If you are using the official client and you're not let back in, please try to hit \[CTRL\] + \[R\] (or \[**⌘**\] + \[R\] if you're a Mac user) to reload it to see if that solves the issue..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>09:26:13</var> GMT+0</small><br><strong>Identified</strong> - Sorry for the lack of updates, we've been heads down working on getting everything online and haven't had time to get the status page properly updated. We're almost to the point where things are in working order, however, there's an existing issue with the client not loading properly that we are working on fixing..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>21:46:29</var> GMT+0</small><br><strong>Identified</strong> - Just wanted to share an update here for everyone watching alongside at home that we're still working on things behind the scenes..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>20:20:57</var> GMT+0</small><br><strong>Identified</strong> - The maintenance is still underway, however preliminary testing with the new infrastructure has been well! We hope to be fully online again with a little treat for everyone soon. 👀.</p> ]]> Tue, 24 Feb 2026 12:00:00 +0000 https://fluxerstatus.com/maintenance/cmm04p16n0e8tp79zr7mh42cp https://fluxerstatus.com/maintenance/cmm04p16n0e8tp79zr7mh42cp API Migration Type: Maintenance Duration: 2 hours and 50 minutes Affected Components: Media Proxy (fluxerusercontent.com), Website (fluxer.app), Fluxer API (api.fluxer.app), Web Client (web.fluxer.app), Static Assets (fluxerstatic.com) Feb 24, 02:00:00 GMT+0 - Identified - We are working on migrating Fluxer to newer infrastructure. Stay tuned. Feb 24, 04:49:35 GMT+0 - Completed - Maintenance will be ending shortly but work will continue on the web client in the meantime. The progress of the migration will resume tomorrow morning as things have stabilized for this evening. Type: Maintenance

Duration: 2 hours and 50 minutes

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>02:00:00</var> GMT+0</small><br><strong>Identified</strong> - We are working on migrating Fluxer to newer infrastructure. Stay tuned..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>04:49:35</var> GMT+0</small><br><strong>Completed</strong> - Maintenance will be ending shortly but work will continue on the web client in the meantime. The progress of the migration will resume tomorrow morning as things have stabilized for this evening..</p> ]]> Tue, 24 Feb 2026 02:00:00 +0000 https://fluxerstatus.com/maintenance/cmlzz802i06jx13wlgvhugd6f https://fluxerstatus.com/maintenance/cmlzz802i06jx13wlgvhugd6f