История сбоев Simplr

We are currently investigating this issue. We will give an update soon.

The issue has been identified. We are working on getting this fixed.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

Latency in the platform has been identified. We are currently working on a fix for this.

This incident has been resolved.

This incident has been resolved.

Outage due to infrastructure changes - cluster migration. Change rolled back and services recovered.

Authorization issue with Salesforce backend. Recovered after our service was restarted.

Zendesk Chat Partial outage due to maintenance on the zedesk end

Autorouting stopped worked. Service was restored after expired keys were rotated

Release caused issues and had to be rolled back. Redeployed after code fix.

Integration was not working with one ticketing system. Service was fully restored after 3 hours

Tickets were not getting created for Bold integration. Code fix restored the service after 5 hours. Only one partner was impacted

Integration was offline with one partner. Service was restored after 3 hours

Intermittent platform performance degradation. Service was fully restored after 2 hours.

Autorouting failures. Config was corrected and service was restored by 9:00a PST

Intermittent page freeze due to the chatbot. Service was fully restored after a code fix on 11/23. Only one partner was impacted.

Email queue was backed up due to mass ticket event external to Simplr. Impacted limited partners. Added processing time due to delays. Service was fully restored after 10 hours.

Salesforce chat was offline for 90 mins. Service was restored. Only 1 partner was impacted

Genesys chat was offline for an hour. Impacted only 1 partner. Service was resotred.

Salesforce chat was offline. Only impact 1 partner and lasted 90 mins. Service was restored.

Email autorouting stopped working that caused a 90 mins delay on escalation. Service was restored at 10:55 pm CT

Platform response time delays and routing delays built a backlog. Changing routing parameter fixed the issue