What this page checks
The API, database and Redis, read from the health endpoint on load and on refresh. Upstream sources, feed imports and your integrations are not covered.
System Status
Checking service health...
Last updated: —
Checks
Service status
streamingChecking service health…
API
Database
Threat data cache
History
Recent incidents
Database connection saturation
resolvedOver 48 hours, a growing share of report lookups could not reach the database as connection demand outgrew the pool. Fixed by routing traffic through a transaction-mode pooler.
Scope
How to read this page
99.9%
Availability target
Monthly API availability is an internal objective, not measured uptime or a contractual SLA.
Incident log
Entries are added by hand and can appear after an incident starts. Integrations should poll the health endpoint and handle failed requests.
Get product updates
Product and platform news by email. Incidents are posted on this page.
Related Blog Posts
Learn more about our infrastructure and best practices.
- API Integration for Threat Intelligence
Best practices for building fault-tolerant security integrations.
- Building a Modern SOC with Threat Intelligence
How to handle rate limits gracefully in your integration.
- Cloud Security Threats and Multi-Cloud Protection
Context for evaluating cloud dependencies and integration requirements.