All Systems Operational

About This Site

Here you can find the actual status of our services. If there are any incidents known to us they will be posted and updated here. You can also find when we perform Maintenance to any of our systems. Subscribe to be notified of new Incidents, Maintenance and next releases. Have a look at https://docs.findock.com/release-notes for a full overview of our upcoming releases.

- For the status of your specific Salesforce instance, please visit https://status.salesforce.com/.
- For the status of Heroku, please visit https://status.heroku.com/.

If you wish to report an incident, please visit https://findock.com/support

Uptime over the past 90 days. View historical uptime.
FinDock Core & Source packages Operational
90 days ago
100.0 % uptime
Today
File processing (ProcessingHub) Operational
90 days ago
100.0 % uptime
Today
(Online) Payment API / Payment Service Providers Operational
90 days ago
100.0 % uptime
Today
Notifications from Payment Service Providers (WebHub) Operational
90 days ago
100.0 % uptime
Today
Giving pages Operational
90 days ago
100.0 % uptime
Today
Sandboxes Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Jan 25, 2026 | Production Release - January '26 Jan 25, 2026 20:00-22:00 CET

The FinDock January '26 release will be pushed to Production. During this event features will be available with no disruptions in services. The release notes will be available on docs.findock.com the Wednesday before the Sandbox release.
Posted on Dec 24, 2025 - 12:31 CET

Feb 22, 2026 | Sandbox Release - March '26 Feb 22, 2026 20:00-22:00 CET

The FinDock March '26 release will be pushed to Sandboxes. During this event features will be available with no disruptions in services. The release notes will be published on docs.findock.com the Wednesday before the Sandbox release.
Posted on Dec 24, 2025 - 12:33 CET

Mar 22, 2026 | Production Release - March '26 Mar 22, 2026 20:00-22:00 CET

The FinDock March '26 release will be pushed to Production. During this event features will be available with no disruptions in services. The release notes will be available on docs.findock.com the Wednesday before the Sandbox release.
Posted on Dec 24, 2025 - 12:34 CET

Apr 19, 2026 | Sandbox Release - May '26 Apr 19, 2026 20:00-22:00 CEST

The FinDock May '26 release will be pushed to Sandboxes. During this event features will be available with no disruptions in services. The release notes will be published on docs.findock.com the Wednesday before the Sandbox release.
Posted on Dec 24, 2025 - 12:35 CET

May 17, 2026 | Production Release - May '26 May 17, 2026 20:00-22:00 CEST

The FinDock May '26 release will be pushed to Production. During this event features will be available with no disruptions in services. The release notes will be available on docs.findock.com the Wednesday before the Sandbox release.
Posted on Dec 24, 2025 - 12:36 CET
Dec 29, 2025

No incidents reported today.

Dec 28, 2025
Dec 28, 2025 | Sandbox Release - January '26
Completed - The scheduled maintenance has been completed.
Dec 28, 22:00 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 28, 20:00 CET
Scheduled - The FinDock January '26 release will be pushed to Sandboxes. During this event features will be available with no disruptions in services. The release notes will be published on docs.findock.com the Wednesday before the Sandbox release.
Dec 24, 12:29 CET
Dec 27, 2025

No incidents reported.

Dec 26, 2025

No incidents reported.

Dec 25, 2025

No incidents reported.

Dec 24, 2025

No incidents reported.

Dec 23, 2025

No incidents reported.

Dec 22, 2025

No incidents reported.

Dec 21, 2025

No incidents reported.

Dec 20, 2025

No incidents reported.

Dec 19, 2025

No incidents reported.

Dec 18, 2025

No incidents reported.

Dec 17, 2025
HOTFIX - Payment collection error corrections
Completed - The scheduled maintenance has been completed.
Dec 17, 20:46 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 17, 20:00 CET
Scheduled - The enhanced logging for our queueable framework from the Nov. 25 release led to unexpected changes in how certain exceptions are handled. This resulted in some installments potentially being left out of the schedule scope or otherwise failing unexpectedly. This hotfix resolves the issues for the impacted packages: Core (fix for Fundraising and NPSP), Gift Aid, and GoCardless. FinDock Support is reaching out to affected customers directly with more details.

With the introduction of Stripe Pre-Authorized Debit (PAD) support in the Nov. 25 release, the Custom Reference field from Mandate was added to all Stripe callouts. This caused recurring payment collections to fail if Custom Reference was already used for other purposes. This hotfix adjusts the callout message to only include Mandate Custom Reference for the PAD payment method. ACTION REQUIRED FOR STRIPE: If you use Custom Reference on Mandate for payment methods other than PAD, check for failed installments of recurring payments (with payment method other than PAD) since Nov. 30th. If you identify such installments, change the status to Pending recollection and run a new payment schedule to collect the installments.
Dec 17, 17:01 CET
Dec 16, 2025

No incidents reported.

Dec 15, 2025
HOTFIX - Schedule validation failure
Completed - The scheduled maintenance has been completed.
Dec 15, 19:30 CET
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 15, 18:30 CET
Scheduled - This hotfix resolves an issue that caused some schedule runs to get stuck in the Validating phase. The issue was caused by logging enhancements for our queueable framework introduced in the Nov. '25 release. If a schedule run for a payment processor-method combination that uses in-line validation included over 75k records, the new logging could result in too many platform events, causing the in-line validation to stall. ACTION REQUIRED AFTER HOTFIX: If you have a schedule stuck in Validating, you need to set the status back to Generated to trigger validation again. Alternatively, use the Data Quality component on the schedule. Once the component shows no errors, manually set the schedule status to Validated.
Dec 15, 16:36 CET
← Incident History Powered by Atlassian Statuspage