Resolved after 2 hours, on June 3, 2025.
Link11 POPs affected : Frankfurt: ffm7& ffm14 London: lon2 Singapore: sgp1 06:06, CET - The clusters reported high CPU usage for local filters. 06:10, CET - Internal monitoring reported packet loss for some of the probes. SOC is escalating the events. 06:16, CET - The on-call operations team decided to reload the affected filters and escalate the issue to the Link11 engineering team for further investigation. 06:55, CET - The filter reload process is complete. Monitoring systems report no packet loss. Open points: - The engineering team should investigate the high CPU events and provide a fix. - The Operations team should improve the filter reload process.
Update timeline
- resolved Jun 03, 2025, 01:24 PM UTC
Link11 POPs affected : Frankfurt: ffm7& ffm14 London: lon2 Singapore: sgp1 06:06, CET - The clusters reported high CPU usage for local filters. 06:10, CET - Internal monitoring reported packet loss for some of the probes. SOC is escalating the events. 06:16, CET - The on-call operations team decided to reload the affected filters and escalate the issue to the Link11 engineering team for further investigation. 06:55, CET - The filter reload process is complete. Monitoring systems report no packet loss. Open points: - The engineering team should investigate the high CPU events and provide a fix. - The Operations team should improve the filter reload process.
Your product runs on more than Link11
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services