BrighterBalance - Slow or failed sign-ins for some users – Incident details

Inngest → Function execution experiencing degraded performance

Slow or failed sign-ins for some users

ResolvedMajor outage2 hours 32 minutes

Affected

Core Application

Operational from 3:20 PM to 5:52 PM

Login/SSO

Operational from 3:20 PM to 5:52 PM

  • PostmortemUTC

    Summary

    On Friday, October 23, between about 11:20 AM and 1:45 PM ET, some BrighterBalance users, mostly in the southeastern US, had trouble signing in and loading pages. From about 11:20 to 11:45 AM, some sign-in and page requests timed out after 40–90 seconds and failed. From 11:45 AM to 1:45 PM, sign-ins worked but were slower than usual, sometimes taking a few seconds.

    Impact

    • Affected: some users whose internet traffic reaches us through network locations in the southeastern US.

    • Not affected: users in other regions, and our background processing (report generation, digests, scheduled jobs). Both kept running normally throughout.

    • Data: no data was lost or changed. The requests that failed never reached our database, so nothing was partially saved.

    Timeline (ET)

    11:20 AM: Sign-in and page requests from the southeastern US start timing out.

    11:25 AM: We start investigating.

    11:42 AM: Last failed request. Sign-ins work again but are slow.

    11:45 AM–1:45 PM: Performance gradually improves.

    1:45 PM: Response times are back to normal. We resolved the incident after continued monitoring.

    Cause

    The problem was with an upstream infrastructure provider, on the network path between our edge network and our sign-in and database services. Requests from affected regions either didn't reach our services or reached them very slowly, while traffic from other regions kept working normally. No change to BrighterBalance's code or configuration was involved, and nothing was deployed that day. We're working with our provider to confirm exactly what failed on their side.

    What we're doing

    • Sharing request-level details from the incident with our provider.

    • Reviewing how we detect region-specific problems like this one, so we can post status updates sooner.

    If you saved an observation between 11:20 and 11:45 AM ET and saw an error, please check that it appears in your records, and re-enter it if not. Questions? Contact us at hello@brighterbalance.app.

  • ResolvedUTC
    This incident has been resolved.
  • MonitoringUTC
    Sign-ins are working for all users. Some requests may still be a little slower than usual while our provider finishes recovering. We're continuing to monitor and will post an update when performance is fully back to normal.