We work really hard to keep your system up and running, but sometimes we experience some hiccups. When that happens, we want you to be in the know. Outages, downtime, service interruptions, and other technical difficulties will be reported here.

Event Attendance Reminder Delays

On Friday, February 3, we made an update to one of our servers that handles sending out attendance reminder emails for upcoming events.  Due to an edge case that was not present during our initial testing, the server caused the emails to backup and not be sent out over the weekend. We have rolled back our changes and our engineers have restored attendance reminder delivery.

Read More

Service Interruptions January 9, 2016

On the evening of January 9, 2016 at approximately 9:30pm MST, our engineers became aware of the inability for church partners to log in to their sites, causing a service interruption. We immediately started investigating the cause and after following our process of diagnosis, we identified that the problem was not related to software and was likely hardware related. Upon discovering the problem, our engineers were immediately dispatched to our primary data center.

Read More

Hardware Maintenance - Friday, August 12, 2016

On Friday, August 12, 2016, at 11 pm MDT, we will be performing maintenance on our systems to address intermittent service interruptions over the last three days. We will be upgrading some of our network hardware over a 2-hour window and as a result, some church partners may experience a loss of session (being logged out) or their site being unavailable for up to 5 minutes. This work is centered around troubleshooting and hardware rotation, and we will be updating our @CCBTECH Twitter account with details as we begin and complete our maintenance.

Read More

DDoS Attack on June 21

On June 21, 2016, at approximately 8:30pm MDT, Church Community Builder was the target of a Distributed Denial of Service attack. Our monitoring systems alerted our engineers to the issue, and we immediately took action and tweeted to our @CCBTech Twitter account that we were aware of the problem. 

Read More