Incidents and maintenance reported on status page for FundFrame ApS https://fundframe.betteruptime.com/ https://d1lppblt9t2x15.cloudfront.net/logos/8cb0b0f6ae634468dc4ba855f2cabb9b.png https://fundframe.betteruptime.com/ en https://fundframe.betteruptime.com/incident/1078017 Wed, 30 Sep 2026 07:46:00 -0000 https://fundframe.betteruptime.com/incident/1078017#411ac4ed1ca0b59b31c88b675aee0f7eac280ee026c8a2ac32c59b4a7c3b1975 Incident FundFrame One recovered. On 30 September 2026, the FundFrame platform was unavailable for approximately 8 minutes. The interruption was caused by a network configuration change at our hosting provider, Railway, which temporarily prevented new connections from reaching hosted services. The issue resolved automatically, and the platform has been fully operational since. No action is required from users. The incident did not involve our application or data, and no data was lost or affected. Our monitoring detected the outage immediately, and we followed the incident until full recovery was confirmed. Railway is conducting a root cause analysis. We will review their findings and assess whether any further measures are appropriate on our side. We apologise for any inconvenience this may have caused. https://fundframe.betteruptime.com/incident/1078017 Wed, 30 Sep 2026 07:38:44 -0000 https://fundframe.betteruptime.com/incident/1078017#990c1b4a0f59a0fdc541653efa6fc5384a9e9758b7d96217ca88e5f1e7aefecb Incident FundFrame One went down. https://fundframe.betteruptime.com/incident/916041 Sat, 06 Jun 2026 19:16:37 -0000 https://fundframe.betteruptime.com/incident/916041#cba96110a4fcdacc0d372fda9e583d7273b2e366e17adf11625c35db57370548 Incident FundFrame One recovered. https://fundframe.betteruptime.com/incident/916041 Sat, 06 Jun 2026 19:09:23 -0000 https://fundframe.betteruptime.com/incident/916041#6a8395543d192fbcd61d89626f4ee4ec8628bb6a47ad59b8f8b7ab1ed9a6206c Incident FundFrame One went down. https://fundframe.betteruptime.com/incident/900531 Wed, 20 May 2026 07:32:00 -0000 https://fundframe.betteruptime.com/incident/900531#9cb45e6f8d4f18410bec32a57841f568e54c1444292323e21c5cce915ed6fdbd Incident On the night of May 20 at approximately 00:20 CEST, our infrastructure provider Railway experienced a widespread service disruption after Google Cloud automatically suspended Railway's account without prior notice. This caused Railway's API, dashboard, control plane, and customer-hosted workloads to go offline. FundFrame services, including FundFrame One, were unreachable for approximately 4 hours during the night (roughly 00:20 to ~04:00 CEST, May 20). Users would have encountered "no healthy upstream" errors or been unable to load the platform entirely. Root cause: Google Cloud placed Railway's account into "restricted" status, which removed their cloud VMs, CloudSQL instance, and API. Since Railway's distributed edge proxy depends on the API, all hosted workloads were affected. Railway has confirmed services are recovering. Their full post-mortem is pending. Reference: https://status.railway.com/ and https://station.railway.com/community/what-we-know-so-far-may-19th-2026-86354cdd No FundFrame data loss is expected. The issue was entirely on the infrastructure provider side and thus subject to exclusions under SLA. https://fundframe.betteruptime.com/incident/788178 Fri, 05 Dec 2025 09:11:00 -0000 https://fundframe.betteruptime.com/incident/788178#b65423f97eba95e837a8e3564ee615d75025186e02f2b796fcecf10644f78f55 Incident Cloudflare services were disrupted for a brief period