- The “unusual activity” message is an anti-bot block triggered when site traffic looks automated, often due to rapid requests, shared VPN/proxy IPs, disabled cookies/JavaScript, extensions, or malware.
- Bloomberg uses a CAPTCHA-based verification flow and requires cookies and JavaScript, typically showing a reference ID for the block.
- Fixes include completing the CAPTCHA, enabling cookies/JavaScript, clearing cache, disabling VPNs/extensions, rebooting routers to change IPs, and scanning for malware.
- Shared or institutional networks can be blocked despite benign users, raising operational risk and highlighting the need for better transparency and appeal paths.
Read More
The message “We’ve detected unusual activity from your computer network” is a standard web-security response when traffic from a device or network diverges from patterns expected of human users. Key triggers include sending many requests in a short span, using VPN or proxy services that share IP addresses with other users, having cookies or JavaScript disabled, or even hidden malware or browser extensions generating automated traffic.
In the Bloomberg instance you saw, the page explicitly cites a CAPTCHA challenge (via PerimeterX or similar service), a block reference ID, and a requirement that the browser support cookies/JavaScript. These are definitive anti-bot measures employed to verify human activity. [Primary Article HTML]
From an investment banking or corporate setting, such blocks carry real strategic risks. If terminals, data feeds or research portals are intermittently inaccessible, time-sensitive trading decisions, risk assessments, or compliance obligations may be impaired. Moreover, shared or institutional IPs—common in offices and co-working facilities—compound the likelihood of collateral damage, even if no misconduct on individual users’ part occurred. Maintaining good network reputation, ensuring infrastructure doesn’t unintentionally generate “noisy” traffic, and coordinating with providers (e.g. VPNs, corporate ISPs) are therefore essential.
Another dimension is the transparency and governance of such detection systems. The lack of clear feedback or contestability for blocked users can degrade trust. For example, users presented only with a generic reference ID and link to Terms of Service are often left wondering what specifically triggered the block—robots? DoS? Botnets? Enforced policies? Strategically, entities like Bloomberg and other data providers may consider auditability, clearer explanations, and customer turn-around paths to improve UX without compromising security.
Open questions and areas for caution include:
- How frequently are false positives happening across financial institutions vs. general consumers?
- What metrics or thresholds are used in real-time to flag “unusual traffic,” and can they be tuned for different user classes (e.g. terminal customers vs public site visitors)?
- What are the cost implications (time delays, missed trades) for institutional clients when access is blocked, and how do providers compensate for that?
- How transparent and responsive is the appeal or unblock process? Does a reference ID actually lead to speed resolution?
- Is there regulatory oversight for these automated access controls, especially when used by information gatekeepers in finance or news?
Supporting Notes
- Site triggers CAPTCHA when traffic appears non-human; also requires JavaScript and cookies enabled.[Primary Article HTML]
- Shared IPs (e.g. corporate, public Wi-Fi, VPN) and rapid request patterns are commonly flagged by automated systems.
- Persistent technical misconfigurations—such as disabled JavaScript, missing cookies, or certain browser extensions—can cause detection and blocking.
- Malware or background automated scripts can generate unintentional traffic that resembles bot behavior.
- Administrators and ISPs can help by ensuring IP reputations are clean; sometimes a router reset changes public IP enough to drop a block.
- Users often receive minimal feedback beyond reference IDs, leading to poor understanding of cause or proper remediation. [Primary Article HTML]