Elevated Connection Latency in dub1 (Dublin, Ireland) Edge Region
- Started
- 2026-01-28 17:19 UTC
- Resolved
- 2026-01-28 20:21 UTC
- Duration
- 181 minutes
- Date
- 2026-01-28
Incident Timeline
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
We have identified elevated connection latency and intermittent timeouts affecting serving traffic in the dub1 Edge region. A fix is currently being rolled out.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
The dub1 Edge traffic is currently being rerouted to the nearest Edge region (lhr1) to mitigate the impact. We are continuing to work on a fix for this issue.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
We have rerouted all dub1 Edge region traffic as of 17:15 UTC, and traffic should no longer see increased latency. We are continuing to work on a fix to restore traffic back to dub1.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
A fix has been implemented and we have routed traffic back to dub1. We are actively monitoring the results.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.
This incident has been resolved, and traffic has been fully routed back to the dub1 region.