Incidents 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/900531 Wed, 20 May 2026 07:32:00 -0000 https://fundframe.betteruptime.com/incident/900531#9cb45e6f8d4f18410bec32a57841f568e54c1444292323e21c5cce915ed6fdbd 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 Cloudflare services were disrupted for a brief period