Histórico de interrupções do Greynoise

1. 28 Here 2026 da 01:47 UTCidentified

   Estamos passando por um atraso no processamento de dados devido à degradação em nosso pipeline de dados. O processamento de dados será temporariamente pausado para realizar a remediação nas lojas de dados degradadas. A ingestão de dados não é afetada. Os dados recebidos da janela de incidente serão processados após a restauração do nosso gasoduto de processamento de dados. O Session Explorer está tendo taxas de erro elevadas. Dados de sessão, IP Intelligence e dados em massa estão atrasados.

2. 28 Here 2026 da 02:49 UTCmonitoring

   A causa da degradação do armazenamento de dados foi remediada. Estamos reiniciando o processamento de dados e monitorando a recuperação.

3. 28 Here 2026 da 03:18 UTCmonitoring

   Replay de dados em massa está sendo executado por horas impactadas. Todos os outros sistemas estão operacionais.

4. 28 Here 2026 da 04:09 UTCresolved

   A frescura dos dados em massa é restaurada. Todos os sistemas operacionais.

Traduzido automaticamente da atualização oficial do incidente.

1. 9 Here 2026 da 00:51 UTCidentified

   Identificamos um problema com o processamento de dados em massa a partir de ~20:50 UTC. A equipe está restaurando os serviços de processamento de dados em massa e irá repetir as horas perdidas após a remediação.

2. 9 Here 2026 da 01:22 UTCmonitoring

   Os trabalhos de processamento de dados em massa estão em execução novamente. O preenchimento dos dados começará em breve.

3. 9 Here 2026 da 01:43 UTCresolved

   Todos os dados em massa foram restaurados.

Traduzido automaticamente da atualização oficial do incidente.

1. 14 Gwengolo 2026 da 14:11 UTCidentified

   Um terceiro prestador de serviços para direitos está fora, causando uma falha completa do sistema. Estamos a trabalhar num sistema interno para resolver.

2. 14 Gwengolo 2026 da 14:16 UTCmonitoring

   A questão do fornecedor de terceiros foi resolvida. Estamos monitorando para não garantir mais degradação de desempenho.

3. 14 Gwengolo 2026 da 14:33 UTCresolved

   Todos os sistemas voltaram a funcionar.

Traduzido automaticamente da atualização oficial do incidente.

1. 13 Gwengolo 2026 da 17:37 UTCidentified

   O explorador de sessões está tendo um atraso no processamento de pacotes. Até 1% dos pacotes podem ser afetados por este atraso. Identificamos a questão e trabalharemos para resolver nos próximos dias. Nenhum dado é perdido, apenas não é processado desta forma oportuna como típico.

2. 14 Gwengolo 2026 da 07:58 UTCresolved

   O atraso foi resolvido; todos os pacotes estão sendo processados como normal.

Traduzido automaticamente da atualização oficial do incidente.

1. 7 Eost 2026 da 15:51 UTCidentified

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

2. 7 Eost 2026 da 16:55 UTCresolved

   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. 16 Mezheven 2026 da 01:04 UTCidentified

   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. 16 Mezheven 2026 da 03:06 UTCidentified

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

3. 16 Mezheven 2026 da 03:41 UTCmonitoring

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

4. 16 Mezheven 2026 da 04:59 UTCmonitoring

   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. 16 Mezheven 2026 da 07:11 UTCresolved

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

1. 15 Ebrel 2026 da 17:46 UTCidentified

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

2. 15 Ebrel 2026 da 17:54 UTCmonitoring

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

3. 15 Ebrel 2026 da 21:12 UTCresolved

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

1. 10 Meurzh 2026 da 16:00 UTCinvestigating

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

2. 10 Meurzh 2026 da 16:07 UTCidentified

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

3. 10 Meurzh 2026 da 16:10 UTCmonitoring

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

4. 10 Meurzh 2026 da 16:19 UTCresolved

   The Visualizer is fully operational.

1. 4 Meurzh 2026 da 23:24 UTCidentified

   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. 5 Meurzh 2026 da 00:33 UTCidentified

   We are continuing to work on restoration of pipeline operations.

3. 5 Meurzh 2026 da 02:58 UTCidentified

   The team is continuing to work on recovery.

4. 5 Meurzh 2026 da 03:56 UTCmonitoring

   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. 5 Meurzh 2026 da 06:28 UTCmonitoring

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

6. 5 Meurzh 2026 da 16:39 UTCresolved

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

1. 26 Cʼhwevrer 2026 da 16:59 UTCinvestigating

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

2. 26 Cʼhwevrer 2026 da 17:34 UTCidentified

   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. 26 Cʼhwevrer 2026 da 18:34 UTCidentified

   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. 26 Cʼhwevrer 2026 da 20:33 UTCidentified

   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. 26 Cʼhwevrer 2026 da 22:07 UTCidentified

   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. 26 Cʼhwevrer 2026 da 23:35 UTCmonitoring

   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. 27 Cʼhwevrer 2026 da 00:44 UTCmonitoring

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

8. 27 Cʼhwevrer 2026 da 00:50 UTCmonitoring

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

9. 27 Cʼhwevrer 2026 da 01:15 UTCmonitoring

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

10. 27 Cʼhwevrer 2026 da 01:32 UTCresolved

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

1. 25 Cʼhwevrer 2026 da 04:55 UTCidentified

   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. 25 Cʼhwevrer 2026 da 06:01 UTCidentified

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

3. 25 Cʼhwevrer 2026 da 06:20 UTCmonitoring

   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. 25 Cʼhwevrer 2026 da 07:00 UTCmonitoring

   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. 25 Cʼhwevrer 2026 da 12:41 UTCmonitoring

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

6. 25 Cʼhwevrer 2026 da 15:03 UTCmonitoring

   Data backfill for bulk data is continuing to process.

7. 25 Cʼhwevrer 2026 da 15:06 UTCresolved

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

1. 8 Genver 2026 da 20:53 UTCinvestigating

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

2. 8 Genver 2026 da 21:24 UTCidentified

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

3. 8 Genver 2026 da 21:57 UTCmonitoring

   Logins are working again. We are monitoring recovery.

4. 8 Genver 2026 da 22:10 UTCresolved

   The issue with Visualizer logins is resolved.

1. 11 Kerzu 2025 da 10:54 UTCidentified

   - Greynoise Bulk data delay - API Data freshness degraded

2. 11 Kerzu 2025 da 17:59 UTCresolved

   Our data service has been restored to real time.

1. 29 Here 2025 da 13:57 UTCinvestigating

   1 hour behind on processing bulk data

2. 29 Here 2025 da 14:30 UTCresolved

   Bulk data processing has caught up

1. 20 Here 2025 da 13:35 UTCidentified

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

2. 20 Here 2025 da 20:00 UTCidentified

   We're continuing to monitor AWS status and impacts.

3. 21 Here 2025 da 00:11 UTCresolved

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

1. 9 Here 2025 da 14:33 UTCidentified

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

2. 9 Here 2025 da 14:56 UTCmonitoring

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

3. 9 Here 2025 da 15:02 UTCresolved

   The GreyNoise API is fully operational.

1. 28 Gouere 2025 da 22:27 UTCinvestigating

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

2. 28 Gouere 2025 da 22:43 UTCmonitoring

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

3. 28 Gouere 2025 da 23:15 UTCresolved

   The Visualizer is stable.

1. 3 Mezheven 2025 da 16:41 UTCidentified

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

2. 3 Mezheven 2025 da 21:41 UTCresolved

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

1. 16 Mae 2025 da 17:13 UTCinvestigating

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

2. 16 Mae 2025 da 19:08 UTCresolved

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

1. 11 Mae 2025 da 20:54 UTCidentified

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

2. 11 Mae 2025 da 21:27 UTCidentified

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

3. 11 Mae 2025 da 21:40 UTCmonitoring

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

4. 11 Mae 2025 da 23:06 UTCmonitoring

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

5. 12 Mae 2025 da 01:05 UTCresolved

   Data reprocessing is complete. All systems are operational.