Leadr had 10 outages in the last 2 years totaling 10h 50m of downtime — averaging 0.4 incidents per month.
There were 10 Leadr outages since August 23, 2025 totaling 10h 50m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
We are currently investigating reports of some users being unable to view agenda topics in meetings they are accessing. Our team is looking into this now and working on a quick resolution.
This issue has been resolved, but we're closely monitoring to prevent further difficulties accessing meeting agendas.
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.
We have identified a delay in API responses and are mitigating the issue.
API latencies have returned to normal ranges. We will continue to monitor closely.
We are closely monitoring a series of intermittent performance issues which are tied to AWS platform disruptions since early morning hours today.
Performance has improved, but we are continuing to monitor closely until AWS reports full resolution of degraded services.
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 currently investigating an issue which is slowing load times for some users when attempting to sign in.
We are continuing to monitor performance, but systems are now returned to normal.
We are currently investigating this issue.
Response times are improving. We're continuing to work through root cause analysis to prevent future issues.
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 are currently investigating reports of slow load times and failures to sign in to Leadr.
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.
We are currently investigating an issue which is causing page timeouts and login failures for some users.
This incident has been resolved. We will continue to monitor closely, but if you are experiencing further issues, please contact [email protected].
Our database provider is experiencing technical difficulties, which has led to an outage of our application. We are pursuing remedy with their team.
Our database provider is actively investigating the interruption.
The database is recovering. We will monitor briefly before resolving.
The application has returned to normal operation.