We don't often ask for money. Just twice a year. This is one of those times. 

So, please, before you hit the "close" button on this box, would you consider a donation to keep Hymnary.org going? 

In April 2020, according to Google Analytics, our Hymnary website had roughly 1.5 million sessions from approximately 1 million users. Both numbers were up 40% from April 2019. Amazing. And what a blessing! But it is expensive to serve all of these people -- worship leaders, hymnologists, hymn lovers and more -- people like you who love hymns.

And we have limited sources of revenue. This fund drive is one critical source. 

So if you benefit from Hymnary.org, would you please consider a donation today? Even small amounts help, and they also let us know you're behind us and support what we do. 

You can make your tax-deductible contribution by sending a check to Hymnary.org at 3201 Burton SE, Grand Rapids, MI 49546, or you can click the Donate button below. 

On behalf of the entire Hymnary.org team,
Harry Plantinga

An Update on Hymnary Downtime

As many of you know, we had some issues with Hymnary this past weekend. The problems began on Saturday morning around 9:30 am EST with a hardware failure. Our on-call team began investigating right away and determined the issue was the storage server. From approx. 11 am to 8 pm on Saturday, we worked to get the storage server to work without losing any data but could not. We then had to do a factory-reset, and at midnight on Saturday, two of our team members began to work through the night to rebuild servers. Hymnary was mostly functional again by 3 am and thus able to be used by people on Sunday morning (our busiest time as of late) while other impacted websites (CCEL.org, preachingandworship.org and more) were back online by 6 am. Then, almost all day yesterday, members of our team continued restoring missing servers and services, got backups copied back and performed other important tasks. We are mostly functional again, and the good news (and blessing!) is that we lost very little production data thanks to our backup system and policies.


It looks like you are using an ad-blocker. Ad revenue helps keep us running. Please consider white-listing Hymnary.org or subscribing to eliminate ads entirely and help support Hymnary.org.