What is the impact?
Threat data’s ip addresses and countries of origin reported during the incident - in the dashboard and with our data integrations - are not the ones from your end-users devices but related to Google’s proxy server instead.
All your apps with threat monitoring data during that period are impacted.
Unfortunately the original data is not recoverable, so all threat data between the mentioned timestamps will remain accompanied with wrong ip address and country of origin metadata.
How to identify compromised data?
In case you already integrated the data in your backend systems: all data reported between November 16th 12:05pm UTC and November 17th 9:00am UTC is accompanied with an ip address in the range 35.191.0.0/16 originating from the country United States.
To avoid future confusion when analysing historical threat monitoring data, we will retroactively update the ip addresses of these events to 0.0.0.0
Resolved
What is the impact?
Threat data’s ip addresses and countries of origin reported during the incident - in the dashboard and with our data integrations - are not the ones from your end-users devices but related to Google’s proxy server instead.
All your apps with threat monitoring data during that period are impacted.
Unfortunately the original data is not recoverable, so all threat data between the mentioned timestamps will remain accompanied with wrong ip address and country of origin metadata.
How to identify compromised data?
In case you already integrated the data in your backend systems: all data reported between November 16th 12:05pm UTC and November 17th 9:00am UTC is accompanied with an ip address in the range 35.191.0.0/16 originating from the country United States.
To avoid future confusion when analysing historical threat monitoring data, we will retroactively update the ip addresses of these events to 0.0.0.0
Monitoring
A fix has been deployed. All new threats should report the correct client ip and country again.
Identified
We've identified the cause of the issue and are working on a fix.
Investigating
We've received reports that ThreatCast is reporting all threats as coming from a Google owned IP address. We are investigating the cause and aim to have a fix deployed as soon as possible.