All Systems Operational

Donation Forms Operational
RaiseNow Manager Operational
RaiseNow Hub Operational
Payment Services Operational
CRM & Accounting System Integrations Operational
Peer-to-Peer & Employee Giving Platforms Operational
Payment Providers ? Operational
TWINT Operational
Datatrans Operational
Ingenico Collect Operational
PayPal Operational
Stripe Operational
Adyen Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance

Scheduled Maintenance

Scheduled Database Maintenance Apr 16, 2025 07:00-13:00 CEST

On 2025-04-16 we'll performing some maintenance work on our infrastructure from 07:00 CEST until 09:00 CEST. During the maintenance period, short connection interruptions might occur. No further impact is expected.
Posted on Apr 03, 2025 - 16:14 CEST
Apr 4, 2025

No incidents reported today.

Apr 3, 2025

No incidents reported.

Apr 2, 2025

No incidents reported.

Apr 1, 2025

No incidents reported.

Mar 31, 2025
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 19:39 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 19:33 CEST
Degraded performance on Manager Platform
Resolved - This incident has been resolved.
Mar 31, 13:33 CEST
Identified - We are aware of an issue affecting our Manager Platform and currently working on fixing its root cause.
You can expect an update on the incident in the next hour.

Affected components
- you might see timeouts while browsing manage.raisenow.com
- you might see timeouts while querying our search API on https://api.raisenow.com/epayment/api//transactions/search
Mar 31, 11:06 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 13:22 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 13:13 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 13:12 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 13:12 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 13:12 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 13:12 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 12:42 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 12:42 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 12:12 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 12:11 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 11:41 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 11:41 CEST
Identified - The issue has been identified and a fix is being implemented.
Mar 31, 11:12 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 11:11 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 13:20 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 13:15 CEST
Update - We have identified the cause of the incident and are actively working on a resolution. As soon as a fix has been implemented, you'll find an update here.
Mar 31, 13:15 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 12:45 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 12:44 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 12:42 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 12:37 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 12:36 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 12:31 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 12:29 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 12:20 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 12:17 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 12:13 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 12:08 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 12:05 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 11:45 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 11:43 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 11:31 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 11:28 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 11:27 CEST
Incident detected
Resolved - This incident has been resolved. We apologize for the inconvenience and thank you for your understanding. We are continuously working on improvements to make our services better.
Mar 31, 10:51 CEST
Investigating - We are aware of an issue affecting our services and currently working on identifying its root cause.
You can expect an update on the incident in the next hour.
Mar 31, 10:42 CEST
Mar 30, 2025

No incidents reported.

Mar 29, 2025

No incidents reported.

Mar 28, 2025

No incidents reported.

Mar 27, 2025

No incidents reported.

Mar 26, 2025

No incidents reported.

Mar 25, 2025

No incidents reported.

Mar 24, 2025

No incidents reported.

Mar 23, 2025

No incidents reported.

Mar 22, 2025

No incidents reported.

Mar 21, 2025

No incidents reported.

← Incident History Powered by Atlassian Statuspage