Historique des pannes de Intrinio

1. 24 juin 2026 à 15:19 UTCinvestigating

   Il y a actuellement un problème de réception des données pour les flux CTA A & CTA B sur le produit SIP 15 minutes différées. UTP fonctionne normalement. Travailler actuellement avec le fournisseur en amont pour résoudre ce problème. Les clients devraient utiliser les prix de CBOE retardés de 15 minutes comme un recul. Toutes les données manquantes seront récupérées.

2. 24 juin 2026 à 16:02 UTCinvestigating

   Les données sur cta a et cta b circulent à nouveau et rattrapent. Toujours en quête de cause profonde.

3. 24 juin 2026 à 22:04 UTCmonitoring

   Un correctif a été mis en place et nous suivons les résultats.

4. 29 juin 2026 à 19:30 UTCresolved

   Cet incident a été résolu.

Traduit automatiquement depuis la mise à jour officielle de l'incident.

1. 14 mai 2026 à 14:59 UTCinvestigating

   We are currently investigating this issue.

2. 14 mai 2026 à 17:42 UTCresolved

   This incident has been resolved.

1. 8 mai 2026 à 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 avril 2026 à 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 février 2026 à 15:37 UTCidentified

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

2. 24 février 2026 à 17:58 UTCresolved

   This incident has been resolved.

1. 3 décembre 2025 à 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 décembre 2025 à 21:19 UTCresolved

   This incident has been resolved.

1. 23 octobre 2025 à 14:35 UTCidentified

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

2. 23 octobre 2025 à 17:00 UTCmonitoring

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

3. 23 octobre 2025 à 19:04 UTCresolved

   This incident has been resolved.

1. 20 octobre 2025 à 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 octobre 2025 à 23:02 UTCresolved

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

1. 20 octobre 2025 à 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 octobre 2025 à 17:32 UTCidentified

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

2. 14 octobre 2025 à 17:16 UTCresolved

   This incident has been resolved.

1. 13 août 2025 à 15:13 UTCidentified

   The issue can be affecting websocket and rest api access.

2. 13 août 2025 à 16:33 UTCmonitoring

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

3. 13 août 2025 à 18:26 UTCresolved

   This incident has been resolved.

1. 17 juillet 2025 à 14:41 UTCidentified

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

2. 18 juillet 2025 à 14:47 UTCresolved

   This incident has been resolved.

1. 12 mai 2025 à 13:54 UTCidentified

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

2. 12 mai 2025 à 14:58 UTCresolved

   Indices feed has been restored.

3. 12 mai 2025 à 15:03 UTCpostmortem

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

1. 11 mars 2025 à 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 mars 2025 à 15:59 UTCresolved

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

1. 13 janvier 2025 à 15:00 UTCinvestigating

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

2. 13 janvier 2025 à 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 janvier 2025 à 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 janvier 2025 à 15:39 UTCresolved

   This incident has been resolved.

1. 6 janvier 2025 à 15:36 UTCidentified

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

2. 6 janvier 2025 à 17:16 UTCresolved

   This incident has been resolved.

1. 23 décembre 2024 à 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 décembre 2024 à 17:00 UTCmonitoring

   Waiting for IEX to come back online.

3. 23 décembre 2024 à 17:01 UTCmonitoring

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

4. 24 décembre 2024 à 16:28 UTCresolved

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

1. 15 décembre 2024 à 22:32 UTCidentified

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

2. 17 décembre 2024 à 17:23 UTCresolved

   This incident has been resolved.

1. 10 juin 2024 à 19:20 UTCinvestigating

   We are investigating this issue

2. 10 juin 2024 à 20:37 UTCmonitoring

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

3. 10 juin 2024 à 20:42 UTCresolved

   This incident has been resolved.