G-core Under Scheduled Maintenance, Sines-2 Networking Affected

Scheduled maintenance and localized issues like this illustrate the constant operational demands of global CDN and edge cloud providers. While much of G-core's network remains functional, a specific regional networking issue can still impact localized streaming delivery and other edge services. Companies relying on G-core or similar providers must monitor status pages closely for specific component-level alerts to manage potential localized service degradation. We will continue to track G-core's resolution of the Sines-2 networking issue and any broader implications for its service stability.

Recent reports highlight the continuous operational challenges faced by CDN and cloud providers. For instance, IsDown, a status page aggregator, reported in May 2026 that G-core had 41 incidents in the previous 90 days, including 10 major outages and 31 minor incidents, with a median duration of 3 hours and 19 minutes. These incidents included a four-hour CDN outage across multiple regions on May 7, 2026, and a one-hour Cloud outage in Luxembourg-3 on April 29, 2026, per IsDown. Furthermore, G-core's own status page shows a scheduled Cloud API maintenance completed on April 22, 2026, aimed at enhancing database load balancer reliability, which intermittently caused 5xx errors. These events underscore the dynamic environment of global infrastructure, where even planned updates and regional incidents necessitate robust monitoring and incident management protocols for maintaining service continuity for streaming and other latency-sensitive applications.