Intrinio の障害履歴

1. 2026年6月24日 15:19 UTCinvestigating

   現在、CTA A および CTA B フィードのデータを 15 分の遅延 SIP 製品で受け取る問題があります。 UTPは正常に動作しています。 現時点では、上流プロバイダーと連携して解決します。 顧客は、15分遅れたCBOEの価格設定をフォールバックとして使用する必要があります。 すべての欠落したデータは、埋め戻されます.

2. 2026年6月24日 16:02 UTCinvestigating

   Cta a と cta b のデータが再び流れ、キャッチアップします。 それでも根本原因を調べる.

3. 2026年6月24日 22:04 UTCmonitoring

   修正を実装し、結果を監視しています.

4. 2026年6月29日 19:30 UTCresolved

   この事件は解決しました.

公式のインシデント更新を自動翻訳しています。

1. 2026年5月14日 14:59 UTCinvestigating

   We are currently investigating this issue.

2. 2026年5月14日 17:42 UTCresolved

   This incident has been resolved.

1. 2026年5月8日 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. 2026年4月16日 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. 2026年2月24日 15:37 UTCidentified

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

2. 2026年2月24日 17:58 UTCresolved

   This incident has been resolved.

1. 2025年12月3日 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. 2025年12月4日 21:19 UTCresolved

   This incident has been resolved.

1. 2025年10月23日 14:35 UTCidentified

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

2. 2025年10月23日 17:00 UTCmonitoring

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

3. 2025年10月23日 19:04 UTCresolved

   This incident has been resolved.

1. 2025年10月20日 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. 2025年10月20日 23:02 UTCresolved

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

1. 2025年10月20日 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. 2025年10月13日 17:32 UTCidentified

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

2. 2025年10月14日 17:16 UTCresolved

   This incident has been resolved.

1. 2025年8月13日 15:13 UTCidentified

   The issue can be affecting websocket and rest api access.

2. 2025年8月13日 16:33 UTCmonitoring

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

3. 2025年8月13日 18:26 UTCresolved

   This incident has been resolved.

1. 2025年7月17日 14:41 UTCidentified

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

2. 2025年7月18日 14:47 UTCresolved

   This incident has been resolved.

1. 2025年5月12日 13:54 UTCidentified

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

2. 2025年5月12日 14:58 UTCresolved

   Indices feed has been restored.

3. 2025年5月12日 15:03 UTCpostmortem

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

1. 2025年3月11日 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. 2025年3月11日 15:59 UTCresolved

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

1. 2025年1月13日 15:00 UTCinvestigating

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

2. 2025年1月13日 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. 2025年1月6日 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. 2025年1月7日 15:39 UTCresolved

   This incident has been resolved.

1. 2025年1月6日 15:36 UTCidentified

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

2. 2025年1月6日 17:16 UTCresolved

   This incident has been resolved.

1. 2024年12月23日 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. 2024年12月23日 17:00 UTCmonitoring

   Waiting for IEX to come back online.

3. 2024年12月23日 17:01 UTCmonitoring

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

4. 2024年12月24日 16:28 UTCresolved

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

1. 2024年12月15日 22:32 UTCidentified

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

2. 2024年12月17日 17:23 UTCresolved

   This incident has been resolved.

1. 2024年6月10日 19:20 UTCinvestigating

   We are investigating this issue

2. 2024年6月10日 20:37 UTCmonitoring

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

3. 2024年6月10日 20:42 UTCresolved

   This incident has been resolved.