Leadr Outage History

This incident has been resolved.

Leadr briefly experienced higher latencies and/or unexpected logouts. Monitoring caught the issue and automated processes resolved it promptly. We apologize for the potential disruption.

While we are continuing to investigate to ensure issues like this do not occur in the future, this incident has been resolved and access has been restored.

API latencies have returned to normal ranges. We will continue to monitor closely.

This afternoon, Leadr experienced infrastructure limitations due to downstream effects of the Amazon Web Services outage. While our region was not primarily affected by the daylong outage, because portions of AWS are built on AWS technologies, the regional outages led to disrupted behavior in services in our region and globally. Shortly after the disruption began, our team stabilized the application in a degraded state and deferred reconstruction until (a) the AWS outage was formally resolved and AWS processing backlogs cleared and (b) US business hours had concluded. As of 5 minutes ago, application servers are fully restored to pre-outage state with no downtime. We will continue to monitor for ripple effects from the AWS outage.

We are continuing to monitor performance, but systems are now returned to normal.

Response times have stabilized fully. We are exploring additional proactive measures.

Leadr experienced extended load times and response failures from some services, which may have resulted in an unexpected logout or difficulty loading data. Interventions resulted in quick recovery.

We have continued to monitor after making improvements, and all portions of the application have been operating steadily for a comfortable period. We will remain watchful for any further hiccups.

This incident has been resolved. We will continue to monitor closely, but if you are experiencing further issues, please contact [email protected].

The application has returned to normal operation.