Impact Both websites remained available and returned HTTP 200. The status page incorrectly reported disruptions for tropikal.ai from 11:54 UTC and tropikal.dev from 13:19 UTC.

What happened Website releases changed their page titles, while the uptime monitor still required outdated page-title checks. The content mismatch was reported as downtime.

Resolution We replaced the title checks with stable canonical-address markers while retaining the HTTP-status and response-time checks.

Prevention Regression coverage now rejects marketing-title checks for website availability monitoring so routine copy changes cannot create the same false positive.

Impact app.tropikal.ai was unavailable during the periods shown above.

What happened The server’s hard drive filled up, preventing the App from starting correctly.

Resolution We cleared space, restored the App, and confirmed it is operating normally.

Prevention We added early storage-capacity alerts and improved routine cleanup so we can act before service is affected.