GiveGab Enterprise Outage History

Started Jul 11, 2026, 02:07 PM UTC· resolved Jul 11, 2026, 04:22 PM UTC

1. investigating Jul 11, 2026, 02:07 PM UTC

   We are aware that some users are experiencing issues logging into Apricot. Our team is actively investigating the root cause and will provide updates as more information becomes available. We apologize for any disruption this may cause.

2. monitoring Jul 11, 2026, 02:34 PM UTC

   The login issue affecting Apricot has been resolved. Our team will continue to monitor to ensure everything remains stable.

3. resolved Jul 11, 2026, 04:22 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jul 01, 2026, 12:55 PM UTC· resolved Jul 01, 2026, 05:58 PM UTC

1. investigating Jul 01, 2026, 12:55 PM UTC

   We are aware of an issue affecting Salsa Engage where users are unable to send emails. We are currently investigating this issue. Please continue to monitor this page for further updates.

2. investigating Jul 01, 2026, 01:59 PM UTC

   We are actively working on a solution to address this issue. It is a top priority and we are hoping to resolve it as soon as possible. Please continue to monitor this page for further updates.

3. monitoring Jul 01, 2026, 02:54 PM UTC

   The needed fix was implemented and tested. While the issue has been addressed, we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

4. resolved Jul 01, 2026, 05:58 PM UTC

   The incident has been successfully resolved.

Read the full incident report →

Started Jun 30, 2026, 02:17 PM UTC· resolved Jun 30, 2026, 08:50 PM UTC

1. investigating Jun 30, 2026, 02:17 PM UTC

   We are currently investigating an issue with running reports on Results. We are reviewing this as a top priority and hope to resolve as soon as possible. Please monitor this page for further issues.

2. investigating Jun 30, 2026, 05:19 PM UTC

   We are still actively investigation the Results reporting issue. As a workaround option, reports can be ran directly from the Results Dashboard, while we work on full resolution. Please continue to monitor this page for further updates.

3. identified Jun 30, 2026, 05:59 PM UTC

   The root cause of the issue has been identified and we are currently working on a fix to remediate. As a workaround option, reports can be ran directly from the Results Dashboard. Please continue to monitor this page for further updates.

4. monitoring Jun 30, 2026, 08:04 PM UTC

   A fix has been implemented and successfully tested. While the issue has been addressed, we will continue to monitor closely to ensure there is no regression. Please continue to monitor this page for further updates.

5. resolved Jun 30, 2026, 08:50 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 30, 2026, 01:08 PM UTC· resolved Jun 30, 2026, 08:50 PM UTC

1. investigating Jun 30, 2026, 01:08 PM UTC

   We are currently investigating an issue that is causing connection and performance issues in CyberGrants' SandBox environment. We are working to resolve as quickly as possible. Please monitor this page for further updates.

2. investigating Jun 30, 2026, 02:36 PM UTC

   We are continuing to review the issue impacting the performance of CyberGrants' SandBox environment. We are working to resolve as quickly as possible. Please monitor this page for further updates.

3. monitoring Jun 30, 2026, 04:16 PM UTC

   We have implemented a fix and have completed testing. While the issue has been addressed, we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

4. resolved Jun 30, 2026, 08:50 PM UTC

   This incident has been resolved.

5. postmortem Jul 13, 2026, 08:15 PM UTC

   **Issue Summary:** On June 30th, 2026, nightly maintenance jobs consumed more than usual disk usage and ran into normal business hours. **Root Cause:** The nightly jobs scanned more than usual information this scan caused high disk IO/throughput stressing the storage system. This additional load caused slow response times and in some cases timeouts/errors for end users. **Prevention:** We increased the available throughput of the disks, and have reviewed the nightly jobs for additional optimization improvements.

Read the full incident report →

Started Jun 29, 2026, 06:37 PM UTC· resolved Jun 29, 2026, 06:45 PM UTC

1. monitoring Jun 29, 2026, 06:37 PM UTC

   This is a test of the statuspage functionality

2. resolved Jun 29, 2026, 06:45 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 29, 2026, 02:02 PM UTC· resolved Jun 30, 2026, 07:14 PM UTC

1. investigating Jun 29, 2026, 02:02 PM UTC

   We are aware of an issue affecting Insights Dashboards where the information is not populating correctly. We are currently investigating this issue.

2. investigating Jun 29, 2026, 06:23 PM UTC

   We remain active in our investigation of this issue. It is a top priority and we are working to resolve it as soon as possible. Please continue to monitor this page for further updates.

3. identified Jun 29, 2026, 08:46 PM UTC

   We have identified the issue and we are currently working on a solution to fully remediate. It may some time before data is current, but we are working to resolve as quickly as possible. Please continue to monitor this page for additional updates.

4. monitoring Jun 30, 2026, 01:05 PM UTC

   The needed fix was implemented and tested. While the issue has been addressed, we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

5. resolved Jun 30, 2026, 07:14 PM UTC

   The incident has been successfully resolved.

6. postmortem Jul 13, 2026, 08:17 PM UTC

   **Issue Summary:** On June 30th, 2026, nightly maintenance jobs consumed more than usual disk usage and ran into normal business hours. **Root Cause:** The nightly jobs scanned more than usual information this scan caused high disk IO/throughput stressing the storage system. This additional load caused slow response times and in some cases timeouts/errors for end users. **Prevention:** We increased the available throughput of the disks, and have reviewed the nightly jobs for additional optimization improvements.

Read the full incident report →

Started Jun 25, 2026, 11:13 PM UTC· resolved Jun 26, 2026, 02:21 AM UTC

1. investigating Jun 25, 2026, 11:13 PM UTC

   We are investigating an issue causing some Users to see intermittent errors when editing Online Actions. The issue does not affect form submissions.

2. monitoring Jun 26, 2026, 12:18 AM UTC

   As of 8:18 PM, the earlier issue with errors in Online Actions has been resolved. If you are still experiencing issues, please log out and log back in. We will continue to monitor.

3. resolved Jun 26, 2026, 02:21 AM UTC

   As of 8:18 PM, the earlier issue with errors in Online Actions has been resolved. If you are still experiencing issues, please log out and log back in. We will continue to monitor.

Read the full incident report →

Started Jun 22, 2026, 02:57 PM UTC· resolved Jun 22, 2026, 07:06 PM UTC

1. investigating Jun 22, 2026, 02:57 PM UTC

   We are actively investigating reported issues impacting user login and general slowness on both the Apricot and ETO applications. This is being reviewed as a top priority. Please monitor this page for additional updates.

2. identified Jun 22, 2026, 03:35 PM UTC

   Cloudflare is reporting an issue that is impacting traffic. Some users connecting in North America, or accessing services in Europe, may see connection issues and increased latency. While the Apricot and ETO applications are up and running, users may be impacted based on the external issue reported by Cloudflare. We will provide further updates as they become available from Cloudflare, but you can also monitor Cloudflare's Status Page at: https://www.cloudflarestatus.com.

3. monitoring Jun 22, 2026, 05:33 PM UTC

   Cloudflare has remediated the external issue and traffic has returned to normal. We will continue to monitor to ensure there is no regression. Please continue to monitor this page for additional updates.

4. resolved Jun 22, 2026, 07:06 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 18, 2026, 06:10 PM UTC· resolved Jun 18, 2026, 11:00 PM UTC

1. investigating Jun 18, 2026, 06:10 PM UTC

   We are currently investigating an issue that is impacting some users from accessing documents. This is a top priority and we are working to resolve as soon as possible. Please monitor this page for further updates.

2. identified Jun 18, 2026, 06:36 PM UTC

   The root cause has been identified and a fix is scheduled to be deployed this evening. Please continue to monitor this page for further updates.

3. resolved Jun 18, 2026, 11:00 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 18, 2026, 04:10 PM UTC· resolved Jun 18, 2026, 08:56 PM UTC

1. investigating Jun 18, 2026, 04:10 PM UTC

   We are currently investigating an issue affecting NGP where data entered or updated today is not being reflected on disclosure reports for some users. We will provide an update as soon as possible.

2. resolved Jun 18, 2026, 08:56 PM UTC

   As of 4:45pm eastern, the earlier issue that caused data entered or updated today to not be reflected on disclosure reports has been resolved. We are continuing to monitor for any further issues.

Read the full incident report →

Started Jun 15, 2026, 02:16 PM UTC· resolved Jun 16, 2026, 12:59 PM UTC

1. monitoring Jun 15, 2026, 02:16 PM UTC

   There was an issue that resulted in delays with the processing of some scheduled jobs. We are now working on the processing of the pending jobs and expect to be current shortly.

2. resolved Jun 16, 2026, 12:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 15, 2026, 04:46 AM UTC· resolved Jun 16, 2026, 03:04 PM UTC

1. investigating Jun 15, 2026, 04:46 AM UTC

   As of 8:00 AM AEST, Penelope is experiencing intermittent disruptions for some users in the Australia and New Zealand regions. We will provide an update and an estimated time for resolution as soon as possible.

2. identified Jun 15, 2026, 05:24 AM UTC

   The cause of the issue has been identified, and our team is actively implementing a solution.

3. identified Jun 15, 2026, 04:25 PM UTC

   We are actively working on resolving the issue and expect it to be fully resolved in the next 24 hours.

4. resolved Jun 16, 2026, 03:04 PM UTC

   The incident has been successfully resolved.

Read the full incident report →

Started Jun 11, 2026, 08:57 PM UTC· resolved Jun 12, 2026, 01:23 PM UTC

1. investigating Jun 11, 2026, 08:57 PM UTC

   We are currently aware of an issue when attempting to submit volunteer hours and we are working on a resolution. Please monitor this page for updates.

2. monitoring Jun 11, 2026, 10:03 PM UTC

   A fix has been implemented and successfully tested. While the issue has been remediated, we will monitor closely to ensure there is no regression. Please continue to monitor this page for further updates.

3. resolved Jun 12, 2026, 01:23 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 11, 2026, 03:01 PM UTC· resolved Jun 11, 2026, 07:53 PM UTC

1. investigating Jun 11, 2026, 03:01 PM UTC

   We are currently aware of an issue with searching for organizations by address, when logging volunteer hours. This is a top priority and we are working to resolve the issue as soon as possible. Please monitor this page for further updates.

2. investigating Jun 11, 2026, 06:12 PM UTC

   We are still working on a resolution to address this issue. We apologize for the impact and appreciate your patience as we continue to implement a fix. Please continue to monitor this page for further updates.

3. resolved Jun 11, 2026, 07:53 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 08:09 PM UTC· resolved Jun 01, 2026, 11:35 PM UTC

1. identified Jun 01, 2026, 08:09 PM UTC

   NPO Hub is temporarily offline as we work through a needed updated. This does not impact the CyberGrants application. Please monitor this page for further updates.

2. resolved Jun 01, 2026, 11:35 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Jun 01, 2026, 07:55 PM UTC· resolved Jun 02, 2026, 09:01 PM UTC

1. investigating Jun 01, 2026, 07:55 PM UTC

   We are currently addressing an issue that is blocking users from accessing NPO Hub. We are working to remediate this as soon as possible. Please monitor this page for updates.

2. investigating Jun 01, 2026, 07:55 PM UTC

   We are continuing to investigate this issue.

3. monitoring Jun 01, 2026, 11:46 PM UTC

   A fix has been implemented and successfully tested. NPO Hub is now accessible, but you may need to clear your cache if you experience any errors. Cache clearing instructions are provided below: Google Chrome (Desktop) Go to Settings > Privacy and security > Third-party cookies. Select See all site data and permissions. Search for the website name in the top-right search bar. Click the Delete (trash can) icon next to the site and confirm. Microsoft Edge Go to Settings > Cookies and site permissions > Manage and delete cookies and site data. Select See all cookies and site data. Search for the site and click the down arrow to its right, then select Delete. Mozilla Firefox Go to Settings > Privacy & Security. Find the Cookies and Site Data section and click Manage Data.... Search for the website, select it, and click Remove Selected (or Remove All Shown). Click Save Changes and confirm Safari (Mac) In the menu bar, choose Safari > Settings (or Preferences). Click the Privacy tab, then click Manage Website Data.... Search for the website, select it, and click Remove Mobile (Android & iOS) Chrome (Android): Open the site, tap the Page info icon (three dots or padlock) in the address bar, then select Cookies and site data > Delete. Safari (iPhone/iPad): Go to Settings > Safari > Advanced > Website Data. Search for the site, swipe left on its name, and tap Delete We will continue to monitor closely to ensure there are no further issues, but please continue to view this page for further updates.

4. resolved Jun 02, 2026, 09:01 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 29, 2026, 02:39 PM UTC· resolved May 29, 2026, 05:59 PM UTC

1. investigating May 29, 2026, 02:39 PM UTC

   We are currently investigating a login issue impacting specific users. This is a top priority and we are working on remediating the issue as soon as possible. Please monitor this page for further updates.

2. identified May 29, 2026, 03:18 PM UTC

   We have identified the root cause of the login issue and we are currently working on a solution. This remains a top priority and expect to have resolution as soon as possible. Please monitor this page for further updates.

3. monitoring May 29, 2026, 04:05 PM UTC

   The needed fix has been implemented and tested. The issue has been resolved, but we will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

4. resolved May 29, 2026, 05:59 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 15, 2026, 01:20 PM UTC· resolved May 15, 2026, 04:24 PM UTC

1. investigating May 15, 2026, 01:20 PM UTC

   We are aware of an ongoing issue that is impacting some users from being able to access Salsa CRM. Our engineers are actively investigating this and working to resolve this issue. Please monitor this page for further updates.

2. investigating May 15, 2026, 02:05 PM UTC

   As we work to resolve this issue, you may experience a slight disruption. Please monitor this page for further updates.

3. monitoring May 15, 2026, 02:29 PM UTC

   A fix has been implemented to address the issue. We will continue to monitor to ensure there is no regression. Please continue to monitor this page for further updates.

4. resolved May 15, 2026, 04:24 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 11, 2026, 07:54 PM UTC· resolved May 11, 2026, 08:18 PM UTC

1. investigating May 11, 2026, 07:54 PM UTC

   We are currently investigating an issue that is blocking access into Apricot for specific customers. We are reviewing this as a top priority and working to remediate as soon as possible. Please monitor this page for further updates.

2. resolved May 11, 2026, 08:18 PM UTC

   This incident has been resolved.

Read the full incident report →

Started May 08, 2026, 03:48 PM UTC· resolved May 08, 2026, 04:04 PM UTC

1. investigating May 08, 2026, 03:48 PM UTC

   We are currently investigating an issue that is causing users to receive an error when editing draft messages in Targeted Email. We are working as quickly as possible to resolve this and will share an update as soon as we have one.

2. resolved May 08, 2026, 04:04 PM UTC

   As of 11:59 AM ET, the earlier issue that caused users to receive an error when editing a draft message in Targeted Email has been resolved. We are continuing to monitor for any further issues.

Read the full incident report →

Started May 05, 2026, 04:31 PM UTC· resolved May 06, 2026, 05:44 PM UTC

1. investigating May 05, 2026, 04:31 PM UTC

   Some users are currently unable to log in to Apricot and are receiving a 403 Unauthorized Access error. We are actively working on a resolution and will post updates here as they become available. While we continue to investigate, there are potential workaround options to assist you: 1. Clearing cache and cookies or 2. Updating their web browser then trying again

2. identified May 05, 2026, 06:59 PM UTC

   We have identified the root cause of this issue and we are actively working on a solution to remediate. In the meantime, please leverage the follow workaround options: 1. Clearing cache and cookies or 2. Updating their web browser then trying again We will add further updates as they become available, so please continue to monitor the page for further updates.

3. identified May 05, 2026, 08:46 PM UTC

   We have identified a solution to remediate the issue, but it will take additional time to fully implement. In the meantime, please leverage the follow workaround options: 1. Clearing cache and cookies or 2. Updating their web browser then trying again **All users should always remember to log out of Apricot, especially when using shared workstations.** Please continue to monitor this page for further updates.

4. identified May 06, 2026, 03:32 PM UTC

   We are currently testing a fix and we are expecting to deploy shortly. Please continue to monitor this page for further updates.

5. resolved May 06, 2026, 05:44 PM UTC

   The incident has been successfully resolved.

Read the full incident report →

Started May 05, 2026, 02:48 PM UTC· resolved May 06, 2026, 05:46 PM UTC

1. monitoring May 05, 2026, 02:48 PM UTC

   At this time, Support is experiencing a high volume of inquiries. We apologize for any delays and we are working to respond as quickly as possible. Thank you for your patience.

2. resolved May 06, 2026, 05:46 PM UTC

   The incident has been successfully resolved.

Read the full incident report →

Started May 04, 2026, 03:05 PM UTC· resolved May 04, 2026, 06:45 PM UTC

1. investigating May 04, 2026, 03:05 PM UTC

   We are currently reviewing an issue that is causing delays/latency issues with CyberGrants. This is a top priority and we are actively working to remediate as soon as possible. Please monitor this page for further updates.

2. monitoring May 04, 2026, 04:22 PM UTC

   We have completed an update to address the delay/latency issue. We will continue to monitor to ensure there are no further issues. Please continue to monitor this page for further updates.

3. resolved May 04, 2026, 06:45 PM UTC

   This incident has been resolved.

4. postmortem May 07, 2026, 02:11 PM UTC

   **Issue Summary:** On May 4th, 2026, when an email campaign was sent with call to action the event search pages were slow to respond and timed out in some cases. **Root Cause:** An edge case in the event configuration was identified that caused the SQL execution plan to be very costly. The increased load on the system in conjunction with the slow query plan caused slowness/timeouts. **Prevention:** Short term, we vertically scaled the database, and also altered the event configuration slightly to help optimize the query. As for a permanent solution we are working to ensure that this edge case is covered correctly by the query optimizer. That may involve altering the query used by the application and/or adding covering indexes to ensure the query optimizer picks the best plan.

Read the full incident report →

Started Apr 30, 2026, 06:51 PM UTC· resolved Apr 30, 2026, 08:13 PM UTC

1. investigating Apr 30, 2026, 06:51 PM UTC

   We are currently investigating reports that some users are experiencing intermittent errors accessing www.targetsmartvan.com. We are working as quickly as possible to resolve this and will share an update as soon as we have one.

2. resolved Apr 30, 2026, 08:13 PM UTC

   As of 4:05PM ET, the earlier issue that caused some users to experience intermittent errors accessing www.targetsmartvan.com has been resolved. We are continuing to monitor for any further issues.

Read the full incident report →

Started Apr 23, 2026, 12:31 AM UTC· resolved Apr 23, 2026, 01:53 AM UTC

1. identified Apr 23, 2026, 12:31 AM UTC

   We are currently seeing some users encountering login issues for Apricot US. We have identified the issue and are working on resolution.

2. monitoring Apr 23, 2026, 01:27 AM UTC

   A fix has been implemented and we are monitoring to ensure stability.

3. resolved Apr 23, 2026, 01:53 AM UTC

   The issue is now resolved.

Read the full incident report →