The issue was caused by an incorrect URL being monitored, leading to an SSL connect error for researcher.gen4.dev. Team corrected the monitor URL, resolving the incident automatically without further escalations.