Zoom.us was inaccessible for a subset of users in the Ohio region in North America
- Started
- 2026-02-10 19:50 UTC
- Resolved
- 2026-02-10 19:56 UTC
- Duration
- 6 minutes
- Date
- 2026-02-10
Incident Timeline
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
On 2/10/2026, between 15:13 UTC and 18:25 UTC on February 10, 2026, a subset of users routing through Cleveland, Ohio experienced connectivity errors caused by network timeouts. A fix has been implemented, and all traffic has returned to normal levels.
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved
This incident has been resolved