Options Feed
Timeline · 2 updates
- investigating May 14, 2026, 02:59 PM UTC
We are currently investigating this issue.
- resolved May 14, 2026, 05:42 PM UTC
This incident has been resolved.
Intrinio had 10 outages in the last 2 years totaling 90h 47m of downtime — averaging 0.4 incidents per month.
There were 10 Intrinio outages since July 17, 2025 totaling 90h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are currently investigating this issue.
This incident has been resolved.
Due to failed servers in AWS, some IEX and Equities EDGE points are missing data from this morning. Websockets and other data streams were not affected. Data backfill is in process. File a ticket if you need assistance with a backfill.
Intrinio APIv2 received extreme and increasing traffic today which resulted in degraded service. Additional hardware as well as improved scaling and improved firewall rules were required to stabilize. We are continuing to monitor the situation.
We are working on an issue stemming from a change at our upstream provider.
This incident has been resolved.
Reports of issues with upstream Kafka server having issues, not responding, and making us reconnect often. If you are experiencing any issues with Nasdaq Basic, this is the likely cause. We are actively working to resolve the issue.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
AWS issues and outage are affecting our data feeds and some users are still experiencing delays. We continue monitoring the situation and most feeds are performing as expected. If you are encountering data delay or issue, please file a ticket and our dev team will follow up asap. https://account.intrinio.com/account/tickets/ AWS STATUS PAGE (https://health.aws.amazon.com/health/status)
The AWS issue was resolved as of 6:53pmEST. https://health.aws.amazon.com/health/status
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The issue can be affecting websocket and rest api access.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.