Greynoise 中断历史

1. 2026年10月28日 UTC 01:47identified

   我们的数据处理因数据管道退化而出现延误。 数据处理将暂时暂停,以便对已退化的数据储存进行补救。 数据摄取没有受到影响。 从事故窗口收到的数据将在我们恢复数据处理管道后处理。 会话探索器正面临较高的出错率. 会话数据,IP智能和批量数据被延迟.

2. 2026年10月28日 UTC 02:49monitoring

   数据库退化的原因已经得到补救。 我们正在重新开始数据处理和监测恢复情况.

3. 2026年10月28日 UTC 03:18monitoring

   散装数据重放正在运行中 。 所有其他系统都已开始运作.

4. 2026年10月28日 UTC 04:09resolved

   批量数据新鲜度被恢复 。 所有系统正常运行.

自动翻译自官方事件更新。

1. 2026年10月9日 UTC 00:51identified

   我们发现一个问题,从协调世界时20:50开始进行大宗数据处理。 工作队正在恢复大宗数据处理服务,并将在补救后重放所缺时间.

2. 2026年10月9日 UTC 01:22monitoring

   批量数据处理任务再次运行. 数据回填将很快开始 .

3. 2026年10月9日 UTC 01:43resolved

   所有批量数据都已恢复.

自动翻译自官方事件更新。

1. 2026年9月14日 UTC 14:11identified

   第三方应享待遇服务提供者服务中断,导致整个系统停用。 我们正在研究解决的内部系统补丁.

2. 2026年9月14日 UTC 14:16monitoring

   第三方供应商问题已经解决。 我们正在监测,以确保不再出现业绩退化.

3. 2026年9月14日 UTC 14:33resolved

   所有系统恢复在线.

自动翻译自官方事件更新。

1. 2026年9月13日 UTC 17:37identified

   会话探索器在处理包时出现延迟 。 多达1%的包可能会受到这种拖延的影响。 未来几天, 数据没有丢失,只是没有以这种典型的方式及时处理.

2. 2026年9月14日 UTC 07:58resolved

   延迟问题已经得到解决;所有数据包现在都正常处理.

自动翻译自官方事件更新。

1. 2026年8月7日 UTC 15:51identified

   Our API is currently offline; we are investigating the cause and resolution.

2. 2026年8月7日 UTC 16:55resolved

   The issue was tracked down to DoS-level traffic to our API. We’ve temporarily suspended the accounts generating that traffic, and will be implementing stricter rate limiting of API calls to prevent future occurrences.

1. 2026年6月16日 UTC 01:04identified

   We are experiencing delays in data processing impacting delivery of session, finished intelligence, and bulk data sets. Fixes are being applied to restore processing performance and burn down the backlog.

2. 2026年6月16日 UTC 03:06identified

   We're continuing to work on fixes for data processing. We expect to begin working through the backlog within the hour.

3. 2026年6月16日 UTC 03:41monitoring

   We are starting backlog processing. Following restoration of data availability for impacted hours, we will export impacted bulk data hourly buckets.

4. 2026年6月16日 UTC 04:59monitoring

   Data backlog processing is continuing as expected. We'll update the status page when we are fully caught up and bulk data exports are started.

5. 2026年6月16日 UTC 07:11resolved

   Data backlog processing has completed and bulk data exports are available.

1. 2026年4月15日 UTC 17:46identified

   We are aware of an issue causing some requests to the IP Details Page to fail.

2. 2026年4月15日 UTC 17:54monitoring

   We have rolled back the change that resulted in these errors. We are monitoring recovery

3. 2026年4月15日 UTC 21:12resolved

   We have confirmed resolution of the issue that led to the errors.

1. 2026年3月10日 UTC 16:00investigating

   We are investigating an issue that is causing requests in the Visualizer to fail across most accounts.

2. 2026年3月10日 UTC 16:07identified

   We are rolling back the change that is causing errors in the Visualizer.

3. 2026年3月10日 UTC 16:10monitoring

   The rollback is complete, and Visualizer requests are successfully completing. We are monitoring the resolution.

4. 2026年3月10日 UTC 16:19resolved

   The Visualizer is fully operational.

1. 2026年3月4日 UTC 23:24identified

   We are experiencing delays in our data processing pipeline. This is impacting the recency of data available via our API and the availability of bulk data files.

2. 2026年3月5日 UTC 00:33identified

   We are continuing to work on restoration of pipeline operations.

3. 2026年3月5日 UTC 02:58identified

   The team is continuing to work on recovery.

4. 2026年3月5日 UTC 03:56monitoring

   We are seeing recovery in our data processing pipeline. The team is monitoring recovery. Missing bulk data files will be generated as we catch up on the backlog.

5. 2026年3月5日 UTC 06:28monitoring

   Backlog reprocessing is continuing and expected rates. The team will process missing bulk data files at ~8AM ET.

6. 2026年3月5日 UTC 16:39resolved

   Bulk data file processing is complete for all impacted hours and pipeline data delivery is stable.

1. 2026年2月26日 UTC 16:59investigating

   We're seeing substantial delays in the handling of inbound packets and are investigating the cause.

2. 2026年2月26日 UTC 17:34identified

   The cause of data processing delays has been identified and remediated. The platform is working through the data backlog. Bulk data files will be updated as data for impacted hours is processed.

3. 2026年2月26日 UTC 18:34identified

   Pipeline performance is still showing signs of degradation. Data is backfilling but at slower than optimal rates. The team is continuing to identify and address performance issues.

4. 2026年2月26日 UTC 20:33identified

   The team is continuing to work on improving processing performance. Data is still delayed, but the pipeline is gradually making progress toward catching up.

5. 2026年2月26日 UTC 22:07identified

   At our current processing pace we expect to be through the backlog in roughly 12 hours, including backfill of bulk data. We will update the incident periodically as we monitor and work on improvements to processing performance.

6. 2026年2月26日 UTC 23:35monitoring

   We have released upgrades to a key part of our pipeline that has improved data processing speed. Our estimated time to recovery is now two hours. Data from ~5 hours ago is still being processed. We are starting bulk data jobs to publish for hours that have already completed backfill.

7. 2026年2月27日 UTC 00:44monitoring

   Bulk data for 2026-02-26_1400 - 2026-02-26_1600 hours are available.

8. 2026年2月27日 UTC 00:50monitoring

   Bulk data for 2026-02-26_1700 - 2026-02-26_1900 hours are available.

9. 2026年2月27日 UTC 01:15monitoring

   Bulk data for 2026-02-26_2000 - 2026-02-26_2200 hours are available.

10. 2026年2月27日 UTC 01:32resolved

    Data backfill is complete. All bulk data hours are available.

1. 2026年2月25日 UTC 04:55identified

   API and Bulk Data sources are impacted by delays in data processing. We are monitoring the situation and taking corrective actions to catch up on the backlog

2. 2026年2月25日 UTC 06:01identified

   We are continuing to monitor recovery. Data processing is still delayed.

3. 2026年2月25日 UTC 06:20monitoring

   We are seeing recovery in data processing rates. At the current pace of recovery we expect normal operations and data backfill to be complete in roughly 4.5hrs. Our team will backfill bulk data as hourly windows finish catching up.

4. 2026年2月25日 UTC 07:00monitoring

   We are continuing to monitor recovery. Data processing rates have remained consistent with prior measurements. The team expects to backfill bulk data around 8AM ET.

5. 2026年2月25日 UTC 12:41monitoring

   Backfill jobs for bulk data have started for hours 00-07 UTC.

6. 2026年2月25日 UTC 15:03monitoring

   Data backfill for bulk data is continuing to process.

7. 2026年2月25日 UTC 15:06resolved

   Bulk data backfill is complete. Overall platform data processing is performance is restored.

1. 2026年1月8日 UTC 20:53investigating

   New logins to the Visualizer are not working. Existing sessions remain active.

2. 2026年1月8日 UTC 21:24identified

   We are working on rollback of infrastructure changes that are causing logins to fail.

3. 2026年1月8日 UTC 21:57monitoring

   Logins are working again. We are monitoring recovery.

4. 2026年1月8日 UTC 22:10resolved

   The issue with Visualizer logins is resolved.

1. 2025年12月11日 UTC 10:54identified

   - Greynoise Bulk data delay - API Data freshness degraded

2. 2025年12月11日 UTC 17:59resolved

   Our data service has been restored to real time.

1. 2025年10月29日 UTC 13:57investigating

   1 hour behind on processing bulk data

2. 2025年10月29日 UTC 14:30resolved

   Bulk data processing has caught up

1. 2025年10月20日 UTC 13:35identified

   We are experiencing occasional service disruptions across our platform as a result of AWS issues.

2. 2025年10月20日 UTC 20:00identified

   We're continuing to monitor AWS status and impacts.

3. 2025年10月21日 UTC 00:11resolved

   AWS has recovered from their outage. GreyNoise services are fully operational. Greynoise sensor data from during the outage window has been processed.

1. 2025年10月9日 UTC 14:33identified

   GreyNoise Tags are not loading in the GreyNoise API. This is impacting most Visualizer pages and some API endpoints.

2. 2025年10月9日 UTC 14:56monitoring

   The GreyNoise API is recovering and calls for tags are succeeding. We are monitoring recovery.

3. 2025年10月9日 UTC 15:02resolved

   The GreyNoise API is fully operational.

1. 2025年7月28日 UTC 22:27investigating

   The GreyNoise Visualizer (viz.greynoise.io) is currently down; the team is investigating.

2. 2025年7月28日 UTC 22:43monitoring

   We have reverted the Visualizer to a prior version and are monitoring the service.

3. 2025年7月28日 UTC 23:15resolved

   The Visualizer is stable.

1. 2025年6月3日 UTC 16:41identified

   The GreyNoise website (https://greynoise.io) is experiencing intermittent availability issues due to an issue with our third-party hosting provider.

2. 2025年6月3日 UTC 21:41resolved

   The issue appears to have been resolved and the website is fully operational again.

1. 2025年5月16日 UTC 17:13investigating

   The observed IP counts in our Vulnerability Prioritization Intelligence product are not accurate. We are investigating the cause.

2. 2025年5月16日 UTC 19:08resolved

   The incident is resolved and the underlying service code has been updated.

1. 2025年5月11日 UTC 20:54identified

   Calls for some blocklist tags are failing to return IP addresses.

2. 2025年5月11日 UTC 21:27identified

   Tag blocklist API calls are successfully returning IP addresses. We are working to restore data recency back to the current hour.

3. 2025年5月11日 UTC 21:40monitoring

   Data processing is recovering. The platform is working through the backlog of data. We will resolve the incident once backlog processing is complete.

4. 2025年5月11日 UTC 23:06monitoring

   Data recency is continue to recover. Hours from 19:00 UTC on will be reprocessed following recovery to ensure completeness.

5. 2025年5月12日 UTC 01:05resolved

   Data reprocessing is complete. All systems are operational.