pingoru pingoru Hoylu had 3 outages in the last 2 years totaling 25m of downtime, averaging 0.1 incidents per month.
There were 3 Hoylu outages since November 26, 2024 totaling 25m of downtime. Each is summarised below. Incident details, duration, and resolution information.
www.hoylu.com | Website is down at the moment. This incident was automatically created by Instatus monitoring..
www.hoylu.com | Website is back up. This incident was automatically resolved by Instatus monitoring..
Hoylu 4.0 API | US is down at the moment. This incident was automatically created by Instatus monitoring..
nexus.us.hoylu.com is back up. This incident was automatically resolved by Instatus monitoring..
We experienced a brief period of unavailability due to scheduled Azure database maintenance that took longer than expected. Service has been fully restored, and no data was affected. We apologize for any inconvenience..
Users were unable to log in between approx. 3:28 PM EST through 3:42 PM EST, and anything that required auth service would not have been working in that same timeframe. * **Time of Impact**: 26th of November 2024 3:28 PM EST through 26th of November, 2024 3:42 PM EST. * **Cause**: The Redis instance used for auth service was disrupted, which lead to auth service going unhealthy, which in turn made several other services unhealthy, and caused the system to restart. * **Affected Functionality**: Login and disrupted connection of services. * **Affected Systems**: EU system.
Our engineering team worked to identify and resolve the issue as quickly as possible. Normal service was fully restored within minutes of the initial reported incident, but we are continuing to monitor the situation to ensure full system stability. **Next Steps**: We are conducting a thorough review of this incident. Additional safeguards will be implemented to minimize the risk of recurrence and increase the fault resistance of the platform. We sincerely apologize for any inconvenience this incident may have caused. If your business was significantly affected, we encourage you to reach out to our Customer Success team at [[email protected]](mailto:[email protected])..