Potential ingress problem

Update timeline

1. investigating Mar 25, 2026, 01:48 PM UTC

   Status: Investigating We confirmed a problem with our system and are currently investigating its root cause. We will provide an update once we have identified the underlying problem. Affected components Gateway (Degraded performance)

2. identified Mar 25, 2026, 02:07 PM UTC

   Status: Identified We have identified a problem with one of our ingress clusters and are now trying to re-route the traffic. We will provide another update once the fix is rolled out. Affected components Gateway (Degraded performance)

3. monitoring Mar 25, 2026, 02:08 PM UTC

   Status: Monitoring We have successfully deployed the new ingress cluster and are now monitoring the system to make sure everything works as expected. We will provide an update once we can confirm our fix is effective. Affected components Gateway (Degraded performance)

4. resolved Mar 25, 2026, 02:15 PM UTC

   Status: Resolved We confirmed that our fix resolved the problem. Apologies for the inconvenience. We will run some additional investigation to find out how we can prevent the ingress problem in the future. Affected components Gateway (Operational)

5. resolved Mar 25, 2026, 07:40 PM UTC

   Status: Resolved Our cloud provider confirmed issues on their end: further details can be found on [Network] Increased internet network latencies and packet loss: https://exoscalestatus.com/incidents/228561 Affected components Gateway (Operational)