Resolved: False Positive Service Alert (myjuicebox.io)
Final Update
The monitoring discrepancy on myjuicebox.io has been resolved, and the status page is now correctly reflecting "Operational" status.
Important Note: Throughout this event, the actual application remained 100% functional for all users. This was a monitoring and reporting error, not a service outage.
What Happened?
During a scheduled test of our new OpenID Connect (OIDC) authentication system on our main client, we identified a configuration conflict. The new security protocols inadvertently began requiring authentication for the automated "heartbeat" checks used by our status page (Instatus).
Because the monitor is an automated tool without a user account, it was unable to bypass the new security layer. This resulted in the monitor reporting the site as "Down," even though it was fully accessible to actual users.
Action Taken
To ensure accurate status reporting while we refine our security configurations:
Rollback: We have temporarily disabled the OIDC integration on the main client.
Verification: Our monitoring systems have successfully re-established a connection to the health-check endpoints.
Refinement: Before re-enabling OIDC, we are updating our configuration to explicitly exempt health-check heartbeats from authentication requirements.
Timeline
[3:18 pm]: OIDC testing initiated; Instatus began reporting false-positive downtime.
[4:29 pm]: Engineering identified the authentication conflict with the monitor.
[4:30 pm]: OIDC integration disabled; monitoring restored to "Operational" status.
