Incidents and maintenance reported on status page for ChoyCraft https://status.choycraft.com/ https://d1lppblt9t2x15.cloudfront.net/logos/8241d5893674cde830c9386de21798b5.png https://status.choycraft.com/ en https://status.choycraft.com/incident/1067979 Tue, 14 Jul 2026 07:47:00 -0000 https://status.choycraft.com/incident/1067979#12b8443aab4f853570f852bf568573e47fa23c44da64b2e2599760f228e22d14 Incident ChoyCraft Website Service Incident Report Incident Date: July 14, 2026 Start Time: 5:35 PM GMT+6 Resolution Time: 7:47 PM GMT+6 Total Duration: Approximately 2 hours 12 minutes Affected Service: ChoyCraft Website (choycraft.com) Incident Type: HTTP 500 — Internal Server Error Status: Resolved Incident Summary On July 14, 2026, the ChoyCraft website experienced an availability incident that resulted in HTTP 500 Internal Server Error responses. The issue was detected by Better Stack's uptime monitoring system at approximately 5:35 PM GMT+6. Monitoring checks from multiple geographic regions, including Australia, North America, and Europe, consistently received HTTP 500 responses from choycraft.com. The incident continued for approximately 2 hours and 12 minutes and was automatically resolved after the website began returning successful responses from all monitored regions. Impact During the incident, visitors attempting to access the ChoyCraft website may have encountered an Internal Server Error and been unable to access the website normally. The monitoring system confirmed that the issue was not isolated to a single monitoring location, as HTTP 500 responses were observed from multiple regions. Detection The incident was detected automatically by Better Stack's uptime monitoring. Initial monitoring observations: Australia: HTTP 500 North America: HTTP 500 Europe: HTTP 500 Response time: Approximately 1.09 seconds Affected request: GET https://choycraft.com The monitoring system subsequently generated an incident and sent an alert notification to the configured escalation contact. Timeline Time (GMT+6) Event 5:35 PM First HTTP 500 response detected from the monitored website. 5:35 PM HTTP 500 responses confirmed from Australia, North America, and Europe. 5:35 PM Better Stack incident created. 5:42 PM Incident notification email sent to the configured contact. 7:46 PM Website recovered for monitoring checks from Europe. 7:47 PM Website recovered for monitoring checks from North America. 7:47 PM Website recovered for monitoring checks from Australia. 7:47 PM Monitoring confirmed service recovery. 7:50 PM Incident automatically resolved after the recovery confirmation period. Technical Details HTTP Status Code: 500 Internal Server Error Request: GET https://choycraft.com Monitoring: Better Stack Uptime Monitoring Regions Affected: Australia North America Europe The monitoring system reported that the HTTP 500 response originated from the site's Vercel infrastructure and included standard HTTP response headers. Root Cause The exact application-level root cause was not identified by the monitoring data available for this incident. The available evidence confirms that the website's infrastructure returned HTTP 500 responses during the incident, but the monitoring information alone does not establish whether the underlying cause was an application error, deployment issue, serverless function failure, configuration problem, dependency failure, or another backend condition. Further application and Vercel logs would be required to determine the definitive root cause. Resolution The incident resolved automatically once the website began returning successful responses to monitoring requests. Recovery was confirmed from multiple monitoring regions, including Europe, North America, and Australia. No manual intervention is recorded in the provided incident timeline. Preventive Actions The following actions are recommended to reduce the likelihood and impact of similar incidents: Review Vercel deployment and runtime logs corresponding to July 14, 2026, between 5:30 PM and 7:50 PM GMT+6. Identify the specific request, application component, or serverless function responsible for the HTTP 500 responses. Review deployments immediately preceding the incident for possible application or configuration changes. Verify environment variables and external service dependencies used by the production application. Maintain multi-region uptime monitoring to detect geographically widespread failures. Configure the Better Stack Status Page to automatically publish appropriate incident updates when production monitoring incidents occur. Consider adding application-level error monitoring alongside uptime monitoring to improve root-cause identification. Final Status Resolved The ChoyCraft website recovered at approximately 7:47 PM GMT+6, with the Better Stack incident automatically resolved at 7:50 PM GMT+6 following the recovery confirmation period. The incident lasted approximately 2 hours and 12 minutes.