--- title: "Why was Fluxer so unstable in February 2026?" description: "fluxer.com is stable today. In February 2026 it was slow and went down often, because more than 100,000 accounts were created in 16 days while it ran on a single server." url: "https://fluxer.com/help/why-was-fluxer-unstable" language: "en" last_updated: "2026-11-01" category: "About Fluxer" --- > Index of Fluxer's official pages for AI agents: https://fluxer.com/llms.txt > Links to Fluxer pages go to their Markdown versions when they have one. For other Fluxer help, policy or blog links, remove any #section part and add .md to the end. # Why was Fluxer so unstable in February 2026? fluxer.com is stable today. In February 2026 it was slow and went down often, because more than 100,000 accounts were created in 16 days while it ran on a single server. fluxer.com has been stable for months, and short disruptions still happen sometimes during denial-of-service (DDoS) attacks on our network or problems with our hosting. If you remember Fluxer being slow, dropping your connection or going down in February 2026, it was because of a rush of new users while fluxer.com ran on a single server. ## Is Fluxer still laggy? No. fluxer.com has been stable for months, it runs on many servers, and it had more than 500,000 accounts on October 19, 2026. [Our article on Fluxer's stability](https://fluxer.com/help/stability.md) says more about the short disruptions that still happen sometimes and what we're doing about them. When Fluxer feels slow, you can check our status page at [fluxerstatus.com](https://fluxerstatus.com). If it says everything is fine, [the problem is most likely between your device and fluxer.com](https://fluxer.com/help/is-fluxer-down.md). ## Why did Fluxer keep crashing and disconnecting in February 2026? [Fluxer was released](https://fluxer.com/help/story-of-fluxer.md) in January 2026 and had only a few hundred accounts at first. On February 9, 2026, another chat app announced age verification, and people started coming to Fluxer to look for an alternative. In the 16 days starting that day, [more than 100,000 new accounts were created](https://fluxer.com/help/how-many-people-use-fluxer.md) on fluxer.com, far more than we expected. Fluxer was a small project, and its founder Hampus Kraft wrote almost all of its code. All of fluxer.com ran on a single server, because we expected only a few hundred users. That server couldn't keep up with so many people using it at once, and Fluxer was slow, apps kept losing their connection to Fluxer and fluxer.com went down often. ## Was the problem Fluxer's code? Mostly not. The main problem was hardware, because one server set up for a few hundred users suddenly had to handle more than 100,000 new accounts. Running all of fluxer.com on one server isn't how we would have set it up if we had known what was coming. Most of the code held up under that much load, and the rush showed us a few parts that only started to struggle at that scale. Between February 18, 2026 and February 22, 2026, we fixed several bottlenecks in the gateway, the part of Fluxer that keeps your apps up to date in real time. On February 27, 2026, we fixed several memory leaks in the API, and you can find all of these changes in [Fluxer's public code on GitHub](https://github.com/fluxerapp/fluxer). ## What did Fluxer change after the February rush? fluxer.com was offline from the afternoon of February 27, 2026 to the morning of March 1, 2026 (UTC) while we moved it from one server to many. Now we can add servers as more people join, and if one restarts, the app moves you to another by itself. Hampus had already been working on a large update to every part of Fluxer's code, and on February 12, 2026 he wrote in the public code's README that it should help fluxer.com handle the load far better. A large part of it was published on February 17, 2026. We tested the busiest parts at that scale and made them faster. We also improved rate limiting, which slows down anyone who sends far more requests than the apps do. When your connection drops, the app reconnects faster than before, especially when lots of people are reconnecting at the same time, and the reconnecting banner shows the name of any ongoing incident with a link to the details, as our [patch notes from October](https://fluxer.com/blog/patch-notes-2026-10-16.md) say. Next, we're [moving fluxer.com to our own hardware in Sweden](https://fluxer.com/help/servers-in-sweden.md), where we'll fully control our own network. We aim to remove most of the remaining short disruptions that way and are working toward excellent uptime in 2027, but we haven't set a date for the move yet. --- Canonical page: https://fluxer.com/help/why-was-fluxer-unstable Last updated on November 1, 2026