WALL OF SHAME
Operational Incidents Review & Management Accountability
Public Apology and Summary Regarding Operational Incidents and Management Failures Over the Past Year
Dear Users,
Looking back at the period from May to December 2025, due to severe internal disagreements, management infighting, and chaotic decision-making, everyone experienced a series of extremely poor services. Although these decisions were not made solely by me, they were carried out in the name of BitsFlowCloud, so I consider them entirely my own actions. I deeply regret and feel guilty about this. To avoid repeating past mistakes, I have decided to publicly review the six core issues that occurred, face our errors honestly, and extend my most sincere apologies to all affected users.
I. Review of Major Operational Failures
01 Regulatory Failure: Hong Kong PRO Node Procurement (May 2025)
Facts: During the procurement of Hong Kong PRO hypervisors, due to breakdowns in internal communication and regulatory mechanisms failing caused by infighting, the partner responsible for procurement deliberately concealed actual costs and configurations to profit personally, delivering servers with severely reduced bandwidth.
Result: Although we deducted payment channel fees and provided cash refunds to applicants, this cannot compensate for the losses to users' businesses. This was a serious consequence of internal management negligence.
02 Conflict of Interest: Frequent UK London Node Migrations (May-Sep 2025)
Facts: During these four months, constrained by conflicting profit motives within the team, the internal team forcibly pushed through decisions to blindly pursue low costs and expand profits, resulting in at least 3 migrations of the UK node. Although nominally "configuration upgrades," the essence was sacrificing stability for cheap resources.
Result: The node was taken offline in October due to failed operational strategy. We assisted users in migrating to German nodes or refunded the remaining value. This behavior of sacrificing user experience due to internal gaming was extremely wrong.
03 Slow Response: Long-term HK Node Instability (Aug-Oct 2025)
Facts: The Hong Kong node experienced one migration during this period, followed by prolonged DDoS attacks. Response was delayed due to internal disputes over technical solutions, and we failed to provide effective defense solutions, resulting in long-term service unavailability.
Result: The node was forced offline in October, with users migrated to Tokyo nodes or refunded to balance.
04 Hasty Planning: Tokyo PRO Node Short-lived Shutdown (Oct-Dec 2025)
Facts: To accommodate Hong Kong users, we hastily launched the Tokyo PRO node. However, hasty planning caused by the decision-making layer's inability to unify opinions led to its shutdown after only two months due to strategic changes resulting from intensified internal contradictions.
Current Status: Refund work for this node is currently in progress, and we will ensure every user's refund is properly handled.
05 Execution Disconnect: System Migration & Improper Asset Handling (Nov-Dec 2025)
Facts: During the migration from WHMCS to Blesta, execution disconnect caused by the team falling apart led to most hypervisors going offline. More seriously, under chaotic management conditions, after new nodes came online, we arbitrarily deducted users' existing account balances by percentage, unilaterally downgraded VPS hardware (from EPYC/RYZEN to Intel Gold), and raised renewal prices.
Correction: We recognize this as a serious violation of user rights. We have restored renewal prices for existing customers and introduced price protection. I deeply apologize for the errors in balance handling.
06 Emotional Loss of Control: Forum Comments Attacking Users (After Dec 2025)
Facts: In December 2025, I completed team restructuring by buying out equity and transitioned to full operation by myself. However, when facing external questioning, influenced by the high pressure of the chaotic internal environment during the restructuring, I failed to maintain professional conduct and verbally attacked some users on forums like NodeSeek.
Reflection: This emotional venting not only failed to solve problems but also hurt users. I formally apologize to all friends who were offended by my words.
II. Summary and Commitments
Looking back at this journey of over half a year, I must honestly admit: all disasters, whether natural or man-made, ultimately stem from severe ideological conflicts and management infighting within the team.
In the past, due to decision-making failures caused by entanglements of interest between partners, and huge divergences in development direction, we repeatedly harmed user trust regarding server configurations, stability, and pricing. What shames me even more is that when problems arose, chaotic internal voices prevented me from immediately reassuring users, and I responded with arrogance and aggression.
After painful reflection, I make the following commitments:
-
Thorough Internal Management Reform: With the completion of member changes in December, internal "quick money" and "kickback" issues, as well as cancers that hindered unified team collaboration, have been removed. Future operations will be under my full responsibility, shifting focus from "pursuing profit" to "ensuring stability."
-
Respect Contractual Spirit: There will be no more arbitrary changes to user assets (balance), unilateral hardware downgrades, or other serious breaches of contract. All product changes will be announced in advance, protecting existing customer rights.
-
Correct Service Attitude: I will deeply reflect on my public statements and humbly accept community supervision. Regardless of questioning, problem-solving will be prioritized, and there will be no more verbal attacks.
Please give me a chance to correct my mistakes and start anew. I don't expect immediate forgiveness, but I will use actual actions and stable service in the coming days to gradually repair everyone's trust.
Once again, to everyone: I am sorry.