Bots Overload OT Commerce Store on OT Box, Spike Paid OTAPI Calls Mistaken for DDoS Attack
An online store built on OT Commerce faced severe performance degradation and sharply rising operational costs when automated bots began systematically crawling product pages. CPU utilization repeatedly hit 98–100% while the number of paid calls to the external OTAPI platform increased six- to seven-fold over three days.
The owner initially described the problem as a DDoS attack because requests arrived from many different IP addresses across multiple countries. However, the traffic was not a volumetric network-layer assault but rather automated HTTP requests that triggered heavy server-side logic and billable OTAPI operations.
The store uses the ready-made OT Box solution, which integrates with the OpenTrade Commerce platform via OTAPI. When a visitor opens a category, search result or product card, the engine may call paid methods such as SearchItemsFrame, GetItemInfo or GetItemFullInfo to fetch live data from Taobao, Tmall, 1688, Alibaba and other marketplaces. Each such call is metered, and some operations carry a multiplier cost.
A previously installed anti-bot module running directly on the VPS failed to stop the problematic traffic. The module’s vendor confirmed it was not designed to address large-scale parsing scenarios. After the owner restricted access to product cards for unauthenticated users, the automated activity persisted.
Switching the site behind the CRONARMOR WAF reversed the situation. Within hours of the cut-over on 16 September, CPU load fell from peaks of 80–100% to mostly single-digit percentages. Over the following 24 hours the server rarely exceeded 9% utilization.
Filtering statistics for the partial period showed 279,680 total HTTP requests, of which 276,100 targeted web pages. Automated requests blocked at the earliest stage numbered 115,660 (41.9%), with 99.3% of them never reaching the origin. Behavioral bots visible in analytics accounted for only 1,367 requests (0.5%), while 27,190 legitimate search-engine crawlers were explicitly permitted.
The case illustrates that high CPU combined with rising external API costs can result from scraping bots rather than classic L7 DDoS. Proper distinction requires analysis of request patterns, not merely the number of source countries or visible analytics events.
Related articles
OpenAI Releases GPT-6.1 Terra: Cost-Effective Model Focused on Computer Control, Image Analysis and Practical Automation
OpenAI has launched GPT-6.1 Terra, a new model positioned between its high-end GPT-6 Astra and more affordable options in the GPT-6 family. The model emphasizes real-world computer interaction, visual understanding of documents and interfaces, and reduced error rates rather than raw reasoning benchmarks. It supports a 1.05 million token context window, image inputs, and tool use through the Responses API while cutting input token prices by half compared with its predecessor. Published benchmarks show substantial gains on Terminal-Bench 4.0, OSWorld 2.1 and Agents' Last Exam, with error rates dropping sharply at both low and maximum reasoning levels. OpenAI stresses that the model still requires human oversight for high-stakes actions and does not directly process audio or video. The release targets developers and enterprises seeking reliable automation of repetitive multi-step tasks at lower cost than flagship models.
Yandex Black October: How Architectural Flaws and Capacity Mismanagement Turned Data Center Losses Into a 11-Day Fintech Coma
In October 2026 three Yandex data centers in Central Russia were physically destroyed within days, triggering the collapse of Yandex Cloud and multiple core services. Between the first and third site failures engineers had 74 hours to restore quorum and rebalance workloads yet failed to do so because Control Plane components remained tied to the lost zone and spare capacity had been eliminated to cut costs. Core banking and BNPL systems entered Read-Only mode after losing quorum, forcing a complete stop-the-world reconciliation that lasted until 22 October. Backups stored inside the same regional S3 buckets proved unusable, resulting in a seven-day RPO and primary-key collisions after restoration. The incident exposed that Metro-Cluster designs had been incorrectly treated as full Disaster Recovery and that aggressive AP microservice patterns created logical split-brain conditions outside the database layer.
Astra Group Releases Low-Code Astra AI Platform for Building Corporate AI Agents in Closed Environments
Astra Group has launched the Astra AI Platform, a low-code constructor designed for creating corporate AI applications that operate entirely within closed circuits without reliance on foreign clouds. The platform targets small and medium businesses as well as large corporations, enabling rapid deployment of AI secretaries, technical support assistants, and other agents in days rather than months. It forms part of the broader Astra AI ecosystem and includes two main constructors: one for machine learning model training and deployment, and another for LLM-based language assistants, document search, and process automation. Users can assemble scenarios from visual blocks, debug them in real time, or extend functionality with custom Python code when needed. The solution supports RAG-based knowledge bases, integration with external tools such as CRM and ERP systems, and the coordination of multiple agents for distributed task handling. One demonstrated use case involves processing ten pages of engineering drawings and specifications in five minutes to prepare data for downstream systems. The product is already listed in the Russian domestic software registry and available to customers.
Multi-Tenancy Isolation in VictoriaMetrics, VictoriaLogs and Grafana: Building Client Separation in a Shared Stack
Voltir runs a single shared monitoring stack consisting of VictoriaMetrics, VictoriaLogs, Grafana and vmalert for all customers instead of deploying separate instances per tenant. Isolation relies on numeric account IDs enforced at every layer: nginx validates tokens against the platform API before proxying writes, Grafana data sources hard-code tenant accounts, and vmalert rules receive automatic account filters. The team discovered that a single malformed rule or template could break alerting for every tenant because vmalert loads the entire rules directory at once. They also found that Grafana automatically created personal organizations granting Org Admin rights, accumulating hundreds of orphaned organizations and users that consumed disk space and resources. A dedicated cleanup module plus hourly reconciliation now removes rules, organizations, series and users when a tenant is deleted, while isolation tests verify both data and API objects across tenants.