Historial de interrupciones de Intrinio

1. June 24, 2026 at 3:19 PM 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. June 24, 2026 at 4:02 PM UTCinvestigating

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

3. June 24, 2026 at 10:04 PM UTCmonitoring

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

4. June 29, 2026 at 7:30 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. May 14, 2026 at 2:59 PM UTCinvestigating

   We are currently investigating this issue.

2. May 14, 2026 at 5:42 PM UTCresolved

   This incident has been resolved.

1. May 8, 2026 at 3:33 PM 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. April 16, 2026 at 5:30 AM 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. February 24, 2026 at 3:37 PM UTCidentified

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

2. February 24, 2026 at 5:58 PM UTCresolved

   This incident has been resolved.

1. December 3, 2025 at 9:09 PM 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. December 4, 2025 at 9:19 PM UTCresolved

   This incident has been resolved.

1. October 23, 2025 at 2:35 PM UTCidentified

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

2. October 23, 2025 at 5:00 PM UTCmonitoring

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

3. October 23, 2025 at 7:04 PM UTCresolved

   This incident has been resolved.

1. October 20, 2025 at 5:01 PM 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. October 20, 2025 at 11:02 PM UTCresolved

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

1. October 20, 2025 at 4:43 PM 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. October 13, 2025 at 5:32 PM UTCidentified

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

2. October 14, 2025 at 5:16 PM UTCresolved

   This incident has been resolved.

1. August 13, 2025 at 3:13 PM UTCidentified

   The issue can be affecting websocket and rest api access.

2. August 13, 2025 at 4:33 PM UTCmonitoring

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

3. August 13, 2025 at 6:26 PM UTCresolved

   This incident has been resolved.

1. July 17, 2025 at 2:41 PM UTCidentified

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

2. July 18, 2025 at 2:47 PM UTCresolved

   This incident has been resolved.

1. May 12, 2025 at 1:54 PM UTCidentified

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

2. May 12, 2025 at 2:58 PM UTCresolved

   Indices feed has been restored.

3. May 12, 2025 at 3:03 PM UTCpostmortem

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

1. March 11, 2025 at 2:07 AM UTCinvestigating

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

2. March 11, 2025 at 3:59 PM UTCresolved

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

1. January 13, 2025 at 3:00 PM UTCinvestigating

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

2. January 13, 2025 at 4:39 PM 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. January 6, 2025 at 8:05 PM 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. January 7, 2025 at 3:39 PM UTCresolved

   This incident has been resolved.

1. January 6, 2025 at 3:36 PM UTCidentified

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

2. January 6, 2025 at 5:16 PM UTCresolved

   This incident has been resolved.

1. December 23, 2024 at 4:33 PM 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. December 23, 2024 at 5:00 PM UTCmonitoring

   Waiting for IEX to come back online.

3. December 23, 2024 at 5:01 PM UTCmonitoring

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

4. December 24, 2024 at 4:28 PM UTCresolved

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

1. December 15, 2024 at 10:32 PM UTCidentified

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

2. December 17, 2024 at 5:23 PM UTCresolved

   This incident has been resolved.

1. June 10, 2024 at 7:20 PM UTCinvestigating

   We are investigating this issue

2. June 10, 2024 at 8:37 PM UTCmonitoring

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

3. June 10, 2024 at 8:42 PM UTCresolved

   This incident has been resolved.