Olark experienced a major incident on June 2, 2025 affecting chat.olark.com and Modern Olark Agent Console (app.olark.com), lasting 17d 12h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 02, 2025, 04:23 PM UTC
We've detected an issue and are working to resolve this quickly. We'll have an update within the hour.
- investigating Jun 02, 2025, 06:00 PM UTC
We're continuing to investigate elevated levels of disconnects from Olark Classic (chat.olark.com). We'll update here as we know more.
- investigating Jun 02, 2025, 09:59 PM UTC
We're continuing to investigate agent disconnects from Olark Classic. Affected teams that would like to utilize our newer agent experience (which is built on a separate platform and not affected by the disconnects issue we're seeing in Olark Classic) are encouraged to have an admin reach out to our support team ([email protected]) and we'll facilitate.
- investigating Jun 09, 2025, 04:52 PM UTC
We're continuing to investigate agent disconnects from Olark Classic. Affected teams that would like to utilize our newer agent experience (which is built on a separate platform and not affected by the disconnects issue we're seeing in Olark Classic) are encouraged to have an admin reach out to our support team ([email protected]) and we'll facilitate.
- investigating Jun 12, 2025, 06:24 PM UTC
We are experiencing network issues that are preventing users from logging in. We're investigating with our provider now and will update as soon as we have more information.
- identified Jun 12, 2025, 07:09 PM UTC
Unfortunately, we're being affected by the Google Cloud, Cloudflare, and other systems outages. We'll update here as soon as we have more information.
- monitoring Jun 12, 2025, 09:07 PM UTC
Google Cloud's outage is beginning to recover and we're seeing Olark services return to normal. We'll continue to monitor closely
- resolved Jun 20, 2025, 04:25 AM UTC
We've been monitoring a fix for the disconnects issue for several days and are now confident that the issue is has been fully resolved.