Google Security Products Status Dashboard
Incident affecting Mandiant Digital Threat Monitoring
Mandiant Digital Threat Monitoring customers experiencing issues in receiving emails or new alerts and the research tools are not returning results.
Incident began at 2026-02-09 14:30 and ended at 2026-02-18 09:00 (all times are US/Pacific).
Previously affected location(s)
Global
| Date | Time | Description | |
|---|---|---|---|
| | 18 Feb 2026 | 10:31 PST | Summary: Mandiant Digital Threat Monitoring customers may have experienced issues in receiving emails or new alerts, and may have seen HTTP 404 Not Found error when viewing alerts through the web console or API. Description: The issue with Mandiant Digital Threat Monitoring has been resolved as of 2026-02-18 at 09:00 US/Pacific. Customer Symptoms: Customers were unable to view alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST and received an HTTP 404 Not Found error. Workaround: API users were able to set the query parameter refs=false for all endpoints that allow the refs parameter. |
| | 17 Feb 2026 | 16:31 PST | Summary: Mandiant Digital Threat Monitoring customers may see HTTP 404 Not Found error when viewing alerts through the web console or API. Description: A temporary data event in part of our system is causing Digital Threat Monitoring alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST to be unavailable. When a customer attempts to view one of these alerts, they may receive an HTTP 404 Not Found error. Our engineering team continues to actively work to restore the availability of these alerts. At this time, the majority of the previously unavailable alerts have been restored. However, customers may still receive errors when viewing the small percentage that have not yet been restored. At this time we do not have an estimated completion for restoring the remaining alerts. We will provide the next update on Wednesday, 2026-02-18 17:00 PST. Customer Symptoms: Customers may be unable to view alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST and instead will receive an HTTP 404 Not Found error. Workaround: API users can set the query parameter refs=false for all endpoints that allow the refs parameter. At this stage, there is no known workaround for viewing alert details via the UI or for other API endpoints. |
| | 16 Feb 2026 | 16:19 PST | Summary: Mandiant Digital Threat Monitoring customers may see HTTP 404 Not Found error when viewing alerts through the web console or API. Description: A temporary data event in part of our system is causing Digital Threat Monitoring alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST to be unavailable. When a customer attempts to view one of these alerts, they may receive an HTTP 404 Not Found error. Our engineering team continues to actively work to restore the availability of these alerts. At this time, the majority of the previously unavailable alerts have been restored. However, customers may still receive errors when viewing the small percentage that have not yet been restored. At this time we do not have an estimated completion for restoring the remaining alerts. We will provide the next update on Tuesday, 2026-02-17 17:00 PST. Customer Symptoms: Customers may be unable to view alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST and instead will receive an HTTP 404 Not Found error. Workaround: API users can set the query parameter refs=false for all endpoints that allow the refs parameter. At this stage, there is no known workaround for viewing alert details via the UI or for other API endpoints. |
| | 15 Feb 2026 | 10:17 PST | Summary:Mandiant Digital Threat Monitoring customers may see HTTP 404 Not Found error when viewing alerts through the web console or API. Description:A temporary data event in part of our system is causing Digital Threat Monitoring alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST to be unavailable. When a customer attempts to view one of these alerts, they may receive an HTTP 404 Not Found error. Our engineering team continues to actively work to restore the availability of these alerts. The estimated time at which all alerts will be restored is Monday, 2026-02-16 17:00 PST. We will provide the next update on Monday, 2026-02-16 17:00 PST. Customer Symptoms:Customers may be unable to view alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST and instead will receive an HTTP 404 Not Found error. Workaround:API users can set the query parameter refs=false for all endpoints that allow the refs parameter. At this stage, there is no known workaround for viewing alert details via the UI or for other API endpoints. |
| | 14 Feb 2026 | 11:55 PST | Summary:Mandiant Digital Threat Monitoring customers may see HTTP 404 Not Found error when viewing alerts through the web console or API. Description:A temporary data event in part of our system is causing Digital Threat Monitoring alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST to be unavailable. When a customer attempts to view one of these alerts, they may receive an HTTP 404 Not Found error. Our engineering team continues to actively work to restore the availability of these alerts. We will provide the next update on Sunday, 2026-02-15 12:00 PST. Customer Symptoms:Customers may be unable to view alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST and instead will receive an HTTP 404 Not Found error. Workaround:API users can set the query parameter refs=false for all endpoints that allow the refs parameter. At this stage, there is no known workaround for viewing alert details via the UI or for other API endpoints. |
| | 10 Feb 2026 | 00:59 PST | Summary:Mandiant Digital Threat Monitoring customers may see HTTP 404 Not Found error when viewing alerts through the web console or API. Description:A temporary data event in part of our system is causing Digital Threat Monitoring alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST to be unavailable. When a customer attempts to view one of these alerts, they may receive an HTTP 404 Not Found error. Our engineering team continues to actively work to restore the availability of these alerts. We will provide the next update on Saturday, 2026-02-14 12:00 PST. Customer Symptoms:Customers may be unable to view alerts generated between Monday, 2026-02-09 14:30 PST and Tuesday, 2026-02-10 21:30 PST, and instead will receive an HTTP 404 Not Found error. Workaround:None at this time. |
- All times are US/Pacific