Status
Status
No incidents reported
No incidents reported
2024-02-13 09:51 UTC
An issue has been found and is currently under investigation.
2024-02-14 16:33 UTC
A solution has been fully rolled out and on-call teams have verified that the impact is resolved.
No further updates are expected.
2024-02-14 05:47 UTC Fix has been deployed to all EU regions and US East. Asia Pacific and US West are scheduled to be completed by 21:00. A final update will be issued when this is complete.
2024-02-14 00:47 UTC Final testing is complete and the fix is being deployed to all production regions over the next few hours. An update will be issued when this is complete.
2024-02-13 20:37 UTC A fix has been identified and making its way to pre-production for final testing. An update will be issued when that is complete.
2024-02-13 18:25 UTC
The issue is limited to a small sub-set of customers. A workaround has been identified and is being tested. A further update will be issued in 2 hours
2024-02-13 16:26 UTC
On-call teams continue working on a solution.
Next update in 2 hours
2024-02-13 15:29 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 13:15 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 12:15 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 11:25 UTC
On-call teams continue working on a solution.
Next update in 1 hour
2024-02-13 11:03 UTC
On-call teams have identified the issue and are working on a solution.
Next update in 20 mins
2024-02-13 10:44 UTC On-call teams are continuing to investigate the issue.
Next update in 20 mins
No incidents reported
No incidents reported
No incidents reported
At 2024-02-09 11:00 UTC We have identified file downloads failures from non-isolated sites taking longer than 30 seconds to process. This affects all the regions except Tokyo (ap-northeast-1)
On-call teams are investigating the issue.
2024-02-09 11:25 UTC On-call teams have identified the issue and are working on a solution.
2024-02-10 02:40 UTC Engineering has completed rolling out a fix globally
2024-02-10 02:40 UTC
A solution has been fully rolled out and on-call teams have verified that the impact is resolved.
No further updates are expected.
2024-02-10 02:40 UTC A solution has been fully rolled out and on-call teams have verified that the impact is resolved.
No further updates are expected.
2024-02-09 20:05 UTC Deployment of the solution has commenced to all impacted regions. Next progress update in 1 hour.
2024-02-09 16:59 UTC
On-call teams continue preparing to roll out the solution to all impacted regions
Next update in 1 hour
2024-02-09 15:58 UTC
On-call teams continue preparing to roll out the solution to all impacted regions.
Next update in 1 hour.
2024-02-09 15:22 UTC
On-call teams continue preparing to roll out the solution to all impacted regions.
2024-02-09 14:29 UTC
On-call teams have verified a solution and are in the process of preparing to roll it out to all impacted regions.
2024-02-09 14:07 UTC
On-call teams continue working on testing and validating the fix.
2024-02-09 13:14 UTC
On-call teams continue working on testing and validating the fix.
2024-02-09 12:43 UTC
On-call teams continue working on testing and validating the fix.
2024-02-09 11:57 UTC
On-call teams have identified a possible solution and are currently testing.
At 2024-02-08 13:43 UTC We identified an issue affecting updates.menlosecurity.com in the APAC region. During the problem, on-prem appliance customers might have seen a delay on live updates. Cloud customers would have seen no direct impact.
At 2024-02-08 14:35 UTC the service was fully restored.
At 2024-02-08 09:55 UTC We identified an issue affecting updates.menlosecurity.com in eu-central-1, eu-west-1, eu-west-2, eu-west-3, me-south-1, sa-east-1, us-east-1, us-east-2, us-west-1, us-west-2
During the problem, on-prem appliance customers might have seen a delay on live updates. Cloud customers would have seen no direct impact.
At 2024-02-08 10:33 UTC the service was fully restored.