Springbook Outage History

Started Oct 01, 2026, 03:56 PM UTC· resolved Oct 01, 2026, 04:48 PM UTC

1. investigating Oct 01, 2026, 03:56 PM UTC

   We are currently seeing reports take an extended time to move from scheduled to processing.

2. resolved Oct 01, 2026, 04:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 28, 2026, 05:45 PM UTC· resolved Jul 28, 2026, 06:39 PM UTC

1. monitoring Jul 28, 2026, 05:45 PM UTC

   We have identified an issue causing slow performance on one of our SQL servers. Performance should be returning to normal soon.

2. monitoring Jul 28, 2026, 05:51 PM UTC

   This was causing slow performance when using the application. This was also causing jobs/reports to take longer to start processing.

3. resolved Jul 28, 2026, 06:39 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 17, 2026, 03:49 PM UTC· resolved Jul 17, 2026, 05:37 PM UTC

1. monitoring Jul 17, 2026, 03:49 PM UTC

   We are monitoring an issue with IVR payments from Selectron.

2. monitoring Jul 17, 2026, 03:59 PM UTC

   Selectron has notified us that the issue has been resolved and processing is returning to normal.

3. resolved Jul 17, 2026, 05:37 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 06, 2026, 03:09 PM UTC· resolved Jul 06, 2026, 04:12 PM UTC

1. investigating Jul 06, 2026, 03:09 PM UTC

   We are currently investigating this issue.

2. monitoring Jul 06, 2026, 03:17 PM UTC

   A fix has been implemented and we are monitoring the results.

3. resolved Jul 06, 2026, 04:12 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 06, 2026, 02:58 PM UTC· resolved Jul 06, 2026, 07:43 PM UTC

1. investigating Jul 06, 2026, 02:58 PM UTC

   We are currently investigating this issue.

2. monitoring Jul 06, 2026, 03:16 PM UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring Jul 06, 2026, 04:12 PM UTC

   We are continuing to monitor for any further issues.

4. investigating Jul 06, 2026, 04:35 PM UTC

   The issue is happening again. We are continuing to investigate.

5. monitoring Jul 06, 2026, 04:56 PM UTC

   A fix has been implemented and we are monitoring the results.

6. monitoring Jul 06, 2026, 05:59 PM UTC

   We are continuing to monitor for any further issues.

7. resolved Jul 06, 2026, 07:43 PM UTC

   We have identified the root cause and have implemented a change.

Read the full incident report →

Started Jun 24, 2026, 12:15 PM UTC· resolved Jun 24, 2026, 01:43 PM UTC

1. investigating Jun 24, 2026, 12:15 PM UTC

   We are currently investigating an issue preventing login to Springbrook Cirrus, Enterprise and Tableau.

2. investigating Jun 24, 2026, 01:03 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 24, 2026, 01:13 PM UTC

   We have identified issue and have implemented a fix. We will continue to monitor the situation.

4. resolved Jun 24, 2026, 01:43 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 21, 2026, 04:45 PM UTC· resolved May 22, 2026, 03:40 AM UTC

1. investigating May 21, 2026, 04:45 PM UTC

   The issue from yesterday is now impacting all users.

2. identified May 21, 2026, 05:39 PM UTC

   The issue has been identified and a fix is being implemented.

3. identified May 21, 2026, 06:10 PM UTC

   In an effort to improve our environment, we upgraded the servers. This has uncovered an issue with the printers. This issue does not appear in our staging environment. It also did not appear in the live environment initially. We have found a fix for the issue, which will require us to migrate everyone to new servers again. We are in the process of building this out. The new servers with the fix will be available by the end of day today. We will migrate everyone overnight.

4. resolved May 22, 2026, 03:40 AM UTC

   Server migrations have completed and testing shows that printing issues have been resolved. We will continue to monitor throughout the day tomorrow.

Read the full incident report →

Started May 20, 2026, 03:58 PM UTC· resolved May 20, 2026, 07:55 PM UTC

1. investigating May 20, 2026, 03:58 PM UTC

   We are investigating an issue with printing in Springbrook Express impacting a subset of users. Printing is offline for these users while we troubleshoot.

2. identified May 20, 2026, 04:59 PM UTC

   Impacted agencies will have a short downtime to implement a fix. This will occur in the next 2 hours.

3. resolved May 20, 2026, 07:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Apr 29, 2026, 03:25 PM UTC· resolved Apr 29, 2026, 08:13 PM UTC

1. investigating Apr 29, 2026, 03:25 PM UTC

   Half our customers are unable to access Express currently. Our engineering team is investigating.

2. identified Apr 29, 2026, 04:41 PM UTC

   We have a cause identified and are working to correct it.

3. identified Apr 29, 2026, 05:43 PM UTC

   We are continuing to work on a fix.

4. resolved Apr 29, 2026, 08:13 PM UTC

   The issue has been resolved.

Read the full incident report →

Started Apr 28, 2026, 07:10 PM UTC· resolved May 05, 2026, 09:45 PM UTC

1. investigating Apr 28, 2026, 07:10 PM UTC

   We are currently investigating an issue with one of the Springbrook Express app servers. This is impacting a subset of customers who use the affectedd app server.

2. monitoring Apr 28, 2026, 07:36 PM UTC

   A fix has been implemented, and we are continuing to investigate the root cause. We will monitor the situation closely and update as progress is made to full resolution.

3. resolved May 05, 2026, 09:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 26, 2026, 02:30 PM UTC· resolved Mar 26, 2026, 03:44 PM UTC

1. investigating Mar 26, 2026, 02:30 PM UTC

   We are currently investigating this issue.

2. investigating Mar 26, 2026, 02:32 PM UTC

   The Portal is now accessible, we are still looking to see what happened.

3. investigating Mar 26, 2026, 02:55 PM UTC

   We are continuing to investigate this issue.

4. resolved Mar 26, 2026, 03:44 PM UTC

   We are still investigating the root cause.

Read the full incident report →

Started Mar 12, 2026, 08:14 PM UTC· resolved Mar 12, 2026, 10:18 PM UTC

1. investigating Mar 12, 2026, 08:14 PM UTC

   We are currently investigating this issue.

2. investigating Mar 12, 2026, 08:23 PM UTC

   We are rebooting one of the servers in about 1 minute. This should assist in getting things running again.

3. monitoring Mar 12, 2026, 08:48 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Mar 12, 2026, 10:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 03, 2026, 05:28 PM UTC· resolved Mar 03, 2026, 09:39 PM UTC

1. monitoring Mar 03, 2026, 05:28 PM UTC

   CivicPay has been notified of an ongoing service disruption impacting FedACH® Services at the Federal Reserve. As a result, ACH transactions (including Same-Day ACH) may be delayed in processing and settlement today. According to the Federal Reserve’s service status page FedACH Services is experiencing delays associated with internal systems processing. - The FedACH Services application is currently offline while they work toward resolution. - File distribution and settlement for the first same-day ACH window are delayed. - File distribution for the first ACH window for future-dated items is also delayed. - Customers are advised not to resend origination files if acknowledgements are pending. What this means for you ACH payments submitted through Xpress Bill Pay may take longer than usual to process, post, or settle at receiving financial institutions. You may see pending ACH items that normally would have completed by now. Some ACH-related reports and acknowledgements may arrive later than expected. Federal Reserve Service Status: https://www.frbservices.org/app/status/outage.do?oId=145787

2. resolved Mar 03, 2026, 09:39 PM UTC

   We are pleased to inform you that the issues causing delays in ACH settlement activity have been resolved. The Federal Reserve has addressed the problem, and Bluefin’s processing systems continue to operate normally. We appreciate your understanding.

Read the full incident report →

Started Mar 03, 2026, 01:36 PM UTC· resolved Mar 03, 2026, 04:53 PM UTC

1. investigating Mar 03, 2026, 01:36 PM UTC

   We have confirmed an issue with signing into Springbrook v7. We are currently investigating this issue.

2. investigating Mar 03, 2026, 02:06 PM UTC

   We are continuing to investigate this issue.

3. investigating Mar 03, 2026, 02:54 PM UTC

   We are continuing to investigate this issue.

4. monitoring Mar 03, 2026, 03:26 PM UTC

   A fix has been implemented and we are currently monitoring the results.

5. resolved Mar 03, 2026, 04:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 17, 2026, 02:22 PM UTC· resolved Feb 17, 2026, 06:48 PM UTC

1. investigating Feb 17, 2026, 02:22 PM UTC

   KVS Hosting Customers are currently unable to connect to the hosting environment. We are currently investigating this issue.

2. investigating Feb 17, 2026, 03:42 PM UTC

   We are continuing to investigate this issue.

3. monitoring Feb 17, 2026, 05:11 PM UTC

   We have identified the issue and a fix has been implemented. We are now monitoring connections to confirm the issue is resolved.

4. resolved Feb 17, 2026, 06:48 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 05, 2026, 04:00 PM UTC· resolved Feb 05, 2026, 04:21 PM UTC

1. investigating Feb 05, 2026, 04:00 PM UTC

   We are currently investigating an availability issue with Springbrook Express related to excessive application errors.

2. identified Feb 05, 2026, 04:03 PM UTC

   The issue has been identified.

3. monitoring Feb 05, 2026, 04:10 PM UTC

   A fix has been implemented. Users with existing sessions will need to re-login to the application.

4. resolved Feb 05, 2026, 04:21 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 15, 2026, 02:18 PM UTC· resolved Jan 15, 2026, 05:00 PM UTC

1. investigating Jan 15, 2026, 02:18 PM UTC

   We are currently investigating this issue.

2. investigating Jan 15, 2026, 02:18 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jan 15, 2026, 03:20 PM UTC

   A fix has been implemented and we are monitoring the results.

4. resolved Jan 15, 2026, 05:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 10, 2026, 06:41 PM UTC· resolved Jan 10, 2026, 09:54 PM UTC

1. monitoring Jan 10, 2026, 06:41 PM UTC

   Microsoft Azure is having service health issues. Springbrook Express is currently operational but may be impacted. We are continuing to monitor the situation.

2. resolved Jan 10, 2026, 09:54 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jan 07, 2026, 01:55 PM UTC· resolved Jan 07, 2026, 02:33 PM UTC

1. monitoring Jan 07, 2026, 01:55 PM UTC

   A fix has been implemented and we're monitoring the status

2. resolved Jan 07, 2026, 02:33 PM UTC

   Issue resolved - No further errors have occurred.

Read the full incident report →

Started Dec 16, 2025, 04:03 PM UTC· resolved Dec 16, 2025, 04:13 PM UTC

1. investigating Dec 16, 2025, 04:03 PM UTC

   We are currently re-deploying the Cirrus application. This will result in a brief disruption while the application service rotates.

2. investigating Dec 16, 2025, 04:04 PM UTC

   We are continuing to investigate this issue.

3. resolved Dec 16, 2025, 04:13 PM UTC

   Cirrus re-deployment complete.

Read the full incident report →

Started Dec 05, 2025, 09:10 AM UTC· resolved Dec 05, 2025, 09:24 AM UTC

1. investigating Dec 05, 2025, 09:10 AM UTC

   The availability of Springbrook and PUBLIQ services are currently being impacted by a Cloudflare outage. We are monitoring the situation as Cloudflare investigates the issue.

2. monitoring Dec 05, 2025, 09:18 AM UTC

   Cloudflare has implemented a fix and services have become available again. We will continue to monitor the incident.

3. resolved Dec 05, 2025, 09:24 AM UTC

   Cloudflare has indicated the incident has been resolved.

Read the full incident report →

Started Nov 12, 2025, 05:21 PM UTC· resolved Nov 13, 2025, 03:55 PM UTC

1. investigating Nov 12, 2025, 05:21 PM UTC

   We are getting reports of slow response times in Springbrook cloud. Cirrus and Enterprise are both impacted.

2. investigating Nov 12, 2025, 06:40 PM UTC

   We are continuing to investigate this issue.

3. identified Nov 12, 2025, 07:51 PM UTC

   The issue has been identified and a fix is being implemented.

4. monitoring Nov 12, 2025, 09:16 PM UTC

   A fix has been implemented and we are monitoring the results.

5. monitoring Nov 12, 2025, 09:17 PM UTC

   We are continuing to monitor for any further issues.

6. resolved Nov 13, 2025, 03:55 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Nov 06, 2025, 05:38 PM UTC· resolved Nov 06, 2025, 09:59 PM UTC

1. identified Nov 06, 2025, 05:38 PM UTC

   We are seeing issues with billing files moving from Springbrook Cloud/Cirrus to Xpress Bill Pay. The cause has been identified and a fix is being developed. Files are able to be transferred to Xpress Bill Pay manually.

2. monitoring Nov 06, 2025, 06:16 PM UTC

   A fix has been put in place. We will be monitoring to confirm there are success uploads.

3. monitoring Nov 06, 2025, 06:19 PM UTC

   We are continuing to monitor for any further issues.

4. resolved Nov 06, 2025, 09:59 PM UTC

   It's confirmed as working.

Read the full incident report →

Started Oct 15, 2025, 07:16 PM UTC· resolved Oct 15, 2025, 10:59 PM UTC

1. investigating Oct 15, 2025, 07:16 PM UTC

   Please be aware that our phone system provider is currently experiencing a service disruption affecting both inbound and outbound calls. You can still reach us via email at [email protected].

2. investigating Oct 15, 2025, 08:24 PM UTC

   Update - The service provider's technical team is working to restore inbound and outbound calling services. We will provide further updates as we receive them.

3. investigating Oct 15, 2025, 09:59 PM UTC

   Update - Our service provider is continuing to work on restoring inbound and outbound calling services. We will provide further updates as we receive them.

4. resolved Oct 15, 2025, 10:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Oct 02, 2025, 05:03 PM UTC· resolved Oct 02, 2025, 08:22 PM UTC

1. investigating Oct 02, 2025, 05:03 PM UTC

   Approximately half the agencies are impacted. Those agencies are not able to use the service while this is occering

2. investigating Oct 02, 2025, 05:39 PM UTC

   We are continuing to work to restore the service.

3. monitoring Oct 02, 2025, 05:55 PM UTC

   The service is now online. We are continuing to monitor as we investigate the root cause.

4. resolved Oct 02, 2025, 08:22 PM UTC

   This incident has been resolved.

Read the full incident report →