Incidents reported on status page for Fundy https://status.fundy.cloud/ https://d1lppblt9t2x15.cloudfront.net/logos/6871a69e3327cc1509892000ad522286.png https://status.fundy.cloud/ en https://status.fundy.cloud/incident/912080 Wed, 03 Jun 2026 14:24:00 -0000 https://status.fundy.cloud/incident/912080#cba967274896b1fd9b42b2a3f90aab671bf5809be1a32073a5b600e7f2d8346b At approximately 14:15 (UTC + 1) the domain registration for `fundy.cloud` lapsed, causing DNS resolution to fail for approximately 30 minutes. During this window, users whose DNS records had not yet expired from cache were unaffected, but anyone resolving the domain freshly was unable to reach our services. In some cases, requests were redirected to a registrar hosted domain expiry placeholder, and embedded Fundy forms on client websites failed to load (or fully function). ## Impact For roughly 30 minutes, the following were affected for any user or client without a cached DNS entry: * The Fundy website and API were unreachable. * Forms on client sites failed to render or function. * Some traffic was directed to the registrars domain expiry landing page. Users with cached DNS records experienced no disruption, so impact was partial rather than total. ## Root cause The domain registration reached its expiry date without renewal completing in time. This is an process gap on our side rather than a technical fault in the platform itself. ## Resolution We renewed the registration and confirmed correct DNS resolution. Service was fully restored once propagation completed for affected resolvers. ## Prevention To ensure this cannot recur, we are implementing the following: * Added external monitoring for domain expiry, with alerting ahead of any future expiry date. We apologise for the disruption and any inconvenience to you or your donors.