--- service: "upcroft.ai" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-11-02T21:22:46.964Z" url: "https://instatus.com/now/zh/upcroft.ai" official_status_page: "https://status.upcroft.ai" website: "https://upcroft.ai" --- # upcroft.ai 故障了吗？ 没有，一切正常. 过去一小时 0 份反馈报告。 ## 官方更新 - **Lulu model response delays** (RESOLVED, 2026-11-01T04:04:13.000Z): Our monitoring detected model response timeouts on 1 November 2026, beginning around 04:04 UTC / 15:04 AEDT (Melbourne), with recovery observed by 04:09 UTC / 15:09 AEDT. Database and authorization checks continued to pass. Model requests did not complete within our monitoring timeout, causing our monitoring to report degraded model availability. The underlying cause remains unconfirmed. The available logs do not distinguish network delays from delays within the model provider. No failed customer conversations were identified in the reviewed application logs. Our automated browser tests did not raise an incident. - **Lulu model response delays** (RESOLVED, 2026-10-31T20:25:07.000Z): Our monitoring detected intermittent model response timeouts on 31 October 2026 UTC / 1 November 2026 AEDT (Melbourne), beginning around 20:25 UTC / 07:25 AEDT. An alert was raised at 20:31 UTC / 07:31 AEDT, and our monitoring observed recovery by 20:33 UTC / 07:33 AEDT. Database and authorization checks continued to pass. Model requests were slower than usual, causing our monitoring to report degraded model availability. Conversation requests continued to complete during the slowdown, although some responses exceeded our monitoring timeout. The underlying cause remains unconfirmed. The available logs do not distinguish network delays from delays within the model provider. No failed customer conversations were identified. All conversation runs recorded in the application logs during the reviewed period completed successfully, and our automated browser tests did not raise an incident. - **Lulu model availability interruption** (RESOLVED, 2026-10-31T05:36:11.000Z): Lulu experienced model availability failures on 31 October 2026, beginning around 05:36 UTC / 16:36 AEDT (Melbourne). Our monitoring raised an alert at 05:38 UTC / 16:38 AEDT and observed recovery by 05:40 UTC / 16:40 AEDT. Database and authorization checks continued to pass. Our recently deployed diagnostic logging captured errors from the upstream model provider stating that the model was at capacity due to high demand. Other availability checks exceeded their response deadline during the same period. No customer impact was observed. No conversation runs were recorded in the application logs during the inspected failure window, and conversations after recovery completed successfully. - **Lulu intermittent model failures** (RESOLVED, 2026-10-30T18:57:41.000Z): Lulu experienced intermittent model failures on 30 October 2026 UTC / 31 October 2026 AEDT (Melbourne). Our monitoring first recorded failures around 18:57 UTC / 05:57 AEDT. Eight internal test conversations encountered failures around 18:58–18:59 UTC / 05:58–05:59 AEDT, very likely during automated browser checks. These earlier failures appear to have been intermittent and may have recovered before our monitoring system confirmed an incident. Model availability failures resumed around 19:05 UTC / 06:05 AEDT. Our monitoring raised an alert at 19:07 UTC / 06:07 AEDT and observed recovery by 19:08 UTC / 06:08 AEDT. Database and authorization checks passed in the captured incident responses. No customer impact was observed across either period. All failures identified in the application logs came from model health checks or internal test conversations consistent with our automated browser tests. We suspect an issue with the upstream model provider, although the exact cause remains unconfirmed. Our current logs record model failures and timeouts without the detailed error messages. We will deploy improved logging to help diagnose future incidents. - **Console and API database connectivity interruption** (RESOLVED, 2026-10-29T07:19:22.000Z): Console and API experienced request timeouts on 29 October 2026, beginning around 06:42 UTC / 17:42 AEDT (Melbourne), with approximately 3–4 minutes of monitored downtime. Both services have recovered. Requests timed out because database connections from the application machines stalled. Console logged a database connection timeout, while API's database health-check requests stalled for several minutes before completing. Console and API are hosted by a different provider from their databases. Our checks showed that the application machines and database instances remained available independently, with no provider-wide outage identified. This points to a temporary network connectivity issue between the two providers. Lulu and its database are hosted by the same provider. Lulu does not rely on that connection between providers and remained available. The exact cause of the network interruption remains unconfirmed. ## upcroft.ai 故障常见问题 ### upcroft.ai 现在挂了吗？ 没有，一切正常. 过去一小时 0 份反馈报告。 ### upcroft.ai 是所有人都坏了，还是只有我？ 看起来只有你遇到。upcroft.ai 的反馈量正常，可以试试刷新页面、检查网络连接，或退出后重新登录。 ### 大家反馈了 upcroft.ai 的哪些问题？ 过去一小时内没有人说明 upcroft.ai 哪里坏了。如果你遇到问题，请在上方选择，让其他人看到。 ### upcroft.ai 上次故障是什么时候？ 过去 30 天内，upcroft.ai 的反馈没有出现激增。 ### upcroft.ai 有状态页面吗？ 有。upcroft.ai 会在官方状态页面发布更新，目前显示：运行正常。 [前往状态页面](https://status.upcroft.ai/) ### upcroft.ai 无法使用时我可以怎么办？ 查看本页和 upcroft.ai 的状态页面获取更新，等几分钟再试一次。不用重新安装：如果是服务中断，要由他们那边修复。 ### 如何反馈 upcroft.ai 的问题？ 点击本页顶部的“我也要反馈问题”，再选择哪里坏了。你的反馈会在一分钟内显示在实时图表上，也可以留言告诉其他人你遇到的情况。 ### Instatus Now 是怎么知道的？ 我们把此页面上用户的反馈，与每分钟检查一次的 upcroft.ai 官方状态页结合起来。