Visitor status should be operating as normal. Thanks for your patience!

We've identified and resolved the operator issue. Thanks for your patience!

We have observed that the issue is no longer occurring since we restarted the servers. We got the 'all clear' at this point.

The scheduled maintenance has been completed.

Our chat console is now operating normally.

All of our transcript and email systems are back to normal and operational.

We've just got updated that the issue with Cobrowsing should now be stable.

Cobrowsing is back up and running. Thanks for the patience.

We're no longer seeing reports of Olark not loading on sites affected by the European ISP outage earlier today. We're continuing to monitor the situation but it we are resolving this incident for now.

The scheduled maintenance has been completed.

We're confident that the issue has been resolved. We've seen no further occurrences in the last 30 minutes, therefore marking this incident as resolved.

Our services are stable and fully operational. Thanks for the patience.

We are confident the issue with Geolocation is now resolved. The change is propagating and you will see geolocation information shortly if you are not already. Please do tell us if you continue to have issues.

A chatbox code change we deployed at 1:08pm Pacific caused a host resolution problem on one of our legacy loaders which currently a very small subset of clients are using. During this time it’s likely the chatbox would not have loaded properly. We rolled back this change at 1:56pm Pacific and consider this issue resolved.

For a period of about one hour starting around 12:20pm PST, the deployed chatbox Javascript code contained an external dependency overriding the "_" variable in the global namespace, affecting some websites using the underscore library. We rolled back the changes immediately, and as of the rollback all new downloads are no longer affected by this issue. Previously loaded chatboxes may have contained a cached copy for up to 2 hours. Although we have safeguards in place to prevent this, today's issue was caused by a gap in automated testing of final builds. Future builds will now run an additional simulated runtime check for all globals before allowing a deploy.

The scheduled maintenance has been completed.

We've been continuing to monitor the issue and are satisfied that the chat service has returned to normal. We're resolving this incident and operators can chat again as normal. Currently we believe the issue to have been caused by affected load balancers.

This incident has been resolved.

We believe that the issue with transcripts has been resolved and is now working normally.

The scheduled maintenance has been completed.

We've monitored services for a couple hours and did not see any further instability. At this point, we believe the issue is resolved. We will be providing a post-mortem update regarding the issue.

All systems appear to be functioning as normal again. Operators can continue to log in and chat as usual. Similar to the incidents on March 30th (see: http://status.olark.com/incidents/zcsc15y53xwq and http://status.olark.com/incidents/2c36gzlv1qw7), we believe this to be caused by a service disruption to an upstream provider. Once the causes are clearer, we will write an update explaining what occurred as well as any steps we are able to take to reduce the risk of this happening again.

We've had no further reports of XMPP chat connection issues, and our metrics indicate the chat is performing as normal. We're resolving this issue as we continue to investigate today's problems/

The issue with the Olark website and operator console has now been resolved. You should be able to use the service as usual. We believe this was caused by a service interruption for an upstream network provider, we're continuing to investigate. Thanks again for your patience while we addressed the issue.

The scheduled maintenance has been completed.

Chatbox settings is now fully operational.

Chat network account creation and updates are now fully operational.

We're satisfied the issue related to message delivery has been resolved. We're continuing to look at the underlying issue that caused this to happen, but customers should not be currently affected.

Cobrowsing functionality should now be resolved for all customers. We will continue to monitor this issue, but we believe it to be resolved now. Thanks for your patience! =)

Everything should be copacetic with transcripts!

We're resolving this issue as our metrics continue to look normal and we aren't seeing any further reports of problems. We apologize for this interruption of service.

We're resolving this issue as our metrics continue to look normal and we aren't seeing any further reports of problems. We'll be providing a postmortem of the events that led to the outage as well as how we might avoid this in the future. From a support point of view, we'd want to apologize for any delay in our response to emails or tweets. Our helpdesk provider was experiencing issues at the same time, making it difficult to reply to tickets in a timely manner.

We are confident the issue has been resolved and are reflecting on the outage so we can take steps to prevent similar problems occurring in the future.

This incident has been resolved.

Around 2 PM EST one of our database servers had an issue, causing problems in several parts of Olark. Chat was affected for about 5 minutes. Olark.com was down for about 15 minutes, and chat.olark.com was down for about 25 minutes. All systems are currently operational again, but if you have questions please contact us at [email protected]!

The scheduled maintenance has been completed.

This incident has been resolved.

Maintenance is over, all clear :)

This incident has been resolved.

The server updates are now complete, have a good one!

This incident has been resolved.

No issues to report from server maintenance.

Maintenance has been completed.

The issue affecting a small number of Olark accounts and message delivery should now be resolved.

We believe this issue to be resolved, and are continuing to monitor it.

If you are having trouble logging in to the operator console try restarting your browser to clear your DNS cache.

Site setting updates issue has been resolved.

Systems are now stable, incident has been resolved

The scheduled maintenance has been completed.

Just before 2pm Pacific (5pm EST) one of our load balancer systems started experiencing issues. By 2:45pm Pacific we had spun up and switched over to another load balancer system and chat became operational again. The cause of the issue was a temporarily disabled load balancer, as a result of a DDOS attack on a site unrelated to Olark. As a result of the outage, our new load balancer now supports IPv6 and we've taken steps to add additional reliability around this part of our system.

This incident has been resolved.

Maintenance has been completed on chat.olark.com

Desk.com interruptions have been normal for the last three hours or so. We are continuing to monitor the situation, but integration activity should be normal from that time period onward.

From about 20:25 UTC to 20:32 UTC we were seeing slow message delivery, but the issue is now resolved.

We've resolved the issue preventing operators connecting to the Olark chat console at https://chat.olark.com. We believe this is caused by a recent change in the Avast! Webshield as part of their antivirus product. We have found that disabling the "HTTPS scanning" feature within Webshield allows operators to connect to Olark. You can find steps on how to disable HTTPS scanning at: https://www.avast.com/en-us/faq.php?article=AVKB189 Olark is in communication with the folks at Avast! to address the problem permanently. If you're not comfortable disabling the HTTPS scanning, you can use Pidgin on your Windows desktop in the meantime. Find setup instructions for Pidgin at http://www.olark.com/help/pidgin For users seeing the "Whoops! We were unable to connect to the server..." error who do not use Avast!, please submit a support ticket at https://www.olark.com/help/ticket

The scheduled maintenance for chat.olark.com has been completed.

We believe the incident has been resolved. chat.olark.com should now be working as normal. We will continue to monitor the situation.

The scheduled maintenance has been completed.

Earlier today there were some issues with users logging in to Olark using their Google account. Logging in to Olark with your Google account is currently working and we're continuing to investigate. If you see any odd behavior please contact us!

The scheduled maintenance has been completed.

The issue affecting transcripts has been resolved. Transcripts should be appearing on the Olark dashboard and in your CRM integrations as normal from now. Thanks again for your patience.

Scheduled maintenance complete. You can log in and chat as normal. Thanks for your patience.

All chat.olark.com servers are operational again. Thanks for your patience.