All Systems Operational
Bigdata APP
Operational
Android App
Operational
Document Storage (Private Content)
Operational
iOS App
Operational
Research Agent
Operational
Watchlists
Operational
Web Application
Operational
Workflows
Operational
Bigdata API
Operational
Data Connectors
Operational
Document Processing API
Operational
Knowledge Graph API
Operational
Research Agent API
Operational
Search API
Operational
Structured Data API
Operational
Widgets
Operational
Workflows
Operational
Bigdata News Content
Operational
Corporate Communications
Operational
Corporate Financials
Operational
ESG Scores
Operational
Expert Networks
Operational
Factset Intelligence
Operational
Factset Transcripts
Operational
Financial Newswires
Operational
Financial Times
Operational
Fund Holdings
Operational
International Filings
Operational
Investment Research
Operational
MT Newswires
Operational
Podcasts
Operational
Public Web
Operational
Preqin
Operational
Quartr
Operational
S&P Global Filings & Transcripts
Operational
SEC Filings
Operational
Developer Tools & Integration
Operational
API Usage
Operational
Authentication Provider
Operational
Developer Platform & Playgrounds
Operational
MCP (Model Context Protocol)
Operational
Python SDK
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Bigdata.com - New Rate Limits Nov 16, 2026 10:00-11:00 UTC
To enhance platform stability, optimize performance, and ensure consistent service quality for all users, Bigdata.com will introduce official rate limits on our public search services starting Monday, November 16th, 2026.
To prevent disruptions to your workflows and integrations, please have your engineering or technical team implement the following practices prior to November 16th:
- Handle HTTP 429 Status Codes: Ensure your client applications gracefully catch 429 responses rather than failing silently or crashing downstream processes.
- Respect Retry-After Headers: Responses returning status code 429 will include a Retry-After HTTP header specifying the backoff duration. Your systems should wait for the designated interval before attempting another request.
- Implement Exponential Backoff & Jitter: Incorporating an exponential backoff strategy with randomized jitter for retry loops will help smooth out traffic spikes and minimize rejected calls.
If you have questions about specific limit thresholds, integration best practices, or need assistance reviewing your current traffic volumes, please contact our support team at [support@bigdata.com] or reach out directly to your account representative.
Posted on Nov 06, 2026 - 10:19 UTC
To prevent disruptions to your workflows and integrations, please have your engineering or technical team implement the following practices prior to November 16th:
- Handle HTTP 429 Status Codes: Ensure your client applications gracefully catch 429 responses rather than failing silently or crashing downstream processes.
- Respect Retry-After Headers: Responses returning status code 429 will include a Retry-After HTTP header specifying the backoff duration. Your systems should wait for the designated interval before attempting another request.
- Implement Exponential Backoff & Jitter: Incorporating an exponential backoff strategy with randomized jitter for retry loops will help smooth out traffic spikes and minimize rejected calls.
If you have questions about specific limit thresholds, integration best practices, or need assistance reviewing your current traffic volumes, please contact our support team at [support@bigdata.com] or reach out directly to your account representative.
Posted on Nov 06, 2026 - 10:19 UTC