Historial de interrupciones de Intrinio

1. 24 de junio de 2026 a las 15:19 UTCinvestigating

   Actualmente hay un problema que recibe datos para el CTA A " CTA B alimenta el producto SIP de 15 minutos. UTP está operando normalmente. Actualmente trabaja con el proveedor de corriente para resolver esto. Los clientes deben utilizar 15 minutos de retraso de precios CBOE como retroceso. Todos los datos perdidos serán recubiertos.

2. 24 de junio de 2026 a las 16:02 UTCinvestigating

   Data on cta a and cta b is flowing again and catching up. Sigue investigando la causa raíz.

3. 24 de junio de 2026 a las 22:04 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 29 de junio de 2026 a las 19:30 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de mayo de 2026 a las 14:59 UTCinvestigating

   We are currently investigating this issue.

2. 14 de mayo de 2026 a las 17:42 UTCresolved

   This incident has been resolved.

1. 8 de mayo de 2026 a las 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 de abril de 2026 a las 5: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 de febrero de 2026 a las 15:37 UTCidentified

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

2. 24 de febrero de 2026 a las 17:58 UTCresolved

   This incident has been resolved.

1. 3 de diciembre de 2025 a las 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 de diciembre de 2025 a las 21:19 UTCresolved

   This incident has been resolved.

1. 23 de octubre de 2025 a las 14:35 UTCidentified

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

2. 23 de octubre de 2025 a las 17:00 UTCmonitoring

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

3. 23 de octubre de 2025 a las 19:04 UTCresolved

   This incident has been resolved.

1. 20 de octubre de 2025 a las 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 de octubre de 2025 a las 23:02 UTCresolved

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

1. 20 de octubre de 2025 a las 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 de octubre de 2025 a las 17:32 UTCidentified

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

2. 14 de octubre de 2025 a las 17:16 UTCresolved

   This incident has been resolved.

1. 13 de agosto de 2025 a las 15:13 UTCidentified

   The issue can be affecting websocket and rest api access.

2. 13 de agosto de 2025 a las 16:33 UTCmonitoring

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

3. 13 de agosto de 2025 a las 18:26 UTCresolved

   This incident has been resolved.

1. 17 de julio de 2025 a las 14:41 UTCidentified

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

2. 18 de julio de 2025 a las 14:47 UTCresolved

   This incident has been resolved.

1. 12 de mayo de 2025 a las 13:54 UTCidentified

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

2. 12 de mayo de 2025 a las 14:58 UTCresolved

   Indices feed has been restored.

3. 12 de mayo de 2025 a las 15:03 UTCpostmortem

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

1. 11 de marzo de 2025 a las 2: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 de marzo de 2025 a las 15:59 UTCresolved

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

1. 13 de enero de 2025 a las 15:00 UTCinvestigating

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

2. 13 de enero de 2025 a las 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 de enero de 2025 a las 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 de enero de 2025 a las 15:39 UTCresolved

   This incident has been resolved.

1. 6 de enero de 2025 a las 15:36 UTCidentified

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

2. 6 de enero de 2025 a las 17:16 UTCresolved

   This incident has been resolved.

1. 23 de diciembre de 2024 a las 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 de diciembre de 2024 a las 17:00 UTCmonitoring

   Waiting for IEX to come back online.

3. 23 de diciembre de 2024 a las 17:01 UTCmonitoring

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

4. 24 de diciembre de 2024 a las 16:28 UTCresolved

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

1. 15 de diciembre de 2024 a las 22:32 UTCidentified

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

2. 17 de diciembre de 2024 a las 17:23 UTCresolved

   This incident has been resolved.

1. 10 de junio de 2024 a las 19:20 UTCinvestigating

   We are investigating this issue

2. 10 de junio de 2024 a las 20:37 UTCmonitoring

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

3. 10 de junio de 2024 a las 20:42 UTCresolved

   This incident has been resolved.