Istoricul incidentelor Intrinio

1. 24 iunie 2026 la 15:19 UTCinvestigating

   În prezent, există o problemă care primește date pentru furajele CTA A & CTA B privind produsul SIP întârziat la 15 minute. UTP funcționează normal. În prezent lucrează cu furnizorul din amonte pentru a rezolva acest lucru. Clienții ar trebui să utilizeze 15 Minute Delayed CBOE tarifare ca o rezervă. Toate datele lipsă vor fi completate.

2. 24 iunie 2026 la 16:02 UTCinvestigating

   Datele despre cita a și cta b curge din nou și recuperează. Încă investighează cauza principală.

3. 24 iunie 2026 la 22:04 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 29 iunie 2026 la 19:30 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 14 mai 2026 la 14:59 UTCinvestigating

   We are currently investigating this issue.

2. 14 mai 2026 la 17:42 UTCresolved

   This incident has been resolved.

1. 8 mai 2026 la 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 aprilie 2026 la 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 februarie 2026 la 15:37 UTCidentified

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

2. 24 februarie 2026 la 17:58 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 23 octombrie 2025 la 14:35 UTCidentified

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

2. 23 octombrie 2025 la 17:00 UTCmonitoring

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

3. 23 octombrie 2025 la 19:04 UTCresolved

   This incident has been resolved.

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

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

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

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

2. 14 octombrie 2025 la 17:16 UTCresolved

   This incident has been resolved.

1. 13 august 2025 la 15:13 UTCidentified

   The issue can be affecting websocket and rest api access.

2. 13 august 2025 la 16:33 UTCmonitoring

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

3. 13 august 2025 la 18:26 UTCresolved

   This incident has been resolved.

1. 17 iulie 2025 la 14:41 UTCidentified

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

2. 18 iulie 2025 la 14:47 UTCresolved

   This incident has been resolved.

1. 12 mai 2025 la 13:54 UTCidentified

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

2. 12 mai 2025 la 14:58 UTCresolved

   Indices feed has been restored.

3. 12 mai 2025 la 15:03 UTCpostmortem

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

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

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

1. 13 ianuarie 2025 la 15:00 UTCinvestigating

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

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

   This incident has been resolved.

1. 6 ianuarie 2025 la 15:36 UTCidentified

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

2. 6 ianuarie 2025 la 17:16 UTCresolved

   This incident has been resolved.

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

   Waiting for IEX to come back online.

3. 23 decembrie 2024 la 17:01 UTCmonitoring

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

4. 24 decembrie 2024 la 16:28 UTCresolved

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

1. 15 decembrie 2024 la 22:32 UTCidentified

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

2. 17 decembrie 2024 la 17:23 UTCresolved

   This incident has been resolved.

1. 10 iunie 2024 la 19:20 UTCinvestigating

   We are investigating this issue

2. 10 iunie 2024 la 20:37 UTCmonitoring

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

3. 10 iunie 2024 la 20:42 UTCresolved

   This incident has been resolved.