Störungsverlauf von Intrinio

1. 24. Juni 2026 um 15:19 UTCinvestigating

   Es gibt derzeit ein Problem beim Empfang von Daten für die CTA A & CTA B-Feeds für das 15-Minuten-verspätete SIP-Produkt. UTP funktioniert normal. Derzeit arbeitet er mit dem Upstream-Anbieter zusammen, um dies zu lösen. Kunden sollten 15 Minuten verzögerte CBOE-Preise als Fallback verwenden. Alle fehlenden Daten werden hinterlegt.

2. 24. Juni 2026 um 16:02 UTCinvestigating

   Die Daten zu cta a und cta b fließen wieder und holen auf. Immer noch die Ursachen untersuchen.

3. 24. Juni 2026 um 22:04 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 29. Juni 2026 um 19:30 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 14. Mai 2026 um 14:59 UTCinvestigating

   We are currently investigating this issue.

2. 14. Mai 2026 um 17:42 UTCresolved

   This incident has been resolved.

1. 8. Mai 2026 um 15:33 UTCresolved

   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.

1. 16. April 2026 um 05:30 UTCresolved

   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.

1. 24. Februar 2026 um 15:37 UTCidentified

   We are working on an issue stemming from a change at our upstream provider.

2. 24. Februar 2026 um 17:58 UTCresolved

   This incident has been resolved.

1. 3. Dezember 2025 um 21:09 UTCidentified

   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.

2. 4. Dezember 2025 um 21:19 UTCresolved

   This incident has been resolved.

1. 23. Oktober 2025 um 14:35 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 23. Oktober 2025 um 17:00 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 23. Oktober 2025 um 19:04 UTCresolved

   This incident has been resolved.

1. 20. Oktober 2025 um 17:01 UTCmonitoring

   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)

2. 20. Oktober 2025 um 23:02 UTCresolved

   The AWS issue was resolved as of 6:53pmEST. https://health.aws.amazon.com/health/status

1. 20. Oktober 2025 um 16:43 UTCresolved

   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/

1. 13. Oktober 2025 um 17:32 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 14. Oktober 2025 um 17:16 UTCresolved

   This incident has been resolved.

1. 13. August 2025 um 15:13 UTCidentified

   The issue can be affecting websocket and rest api access.

2. 13. August 2025 um 16:33 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 13. August 2025 um 18:26 UTCresolved

   This incident has been resolved.

1. 17. Juli 2025 um 14:41 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 18. Juli 2025 um 14:47 UTCresolved

   This incident has been resolved.

1. 12. Mai 2025 um 13:54 UTCidentified

   The issue has been identified and a fix is being implemented.

2. 12. Mai 2025 um 14:58 UTCresolved

   Indices feed has been restored.

3. 12. Mai 2025 um 15:03 UTCpostmortem

   A network outage caused degraded service. This outage has been resolved.

1. 11. März 2025 um 02:07 UTCinvestigating

   EOD stock prices have been delayed from our source. We are working with our provider to get this data deliver ASAP.

2. 11. März 2025 um 15:59 UTCresolved

   We've received processed all US prices from March 10th.

1. 13. Januar 2025 um 15:00 UTCinvestigating

   We are investigating this issue that is affecting API and websocket users.

2. 13. Januar 2025 um 16:39 UTCresolved

   This incident is now resolved and data is flowing. We are waiting for an update on the post mortem from the upstream provider.

1. 6. Januar 2025 um 20:05 UTCidentified

   We are experiencing brown outs with one of our cloud providers. We are working with them on recovery and simultaneously moving components other providers

2. 7. Januar 2025 um 15:39 UTCresolved

   This incident has been resolved.

1. 6. Januar 2025 um 15:36 UTCidentified

   We identified an issue with the Quote endpoint and are working on a fix.

2. 6. Januar 2025 um 17:16 UTCresolved

   This incident has been resolved.

1. 23. Dezember 2024 um 16:33 UTCidentified

   IEX Exchange has encountered an issue and stopped all trading IEX. They are in the process of trying to come back online. See updates from https://iextrading.com/status/#/

2. 23. Dezember 2024 um 17:00 UTCmonitoring

   Waiting for IEX to come back online.

3. 23. Dezember 2024 um 17:01 UTCmonitoring

   Correction. We are waiting for IEX to bring their trading system back online.

4. 24. Dezember 2024 um 16:28 UTCresolved

   This has been resolved. Awaiting a postmortem from IEX. https://iextrading.com/status/#/

1. 15. Dezember 2024 um 22:32 UTCidentified

   We are investigating reported error messages such as for api key, reached limits, etc.

2. 17. Dezember 2024 um 17:23 UTCresolved

   This incident has been resolved.

1. 10. Juni 2024 um 19:20 UTCinvestigating

   We are investigating this issue

2. 10. Juni 2024 um 20:37 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 10. Juni 2024 um 20:42 UTCresolved

   This incident has been resolved.