- Bloomberg may block access with an “unusual activity” CAPTCHA when it flags your network as suspicious.
- Common triggers include rapid requests, automation, VPNs/proxies or shared IPs, and blocked JavaScript/cookies or privacy extensions.
- Fixes typically involve enabling cookies/JavaScript, disabling VPNs/extensions, clearing data, or switching networks.
- The broader tradeoff is protecting content from scraping while avoiding false positives that frustrate legitimate subscribers.
Read More
The HTML you provided is a live example of Bloomberg’s browser-based security block that arises when its backend detects communications from your network deemed “unusual” — triggering a CAPTCHA and a block reference ID requirement. This is designed to prevent data scraping, bot access, or malicious automated behavior that might degrade site performance or compromise content integrity.
Key triggers include: (a) shared public IPs or VPNs or proxy services that are also used by bad actors; (b) use of browser extensions, ad-blockers, incognito or privacy modes that interfere with JavaScript or cookie behavior; (c) high volumes of requests or rapid navigation that could resemble automated scraping or brute-force activity; (d) possibly device-level fingerprinting inconsistencies. These are common trigger points documented in tech support guidance.
Users can usually resolve this by enabling cookies and JavaScript, using clean browser profiles without blocking extensions, avoiding proxies or VPNs, clearing cache, switching to a different network (e.g. from corporate or shared to private or residential), and scanning for malware that may be generating background traffic.
From a strategic perspective for Bloomberg and similar information platforms, this is a tension between safeguarding digital assets and user experience. Overly aggressive blocking can alienate or reduce loyalty among subscribers or institutional users (e.g. banks, investment firms) whose access may be hindered by corporate firewalls, VPN policies, or shared Internet infrastructure. On the other hand, failing to secure content invites scraping, unauthorized redistribution, or bot-driven traffic that can undermine subscription models.
Open questions include: What are the thresholds or heuristics Bloomberg uses to flag “unusual”? Are there false positives affecting legitimate users in certain environments (e.g. financial institutions, academia, large offices)? Does Bloomberg’s paid subscriber base receive different treatment or reduced detection sensitivity? What logging or feedback process exists around block reference IDs for troubleshooting? Is there transparency around how browser fingerprinting or device metrics feed into these decisions?
Supporting Notes
- Bloomberg shows a “We’ve detected unusual activity from your computer network” message, prompting verification via CAPTCHA and use of a block reference ID.
- The instructions include ensuring JavaScript and cookies are enabled and not being blocked.
- Other sources indicate the use of VPNs or shared IP addresses can trigger this warning.
- Browser extensions or privacy tools (ad blockers, disabling cookies/JS, incognito mode) have been repeatedly identified as causes of such blocks.
- Clearing browser cache or switching networks are common methods to resolve this.
- Some users report false positives and recurring blocks even without using automation or VPNs, especially when in incognito/private browser windows or behind shared institutional infrastructure.