pingoru pingoru Parade had 3 outages in the last 2 years totaling 482h 26m of downtime, averaging 0.1 incidents per month.
There were 3 Parade outages since February 5, 2026 totaling 482h 26m of downtime. Each is summarised below. Incident details, duration, and resolution information.
An upstream outage with our inference infrastructure provider has taken down our third party dialogue LLM cluster, resulting in agent silence. They have blocked further outbound dispatch and are queueing calls. They are moving workloads over to restore functionality.
We are currently experiencing a period of instability, and some services may be temporarily disrupted. Our teams are actively working on a fix and monitoring the situation closely. Updates will be shared as progress is made.
We have pinpointed the root cause of this issue to be an authentication issue with one of our integration partners, that is causing some locking throughout our system. We have temporarily stopped our scheduled postings feature, to contain the impact, and to prevent this issue from causing any further degradation. Scheduled postings will remain non-functional until we can work with the partner to fix authentication. Other features should not be affected.
We have deployed a fix to scheduled postings and are currently monitoring performance.
We have confirmed that our deploy has fixed the scheduled posting instability issues from this morning. The scheduled posting feature is now fully enabled for all customers. However, due to Truckstop instability yesterday (see their incident here: https://truckstop.statuspage.io/incidents/s6x1x7bwb8dp) - Some of our Truckstop auth tokens were invalidated with no way of recovering without assistance from Truckstop. This is causing the Truckstop integration to remain broken for those affected customers. Our support team will be reaching out if your Truckstop posting integration is affected, so that we can work together with Truckstop to get your integration back into a healthy state. We will be closing this incident now, as it is no longer global, and scheduled postings are running again.
This incident has been resolved.