Interactive Brokers Outage: Authentication Failures During US Market Hours

Incident Parameters

The discrepancy between user-reported failures and the broker's official system status page — which displayed all systems operational at the time of writing — defines the central technical signature of this event: a partial, regionally-bounded authentication failure that bypassed the standard status monitoring infrastructure.

Confirmed Scope and Resolution

Following publication, an Interactive Brokers spokesperson stated that "a technical issue temporarily prevented a fraction of a percent of Interactive Brokers clients from logging in." The company specified that affected accounts were hosted in certain APAC data centers. Per the statement, a notice appeared on the login screen within minutes of detection, and full access was restored within one hour.

Reported failure modes from social media posts included authentication rejection, inability to reach Trader Workstation, and account access denial. The scope of geographic impact and the specific data center segments responsible were not disclosed.

Context: Broker Platform Failure Frequency

This is not an isolated event. Interactive Brokers experienced a related login disruption in March 2020, when a server issue briefly affected UK and European clients — TWS and the mobile platform were impacted while Client Portal and WebTrader remained accessible. In November 2025, XTB suffered a platform failure that prevented clients from closing positions for several hours. Robinhood has recorded multiple service disruptions during periods of elevated market activity. The pattern: authentication-layer or routing-layer failures that bypass public-facing status dashboards, leaving retail traders with no external confirmation of system health during the failure window.

Separately, attempted AI-powered voice phishing attacks were reported against Citadel, Point72, and Two Sigma on the same date. No link to the IBKR incident has been established.

Operational Checklist for Active Traders

• Verify routing: Confirm which APAC data center hosts the account. IBKR permits data center selection in account management; clients in affected segments should review available failover options.
• Test secondary access paths: Client Portal and WebTrader have demonstrated independent uptime during prior incidents. Maintain working credentials and bookmarks for both.
• Monitor non-status indicators: When the public status page reads green during an active failure window, corroborate with order entry timestamps, mobile app sync status, and real-time market data feeds before assuming platform health.
• Document failure timing: Log exact login attempt timestamps and error messages. Broker SLA claims and any subsequent compensation reviews depend on trader-side timestamp records.
• Pre-stage backup broker access: Given the multi-year pattern of broker outages, a redundant execution venue with funded, tested login credentials is standard infrastructure for scalping and intraday operations.