BrainBRAIN
// status — system status

Brain is slower than usual

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 9:59:21 AM

trybrain.io (main address)
Degraded
Typical
2.52 s
Slow case (p95)
3.48 s
Worst case (p99)
3.48 s
Failed checks
0 of 6
Published app (Lovable hosting)
Degraded
Typical
2.52 s
Slow case (p95)
3.48 s
Worst case (p99)
3.48 s
Failed checks
0 of 6
Where is the delay?

Both addresses are slow by a similar amount (difference 0 ms), so the delay is inside the app or the database, not in the routing layer.

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 7.27 s

Incident timeline

  1. Ongoing
    Published app (Lovable hosting) is slow9/16/2026, 9:21:04 AM

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

  2. Ongoing
    trybrain.io (main address) is slow9/16/2026, 9:21:03 AM

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

  3. Resolved
    Published app (Lovable hosting) is slow9/16/2026, 8:41:03 AM → 9/16/2026, 9:11:04 AM

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

  4. Resolved
    trybrain.io (main address) is slow9/16/2026, 8:41:03 AM → 9/16/2026, 9:11:03 AM

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

  5. Resolved
    Published app (Lovable hosting) is slow9/16/2026, 8:31:03 AM → 9/16/2026, 8:36:13 AM

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

  6. Resolved
    Published app (Lovable hosting) is slow9/16/2026, 7:51:04 AM → 9/16/2026, 8:26:05 AM

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

  7. Resolved
    trybrain.io (main address) is slow9/16/2026, 7:46:04 AM → 9/16/2026, 8:16:04 AM

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

  8. Resolved
    Published app (Lovable hosting) is slow9/16/2026, 7:01:05 AM → 9/16/2026, 7:26:03 AM

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

  9. Resolved
    trybrain.io (main address) is slow9/16/2026, 7:01:04 AM → 9/16/2026, 7:36:14 AM

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

  10. Resolved
    Published app (Lovable hosting) is slow9/16/2026, 3:01:04 AM → 9/16/2026, 6:31:07 AM

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

  11. Resolved
    trybrain.io (main address) is slow9/16/2026, 3:01:04 AM → 9/16/2026, 6:31:07 AM

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

  12. Resolved
    Published app (Lovable hosting) is slow9/16/2026, 1:31:05 AM → 9/16/2026, 2:16:10 AM

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

  13. Resolved
    trybrain.io (main address) is slow9/16/2026, 1:31:04 AM → 9/16/2026, 2:16:09 AM

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

  14. Resolved
    Published app (Lovable hosting) is slow9/15/2026, 11:51:08 PM → 9/16/2026, 12:31:09 AM

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

  15. Resolved
    trybrain.io (main address) is slow9/15/2026, 11:51:07 PM → 9/16/2026, 12:31:08 AM

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

  16. Resolved
    Published app (Lovable hosting) is slow9/15/2026, 6:56:09 PM → 9/15/2026, 10:36:05 PM

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

  17. Resolved
    trybrain.io (main address) is slow9/15/2026, 6:56:08 PM → 9/15/2026, 10:36:05 PM

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

  18. Resolved
    Published app (Lovable hosting) is slow9/15/2026, 6:06:10 PM → 9/15/2026, 6:31:02 PM

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

  19. Resolved
    trybrain.io (main address) is slow9/15/2026, 6:06:09 PM → 9/15/2026, 6:31:01 PM

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

  20. Resolved
    Published app (Lovable hosting) is slow9/15/2026, 4:56:07 PM → 9/15/2026, 6:01:02 PM

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

  21. Resolved
    trybrain.io (main address) is slow9/15/2026, 4:56:06 PM → 9/15/2026, 6:01:01 PM

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

  22. Resolved
    trybrain.io (main address) is slow9/15/2026, 4:36:07 PM → 9/15/2026, 4:46:05 PM

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

  23. Resolved
    Published app (Lovable hosting) is slow9/15/2026, 4:21:05 PM → 9/15/2026, 4:46:06 PM

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

  24. Resolved
    Published app (Lovable hosting) is slow9/15/2026, 12:16:10 PM → 9/15/2026, 3:11:02 PM

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

  25. Resolved
    trybrain.io (main address) is slow9/15/2026, 12:16:09 PM → 9/15/2026, 3:11:01 PM

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

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