Histórico de interrupções do Intrinio

1. 24 Mezheven 2026 da 15:19 UTCinvestigating

   Atualmente há um problema recebendo dados para os feeds CTA A & CTA B do produto SIP de 15 minutos atrasado. O UTP está a funcionar normalmente. Atualmente trabalhando com o provedor upstream para resolver isso. Os clientes devem usar 15 minutos de atraso no preço do CBOE como um retrocesso. Todos os dados em falta serão preenchidos.

2. 24 Mezheven 2026 da 16:02 UTCinvestigating

   Dados sobre cta a e cta b estão fluindo novamente e alcançando. Ainda a investigar a causa da raiz.

3. 24 Mezheven 2026 da 22:04 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 29 Mezheven 2026 da 19:30 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Mae 2026 da 14:59 UTCinvestigating

   We are currently investigating this issue.

2. 14 Mae 2026 da 17:42 UTCresolved

   This incident has been resolved.

1. 8 Mae 2026 da 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 Ebrel 2026 da 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 Cʼhwevrer 2026 da 15:37 UTCidentified

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

2. 24 Cʼhwevrer 2026 da 17:58 UTCresolved

   This incident has been resolved.

1. 3 Kerzu 2025 da 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 Kerzu 2025 da 21:19 UTCresolved

   This incident has been resolved.

1. 23 Here 2025 da 14:35 UTCidentified

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

2. 23 Here 2025 da 17:00 UTCmonitoring

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

3. 23 Here 2025 da 19:04 UTCresolved

   This incident has been resolved.

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

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

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

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

2. 14 Here 2025 da 17:16 UTCresolved

   This incident has been resolved.

1. 13 Eost 2025 da 15:13 UTCidentified

   The issue can be affecting websocket and rest api access.

2. 13 Eost 2025 da 16:33 UTCmonitoring

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

3. 13 Eost 2025 da 18:26 UTCresolved

   This incident has been resolved.

1. 17 Gouere 2025 da 14:41 UTCidentified

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

2. 18 Gouere 2025 da 14:47 UTCresolved

   This incident has been resolved.

1. 12 Mae 2025 da 13:54 UTCidentified

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

2. 12 Mae 2025 da 14:58 UTCresolved

   Indices feed has been restored.

3. 12 Mae 2025 da 15:03 UTCpostmortem

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

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

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

1. 13 Genver 2025 da 15:00 UTCinvestigating

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

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

   This incident has been resolved.

1. 6 Genver 2025 da 15:36 UTCidentified

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

2. 6 Genver 2025 da 17:16 UTCresolved

   This incident has been resolved.

1. 23 Kerzu 2024 da 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 Kerzu 2024 da 17:00 UTCmonitoring

   Waiting for IEX to come back online.

3. 23 Kerzu 2024 da 17:01 UTCmonitoring

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

4. 24 Kerzu 2024 da 16:28 UTCresolved

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

1. 15 Kerzu 2024 da 22:32 UTCidentified

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

2. 17 Kerzu 2024 da 17:23 UTCresolved

   This incident has been resolved.

1. 10 Mezheven 2024 da 19:20 UTCinvestigating

   We are investigating this issue

2. 10 Mezheven 2024 da 20:37 UTCmonitoring

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

3. 10 Mezheven 2024 da 20:42 UTCresolved

   This incident has been resolved.