Last checked: 10 minutes ago
Get notified about any outages, downtime or incidents for Funraise and 1800+ other cloud vendors. Monitor 10 companies, for free.
Outage and incident data over the last 30 days for Funraise.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowOutlogger tracks the status of these components for Xero:
Component | Status |
---|---|
Campaign Sites | Active |
Donation Forms | Active |
Funraise Platform | Active |
Payments | Active |
Payments (Next Gen) | Active |
View the latest incidents for Funraise and check for official updates:
Description: This incident has been resolved.
Status: Resolved
Impact: Minor | Started At: Feb. 28, 2022, 8:08 p.m.
Description: A handful (~10) of donations using our new PayPal integration failed to process between 4:15am to 6:30am Pacific Standard Time due to a power loss at an Amazon data center. Amazon resolved the situation and donations are processing normally through that integration since 6:30am PST.
Status: Resolved
Impact: Minor | Started At: Dec. 22, 2021, noon
Description: A handful (~10) of donations using our new PayPal integration failed to process between 4:15am to 6:30am Pacific Standard Time due to a power loss at an Amazon data center. Amazon resolved the situation and donations are processing normally through that integration since 6:30am PST.
Status: Resolved
Impact: Minor | Started At: Dec. 22, 2021, noon
Description: Funraise for the does not use log4j for any of its native application code. Funraise identified one area of log4j use in a 3rd party component that we use for search engine functionality (ElasticSearch) that is hosted separately from the Funraise Platform core infrastructure. Funraise applied the appropriate initial patches and mitigation strategies on Dec 13 and continues to monitor the situation as new recommendations and patches are released and has found no evidence of exploit or attempted exploit in our application logs. Log4j was also identified in a 3rd party component powering our BI functionality. This functionality is also hosted separately from the Funraise core infrastructure and presents lowered risk of RCE. The vendor for that component patched and updated their infrastructure on Dec 16. Funraise continues to maintain a proactive security posture and undergoes annual analysis of our codebase and infrastructure by an independent security firm.
Status: Resolved
Impact: None | Started At: Dec. 13, 2021, 7 a.m.
Description: Funraise for the does not use log4j for any of its native application code. Funraise identified one area of log4j use in a 3rd party component that we use for search engine functionality (ElasticSearch) that is hosted separately from the Funraise Platform core infrastructure. Funraise applied the appropriate initial patches and mitigation strategies on Dec 13 and continues to monitor the situation as new recommendations and patches are released and has found no evidence of exploit or attempted exploit in our application logs. Log4j was also identified in a 3rd party component powering our BI functionality. This functionality is also hosted separately from the Funraise core infrastructure and presents lowered risk of RCE. The vendor for that component patched and updated their infrastructure on Dec 16. Funraise continues to maintain a proactive security posture and undergoes annual analysis of our codebase and infrastructure by an independent security firm.
Status: Resolved
Impact: None | Started At: Dec. 13, 2021, 7 a.m.
Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.