--- service: "upcroft.ai" status: "up" reports_last_hour: 0 reports_last_12_hours: 0 baseline_reports_per_hour: 0 checked_at: "2026-11-02T16:05:10.933Z" url: "https://instatus.com/now/ko/upcroft.ai" official_status_page: "https://status.upcroft.ai" website: "https://upcroft.ai" --- # upcroft.ai 다운되었나요? 아니요, 정상이에요. 최근 1시간 동안 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 장애 FAQ ### 지금 upcroft.ai 다운됐나요? 아니요, 정상이에요. 최근 1시간 동안 0건 보고됨. ### upcroft.ai이(가) 모두에게 안 되나요, 저만 안 되나요? 당신만 겪는 문제일 수 있어요. upcroft.ai 제보가 평소 수준이니, 페이지를 새로고침하거나 연결을 확인하거나 로그아웃 후 다시 로그인해 보세요. ### upcroft.ai에서 사람들은 어떤 문제를 제보하나요? 지난 1시간 동안 upcroft.ai에서 무엇이 안 되는지 말한 사람이 없습니다. 안 되는 게 있다면 위에서 선택해 다른 사람들도 볼 수 있게 해주세요. ### upcroft.ai의 마지막 장애는 언제였나요? upcroft.ai 제보는 최근 30일간 급증하지 않았어요. ### upcroft.ai에 상태 페이지가 있나요? 네. upcroft.ai은(는) 공식 상태 페이지에 업데이트를 올리며, 현재 상태는 정상입니다. [상태 페이지로 이동](https://status.upcroft.ai/) ### upcroft.ai이(가) 안 되면 어떻게 하나요? 이 페이지와 upcroft.ai의 상태 페이지에서 업데이트를 확인하고, 몇 분 기다린 후 다시 시도하세요. 재설치는 하지 마세요. 장애라면 해결은 서비스 쪽에서 합니다. ### upcroft.ai 문제는 어떻게 제보하나요? 이 페이지 상단의 “저도 같은 문제가 있습니다”를 누르고 무엇이 안 되는지 선택하세요. 제보는 1분 안에 실시간 차트에 표시되며, 댓글로 어떤 상황인지 다른 사람에게 알려줄 수도 있습니다. ### Instatus Now는 어떻게 알죠? 이 페이지의 사용자 제보와 매분 확인하는 upcroft.ai 공식 상태 페이지를 함께 살펴봐요.