GreyNoise Enterprise Outage History

13 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live GreyNoise Enterprise status100.00% uptime history

Every Recorded GreyNoise Enterprise Incident

GreyNoise Enterprise incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 28, 2026Delayed Data ProcessingBulk data freshness is restored. All systems operational.2h 22mResolved
Oct 9, 2026Bulk Data Processing DelayAll bulk data has been restored.52 minResolved
Sep 14, 2026Full System OutageAll systems are back online.22 minResolved
Sep 13, 2026Session Explorer processing delayThe delay has been resolved; all packets are now being processed as normal.14h 20mResolved
Aug 7, 2026API OutageThe 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.1h 4mResolved
Jun 16, 2026Delayed Data ProcessingData backlog processing has completed and bulk data exports are available.6h 6mResolved
Apr 15, 2026Intermittent IP Details Page FailuresWe have confirmed resolution of the issue that led to the errors.3h 25mResolved
Mar 10, 2026Visualizer ErrorsThe Visualizer is fully operational.18 minResolved
Mar 4, 2026Data Processing DelayedBulk data file processing is complete for all impacted hours and pipeline data delivery is stable.17h 14mResolved
Feb 26, 2026Data Processing DelaysData backfill is complete. All bulk data hours are available.8h 32mResolved
Feb 25, 2026Delayed Data ProcessingBulk data backfill is complete. Overall platform data processing is performance is restored.10h 11mResolved
Jan 8, 2026Visualizer Login OutageThe issue with Visualizer logins is resolved.1h 17mResolved
Dec 11, 2025Delay in processing dataOur data service has been restored to real time.7h 4mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next GreyNoise Enterprise incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This GreyNoise Enterprise Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before GreyNoise Enterprise acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single GreyNoise Enterprise outage in this window ran 17h 14m, against a mean recovery of 5h 38m. If you depend on GreyNoise Enterprise in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.