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

FinDock Core & Source packages Operational
File processing (ProcessingHub) Operational
(Online) Payment API / Payment Service Providers Operational
Notifications from Payment Service Providers (WebHub) Operational
Giving pages Operational
Sandboxes Operational
FinDock Knowledge Base 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.

Scheduled Maintenance

Sep 20, 2026 | Production Release - September '26 Sep 20, 2026 19:00-22:00 CEST

The FinDock September '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 Aug 18, 2026 - 10:36 CEST

Sep 17, 2026

No incidents reported today.

Sep 16, 2026

Resolved - Salesforce Rollout in Progress — Services Recovering
Salesforce has confirmed they are rolling out a fix for the earlier incident (status.salesforce.com/incidents/20004433). The rollout is progressing region by region, and services are returning to normal in regions where it has completed. Salesforce continues to monitor the rollout and is working on a permanent fix.
This also means FinDock is fully operational again.
What FinDock is doing:
Notifications affected during the incident have been resent, or are in the process of being resent.
We will close this incident but will continue monitoring the situation closely as Salesforce completes the rollout, and will provide a further update if anything changes.

Sep 16, 15:26 CEST
Monitoring - FinDock will automatically retry notifications where possible once the underlying Salesforce issue is resolved. We're closely monitoring the incident and will act as soon as Salesforce's systems are back to normal.
Sep 16, 12:16 CEST
Investigating - Salesforce is currently experiencing an incident (https://status.salesforce.com/incidents/20004433). Because FinDock runs natively on the Salesforce platform, this may affect some FinDock features while the incident is ongoing.

What this could mean for you:
- Donation/payment pages may be temporarily inaccessible, or fail to successfully initiate a payment
- Notifications may be delayed
- Payment processing within Salesforce may be affected
The full impact is still unclear, but it's most likely that this Salesforce incident means payments cannot be processed within Salesforce now.
What we're doing:
FinDock will automatically retry notifications where possible once the underlying Salesforce issue is resolved. We're closely monitoring the incident and will act as soon as Salesforce's systems are back to normal.
What you can do:
Please keep an eye on Salesforce's status page (https://status.salesforce.com/incidents/20004433) for the latest updates on the underlying incident.

Sep 16, 12:01 CEST

Sep 15, 2026

No incidents reported.

Sep 14, 2026

No incidents reported.

Sep 13, 2026

No incidents reported.

Sep 12, 2026

No incidents reported.

Sep 11, 2026

Completed - The scheduled maintenance has been completed.
Sep 11, 01:00 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Sep 11, 00:00 CEST
Scheduled - This hotfix adds new new fallback logic for Event Date and Event Date ISO8601 field data to safeguard against comparing null values when determining inbound report handling order. In certain scenarios, Guided Matching was getting into a loop that consumes the queueable limits of an org because the Is It My Turn rule could not determine handling order based on the notification event date.
Sep 10, 17:24 CEST

Sep 10, 2026

No incidents reported.

Sep 9, 2026

No incidents reported.

Sep 8, 2026

No incidents reported.

Sep 7, 2026

No incidents reported.

Sep 6, 2026

No incidents reported.

Sep 5, 2026

No incidents reported.

Sep 4, 2026

No incidents reported.

Sep 3, 2026

No incidents reported.