Incidents reported on status page for UpTrader https://status.uptrader.io/ https://d1lppblt9t2x15.cloudfront.net/logos/321077b9dedc1ce39669c1f61ed8cbb5.png https://status.uptrader.io/ en https://status.uptrader.io/ Wed, 04 Feb 2026 13:24:34 +0000 https://status.uptrader.io/#61b844b1ad1c1a47f199e7f73d15f20c9e6f6d7ab9c65bfbb01f34fc5e3144df UpTrader CRM recovered https://status.uptrader.io/ Wed, 04 Feb 2026 13:22:55 +0000 https://status.uptrader.io/#61b844b1ad1c1a47f199e7f73d15f20c9e6f6d7ab9c65bfbb01f34fc5e3144df UpTrader CRM went down https://status.uptrader.io/ Tue, 03 Feb 2026 11:56:34 +0000 https://status.uptrader.io/#9bd1cb75fd1601e658be95f0ebd46a0f8fc18601ec53f4272942ef51f22721bb UpTrader CRM recovered https://status.uptrader.io/ Tue, 03 Feb 2026 11:56:03 +0000 https://status.uptrader.io/#9bd1cb75fd1601e658be95f0ebd46a0f8fc18601ec53f4272942ef51f22721bb UpTrader CRM went down https://status.uptrader.io/ Wed, 28 Jan 2026 23:44:01 +0000 https://status.uptrader.io/#96f7110b59874840fa333e1c9d4ac0755860d79aa2acd84256627144a4bfe445 UpTrader CRM recovered https://status.uptrader.io/ Wed, 28 Jan 2026 23:38:26 +0000 https://status.uptrader.io/#96f7110b59874840fa333e1c9d4ac0755860d79aa2acd84256627144a4bfe445 UpTrader CRM went down https://status.uptrader.io/ Wed, 28 Jan 2026 23:26:03 +0000 https://status.uptrader.io/#4da2e3f16a4c0d502a1352412a77f784c7803660977c52660b547c0ec3d9efa6 UpTrader CRM recovered https://status.uptrader.io/ Wed, 28 Jan 2026 23:18:01 +0000 https://status.uptrader.io/#4da2e3f16a4c0d502a1352412a77f784c7803660977c52660b547c0ec3d9efa6 UpTrader CRM went down https://status.uptrader.io/ Tue, 06 Jan 2026 19:44:55 +0000 https://status.uptrader.io/#cfc4f89cea746aeaca096680f745ba342680f4f869ab009feab66a7f33d21009 UpTrader CRM recovered https://status.uptrader.io/ Tue, 06 Jan 2026 19:43:54 +0000 https://status.uptrader.io/#cfc4f89cea746aeaca096680f745ba342680f4f869ab009feab66a7f33d21009 UpTrader CRM went down https://status.uptrader.io/ Thu, 04 Dec 2025 05:57:16 +0000 https://status.uptrader.io/#7172fae68995d180de77d9c14a8f10c70cd371236a1a49c77138eedf59a378f4 UpTrader CRM recovered https://status.uptrader.io/ Thu, 04 Dec 2025 05:54:09 +0000 https://status.uptrader.io/#7172fae68995d180de77d9c14a8f10c70cd371236a1a49c77138eedf59a378f4 UpTrader CRM went down https://status.uptrader.io/ Wed, 03 Dec 2025 14:03:43 +0000 https://status.uptrader.io/#a51b1aa810f513e338ef174081a194d946887523bd07c959b5e7acbce37d2f60 UpTrader CRM recovered https://status.uptrader.io/ Wed, 03 Dec 2025 13:46:42 +0000 https://status.uptrader.io/#a51b1aa810f513e338ef174081a194d946887523bd07c959b5e7acbce37d2f60 UpTrader CRM went down https://status.uptrader.io/ Fri, 14 Nov 2025 14:39:16 +0000 https://status.uptrader.io/#ae125353ab53b7ee0e1cc53aa64cfdff9604d46678de1acefee0bb733bb3ac50 UpTrader CRM recovered https://status.uptrader.io/ Fri, 14 Nov 2025 14:38:15 +0000 https://status.uptrader.io/#ae125353ab53b7ee0e1cc53aa64cfdff9604d46678de1acefee0bb733bb3ac50 UpTrader CRM went down https://status.uptrader.io/incident/464171 Tue, 19 Nov 2024 14:46:00 -0000 https://status.uptrader.io/incident/464171#e9c60a7c4cafab939e904dc0d9f07f188678f08b9f69f85547739d4140e02b1e **Date:** November 19, 2024 * * * **1\. Introduction** This report provides a detailed account of the incidents that led to extended downtimes of our UpTrader CRM system on November 1 and November 19, 2024. These incidents were unprecedented in our seven years of operation, and we are addressing them with utmost seriousness to prevent future occurrences. **2\. Incident Description** **November 1, 2024** - **Time:** At 01:14 UTC, the UpTrader CRM system began experiencing significant performance issues. - **Issue:** A network card on one of our servers started malfunctioning. While it continued to process traffic, it did so at a drastically reduced speed. - **Diagnosis:** The degraded performance made it challenging to promptly identify the root cause. - **Resolution:** Upon determining the issue, the affected server was rebooted, restoring normal operations. - **Downtime Duration:** 2 hours. Analysis revealed that the network card malfunctioned due to processing excessive data without regular reboots. **November 19, 2024** - **Time:** At 10:39 UTC, a similar issue occurred on another server that had not been rebooted since the previous incident. - **Issue:** The network card failed, leading to service disruption. - **Resolution:** The server was rebooted, and the system was restored after 25 minutes of downtime. Following this, we decided to proactively reboot the third and final server to prevent further disruptions. - **Additional Issue:** During the reboot of the third server, a system misconfiguration caused the entire production cluster to go down. - **Resolution:** Multiple issues were identified and resolved. The system was fully operational after 1 hour and 58 minutes of intermittent downtime. **3\. Timeline of Events** - **November 1, 2024** - **01:14 UTC:** Downtime began due to a malfunctioning network card on Server 1. - **03:12 UTC:** Server 1 rebooted; system restored. - **November 19, 2024** - **10:39 UTC:** Network card failure on Server 2 caused service disruption. - **11:04 UTC:** Server 2 rebooted; system restored after 25 minutes. - **11:20 UTC:** Initiated reboot of Server 3. - **11:20 UTC - 13:18 UTC:** System misconfiguration led to intermittent production cluster downtime. - **13:18 UTC:** System restored after resolving multiple issues. **4\. Root Cause Analysis** - **Network Card Malfunctions:** The primary cause was the network cards processing excessive data without regular reboots, leading to performance degradation. - **Delayed Diagnosis:** The servers continued to process traffic slowly, complicating timely identification of the issue. - **System Misconfiguration:** An unforeseen misconfiguration in the system settings caused a complete cluster shutdown during the reboot of the third server. **5\. Impact Assessment** - **Service Downtime:** - **November 1:** 2 hours of system unavailability. - **November 19 (First Incident):** 25 minutes of downtime. - **November 19 (Second Incident):** 1 hour and 58 minutes of intermittent system downtime. - **Business Impact:** Clients experienced interruptions in accessing the UpTrader CRM system, affecting their business operations. **6\. Preventive Measures and Future Actions** To prevent similar incidents, we are implementing the following measures: 1. **Infrastructure Enhancement:** - Increasing the capacity of our production cluster to provide additional resources and redundancy. - Upgrading server  hardware to handle higher loads efficiently. 2. **Proactive Maintenance:** - Introducing scheduled reboots during low-traffic periods. 3. **System Configuration Review:** - Conducting a comprehensive analysis of current system configurations. - Adjusting settings to enhance fault tolerance and prevent misconfigurations. - Establishing protocols for configuration changes and system reboots to ensure stability. **7\. Conclusion** We deeply regret the inconvenience caused by these incidents. Ensuring the reliability and stability of our services is our top priority. We are committed to taking all necessary steps to prevent future occurrences and to maintain the trust our clients have placed in us over the past seven years. **For any further inquiries or assistance, please contact our support team at support@uptrader.io** * * * **Prepared by:** Vasily Alexeev CEO/CTO UpTrader