BrainBRAIN
// status — system status

All systems operational

Brain knocks on its own front doors every few minutes from the outside and writes down how long each one took to answer. Numbers below cover the last 30 minutes. This page refreshes itself every 30 seconds.

Your own browser reached Brain in measuring… · checked at 12:34:02 AM

trybrain.io (main address)
Operational
Typical
144 ms
Slow case (p95)
614 ms
Worst case (p99)
614 ms
Failed checks
0 of 6
Published app (Lovable hosting)
Operational
Typical
617 ms
Slow case (p95)
1.62 s
Worst case (p99)
1.62 s
Failed checks
0 of 6
Where is the delay?

Both front doors are healthy (main address 614 ms, published app 1.62 s).

Healthy limits: slow case under 2.50 s, worst case under 5.00 s, failed checks under 20%. Crossing any of them opens an incident below and emails the Brain team straight away.

Last 24 hours — slow-case response time
main address published appscale up to 6.07 s

Incident timeline

  1. Resolved
    trybrain.io (main address) is slow9/4/2026, 11:35:06 PM → 9/5/2026, 12:10:02 AM

    Slow-case response time is 2.59 s and worst-case is 2.59 s; the healthy limits are 2.50 s and 5.00 s.

  2. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 10:50:05 PM → 9/5/2026, 12:10:02 AM

    Slow-case response time is 2.59 s and worst-case is 2.59 s; the healthy limits are 2.50 s and 5.00 s.

  3. Resolved
    trybrain.io (main address) is slow9/4/2026, 10:50:04 PM → 9/4/2026, 11:20:07 PM

    Slow-case response time is 2.93 s and worst-case is 2.93 s; the healthy limits are 2.50 s and 5.00 s.

  4. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 9:45:08 PM → 9/4/2026, 10:30:15 PM

    Slow-case response time is 3.80 s and worst-case is 3.80 s; the healthy limits are 2.50 s and 5.00 s.

  5. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 9:00:20 PM → 9/4/2026, 9:35:03 PM

    Slow-case response time is 2.65 s and worst-case is 2.65 s; the healthy limits are 2.50 s and 5.00 s.

  6. Resolved
    trybrain.io (main address) is slow9/4/2026, 9:00:19 PM → 9/4/2026, 9:35:03 PM

    Slow-case response time is 2.65 s and worst-case is 2.65 s; the healthy limits are 2.50 s and 5.00 s.

  7. Resolved
    trybrain.io (main address) is slow9/4/2026, 7:50:08 PM → 9/4/2026, 8:20:12 PM

    Slow-case response time is 2.84 s and worst-case is 2.84 s; the healthy limits are 2.50 s and 5.00 s.

  8. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 6:00:30 PM → 9/4/2026, 6:31:01 PM

    Slow-case response time is 2.54 s and worst-case is 2.54 s; the healthy limits are 2.50 s and 5.00 s.

  9. Resolved
    trybrain.io (main address) is slow9/4/2026, 6:00:29 PM → 9/4/2026, 6:31:01 PM

    Slow-case response time is 2.56 s and worst-case is 2.56 s; the healthy limits are 2.50 s and 5.00 s.

  10. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 4:35:06 PM → 9/4/2026, 5:35:07 PM

    Slow-case response time is 2.69 s and worst-case is 2.69 s; the healthy limits are 2.50 s and 5.00 s.

  11. Resolved
    trybrain.io (main address) is slow9/4/2026, 4:35:05 PM → 9/4/2026, 5:35:07 PM

    Slow-case response time is 2.68 s and worst-case is 2.68 s; the healthy limits are 2.50 s and 5.00 s.

  12. Resolved
    trybrain.io (main address) is slow9/4/2026, 2:55:05 PM → 9/4/2026, 4:25:05 PM

    Slow-case response time is 6.06 s and worst-case is 6.06 s; the healthy limits are 2.50 s and 5.00 s.

  13. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 2:46:06 PM → 9/4/2026, 4:25:06 PM

    Slow-case response time is 6.07 s and worst-case is 6.07 s; the healthy limits are 2.50 s and 5.00 s.

  14. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 12:30:18 PM → 9/4/2026, 2:31:22 PM

    Slow-case response time is 4.17 s and worst-case is 4.17 s; the healthy limits are 2.50 s and 5.00 s.

  15. Resolved
    trybrain.io (main address) is slow9/4/2026, 12:30:17 PM → 9/4/2026, 2:31:21 PM

    Slow-case response time is 4.17 s and worst-case is 4.17 s; the healthy limits are 2.50 s and 5.00 s.

  16. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 11:05:08 AM → 9/4/2026, 11:40:05 AM

    Slow-case response time is 2.83 s and worst-case is 2.83 s; the healthy limits are 2.50 s and 5.00 s.

  17. Resolved
    Published app (Lovable hosting) is slow9/4/2026, 8:30:07 AM → 9/4/2026, 9:20:05 AM

    Slow-case response time is 2.50 s and worst-case is 2.50 s; the healthy limits are 2.50 s and 5.00 s.

  18. Resolved
    trybrain.io (main address) is slow9/4/2026, 8:30:07 AM → 9/4/2026, 9:20:04 AM

    Slow-case response time is 2.57 s and worst-case is 2.57 s; the healthy limits are 2.50 s and 5.00 s.

  19. Ongoing
    Scheduled job "capi-value-model" is failing every run9/4/2026, 7:20:09 AM

    All 1 runs in the last 24 hours failed. Whatever this job maintains has not happened since at least that long ago. Last error: ERROR: CRON_SECRET is not configured for CAPI value model dispatch CONTEXT: PL/pgSQL function dispatch_capi_value_model() line 12 at RAISE

  20. Ongoing
    Scheduled job "booking-coverage-sweep" is failing every run9/4/2026, 7:20:08 AM

    All 1 runs in the last 24 hours failed. Whatever this job maintains has not happened since at least that long ago. Last error: ERROR: CRON_SECRET is not configured for booking coverage sweep CONTEXT: PL/pgSQL function dispatch_booking_coverage_sweep() line 12 at RAISE

  21. Resolved
    Scheduled job "vacuum-cron-run-details-weekly" has not run at all9/4/2026, 7:01:24 AM → 9/4/2026, 7:16:08 AM

    It is switched on with the schedule "15 3 * * 0" but produced no runs in the last 24 hours.

  22. Resolved
    Scheduled job "run-lookalike-builder-weekly" has not run at all9/4/2026, 7:01:23 AM → 9/4/2026, 7:16:07 AM

    It is switched on with the schedule "0 12 * * 1" but produced no runs in the last 24 hours.

  23. Resolved
    Scheduled job "regen-meat-cta-library-weekly" has not run at all9/4/2026, 7:01:21 AM → 9/4/2026, 7:16:06 AM

    It is switched on with the schedule "0 3 * * 1" but produced no runs in the last 24 hours.

  24. Resolved
    Scheduled job "organic-weekly-report-sunday" has not run at all9/4/2026, 7:01:20 AM → 9/4/2026, 7:16:04 AM

    It is switched on with the schedule "0 8 * * 0" but produced no runs in the last 24 hours.

  25. Resolved
    Scheduled job "organic-weekly-report" has not run at all9/4/2026, 7:01:19 AM → 9/4/2026, 7:16:03 AM

    It is switched on with the schedule "0 8 * * 1" but produced no runs in the last 24 hours.

2 open incidents — the team was emailed when each one started and will be emailed again when it clears.