
Even the status page needed help
In February 2023, a BB post suspected that individual users had coordinated an attack. The following month brought a stranger update: after a DDoS test, BB’s own status service had been mistaken for an attacker.
The announcement ended with one reassuring word: “Fixed.” Even the page that tells you whether things work had needed a little help.
A thank-you in the middle of the afternoon
On 26 February 2024, BB announced another DDoS attack. The chat had reports of bots failing. Later that afternoon, one reply said things seemed to be working again, with a thank-you attached.
The bot asked for JSON. It got a loading page.
In May, a developer described another headache: their API request expected JSON data but received a loading page instead. A browser could get through; their bot could not. They compared notes with other users and kept explaining the problem.
The conversation grew prickly. The owner explained that the page belonged to DDoS protection and said they would try to fix the API trouble. The builder also thanked BB for helping them create bots. Frustration and affection fitted into the same support thread.
Better news in July
On 10 July 2024, BB reported faster request processing. In early August, the owner described the previous month as very stable.
Recovery reports in 2026
A separate attack in May 2026 brought more work on the defenses. On 31 May, BB reported all major services operating normally and thanked users whose reports and patience had helped the team respond faster.
In September 2026, the owner describes the service as stable.
From the archive
Community chat · 26 February 2024; an individual report of recovery
Community chat · 12–14 May 2024; the builder’s report and the owner’s replies
Community chat · 4 August 2024
Current perspective · owner’s account, September 2026

