Cuseum Outage History

Cuseum is up right now

Cuseum had 8 outages in the last 2 years totaling 157h 56m of downtime, averaging 0.3 incidents per month.

There were 8 Cuseum outages since November 22, 2024 totaling 157h 56m of downtime. Each is summarised below. Incident details, duration, and resolution information.

Source: status.cuseum.com

Major July 28, 2026

Issue Identified with Member Portal and Apps

Detected by Pingoru
Jul 28, 2026, 06:22 PM UTC
Resolved
Jul 29, 2026, 12:49 PM UTC
Duration
18h 26m
Affected: Member PortalWeb AppsMobile Apps
Timeline · 3 updates
  1. identified Jul 28, 2026, 06:22 PM UTC

    We have identified the issue affecting Member Portal and Apps. Our team is now working diligently to resolve the issue. We will provide updates on our progress. If you require further information, please don't hesitate to contact our support team. We apologize for any disruption this may have caused.

  2. monitoring Jul 29, 2026, 12:28 PM UTC

    The issues have been addressed, and a fix has been implemented. We are now monitoring the situation to ensure that everything is working as expected. We will provide another update once we can confirm the issue is fully resolved. If you have any questions or concerns, please reach out to our support team. Thank you for your patience.

  3. resolved Jul 29, 2026, 12:49 PM UTC

    We are pleased to report that the issue has been resolved. We have confirmed that all systems are operating as expected. If you have any further questions or concerns, please don't hesitate to contact our support team. We apologize for any disruption this incident may have caused and thank you for your patience.

Read the full incident report →

Minor July 12, 2026

Issue Identified with Neon CRM

Detected by Pingoru
Jul 12, 2026, 08:15 AM UTC
Resolved
Jul 14, 2026, 01:21 AM UTC
Duration
1d 17h
Affected: [Third-party] Neon CRM
Timeline · 3 updates
  1. identified Jul 12, 2026, 08:15 AM UTC

    We have identified the issue affecting Neon CRM. Our team is now working diligently to resolve the issue. We will provide updates on our progress. If you require further information, please don't hesitate to contact our support team. We apologize for any disruption this may have caused.

  2. monitoring Jul 13, 2026, 11:44 PM UTC

    The issue with the V2 API has been addressed, and a fix has been implemented. We are now monitoring the situation to ensure that everything is working as expected. We will provide another update once we can confirm the issue is fully resolved. If you have any questions or concerns, please reach out to our support team. Thank you for your patience.

  3. resolved Jul 14, 2026, 01:21 AM UTC

    We are pleased to report that the issue with Neon CRM has been resolved. We have confirmed that all systems are operating as expected. If you have any further questions or concerns, please don't hesitate to contact our support team. We apologize for any disruption this incident may have caused and thank you for your patience.

Read the full incident report →

Minor March 11, 2026

Issue Identified with CMS

Detected by Pingoru
Mar 11, 2026, 04:25 PM UTC
Resolved
Mar 11, 2026, 05:36 PM UTC
Duration
1h 10m
Affected: CMS / Main AppMember Portal
Timeline · 3 updates
  1. identified Mar 11, 2026, 04:25 PM UTC

    We have identified the issue affecting some users accessing the CMS. Our team is now working diligently to resolve the issue. We will provide updates on our progress. If you require further information, please don't hesitate to contact our support team. We apologize for any disruption this may have caused.

  2. monitoring Mar 11, 2026, 04:50 PM UTC

    The issues have been addressed and a fix has been implemented. We are now monitoring the situation to ensure that everything is working as expected. We will provide another update once we can confirm the issue is fully resolved. If you have any questions or concerns, please reach out to our support team. Thank you for your patience.

  3. resolved Mar 11, 2026, 05:36 PM UTC

    We are pleased to report that the issue has been resolved. We have confirmed that all systems are operating as expected. If you have any further questions or concerns, please don't hesitate to contact our support team. We apologize for any disruption this incident may have caused and thank you for your patience.

Read the full incident report →

Minor March 2, 2026

Issue identified with Blackbaud services

Detected by Pingoru
Mar 02, 2026, 04:13 PM UTC
Resolved
Mar 03, 2026, 04:49 PM UTC
Duration
1d
Affected: [Third-party] Blackbaud Altru®[Third-party] Blackbaud eTapestry®[Third-party] Blackbaud Raiser's Edge NXT®[Third-party] Raiser's Edge®
Timeline · 5 updates
  1. identified Mar 02, 2026, 04:13 PM UTC

    We have identified an issue affecting Blackbaud customers. Blackbaud is returning "504 Gateway Timeout" errors on their side. Our team is monitoring Blackbaud's progress in resolving the issue. You can follow the Blackbaud issue here: https://status.blackbaud.com/incidents/s8trlcbc0hlh If you require further information, please don't hesitate to contact our support team.

  2. identified Mar 02, 2026, 05:56 PM UTC

    Update from Blackbaud: Intermittent issues are recurring. Users are receiving errors including "504 Gateway Timeout" when attempting to login or navigate through their solutions. Our engineers are investigating this error and working to resolve it for you as quickly as possible. Please continue to reference this page for updates. ---- You can follow their updates here: https://status.blackbaud.com/incidents/s8trlcbc0hlh

  3. identified Mar 02, 2026, 07:22 PM UTC

    Update from Blackbaud: We continue to see a reduction in the number of errors received by users when attempting to login or navigate through their Blackbaud solutions. Our engineers are continuing to investigate to identify the root cause and work toward full resolution of this incident. We continue monitoring system performance. Please continue to reference this page for updates. ---- You can follow their updates here: https://status.blackbaud.com/incidents/s8trlcbc0hlh

  4. identified Mar 02, 2026, 08:48 PM UTC

    Update from Blackbaud: We continue to see stable login response times and reduced navigation errors following recent configuration changes. We will continue monitoring system performance to ensure ongoing stability. Please continue to reference this page for updates ---- You can follow their updates here: https://status.blackbaud.com/incidents/s8trlcbc0hlh

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

    We are pleased to report that the issue has been resolved. We have confirmed that all systems are operating as expected. If you have any further questions or concerns, please don't hesitate to contact our support team. Update from Blackbaud: An issue impacting some of our customers is now resolved and services have been restored. If you have any questions about status in the future, you can always get updates at this page. Thank you. ---- Blackbaud issue timeline here: https://status.blackbaud.com/incidents/s8trlcbc0hlh

Read the full incident report →

Minor November 14, 2025

Investigation - Degraded performance

Detected by Pingoru
Nov 14, 2025, 03:36 PM UTC
Resolved
Nov 15, 2025, 10:36 AM UTC
Duration
18h 59m
Affected: CMS / Main App
Timeline · 4 updates
  1. investigating Nov 14, 2025, 03:36 PM UTC

    We are currently experiencing a service degradation resulting in slow page loads and/or timeout errors for some users. Our team is working to identify the issue, and we will update you with more information as soon as it becomes available. If you require additional information or assistance, please contact our support team. We apologize for any inconvenience caused and appreciate your patience.

  2. identified Nov 15, 2025, 08:58 AM UTC

    We have identified the issue affecting performance, and a fix is in progress. Our team is now working diligently to resolve the issue. We will provide updates on our progress. If you require further information, please don't hesitate to contact our support team. We apologize for any disruption this may have caused.

  3. monitoring Nov 15, 2025, 10:07 AM UTC

    The issues have been addressed and a fix has been implemented. We are now monitoring the situation to ensure that everything is working as expected. We will provide another update once we can confirm the issue is fully resolved. If you have any questions or concerns, please reach out to our support team. Thank you for your patience.

  4. resolved Nov 15, 2025, 10:36 AM UTC

    We are pleased to report that the issue has been resolved. We have confirmed that all systems are operating as expected. If you have any further questions or concerns, please don't hesitate to contact our support team. We apologize for any disruption this incident may have caused and thank you for your patience.

Read the full incident report →

Minor April 29, 2025

High volume causing processing delays

Detected by Pingoru
Apr 29, 2025, 05:21 PM UTC
Resolved
Apr 30, 2025, 04:12 AM UTC
Duration
10h 50m
Affected: Fetch APIGeneration APIDistribution APIPush Notifications APISMS / Text MessagingGuest PassesSFTP
Timeline · 2 updates
  1. identified Apr 29, 2025, 05:21 PM UTC

    We are currently experiencing a high volume of activity, which is causing delays in processing digital memberships. Our team is actively working to resolve the issue and ensure that memberships are processed as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience. Updates will be provided here as we progress.

  2. resolved Apr 30, 2025, 04:12 AM UTC

    We are happy to report that the high volume causing delays in digital membership processing has been resolved. All systems are now operating normally, and memberships are being processed without delays. Thank you for your patience and understanding while we worked to restore full performance. If you continue to experience any issues, please don’t hesitate to contact our support team.

Read the full incident report →

Minor December 12, 2024

Investigation for Issues with Blackbaud Altru integration

Detected by Pingoru
Dec 12, 2024, 02:39 PM UTC
Resolved
Dec 14, 2024, 12:22 AM UTC
Duration
1d 9h
Affected: [Third-party] Blackbaud Altru®
Timeline · 3 updates
  1. investigating Dec 12, 2024, 02:39 PM UTC

    We are currently investigating an issue affecting Altru customers. It appears that Blackbaud Altru API is returning an unauthorized or access-denied response on their side. Our team is contacting Blackbaud, and we will update you with more information as soon as we have it. If you require further information, please don't hesitate to contact our support team.

  2. investigating Dec 12, 2024, 05:10 PM UTC

    UPDATE: We are currently in touch with Blackbaud support regarding the issue. They are investigating the matter, and we will keep you updated when any changes occur.

  3. resolved Dec 14, 2024, 12:22 AM UTC

    The issue has been identified and solved. However, some updates need to be worked on. Please keep an eye on your inbox for further steps in order to address the fetching situation with Altru. If you didn't receive an email please email [email protected] or use the chat widget in your Cuseum account to receive assistance as soon as possible.

Read the full incident report →

Minor November 25, 2024

Active Issue Alert - Degraded CMS performance

Detected by Pingoru
Nov 25, 2024, 10:22 PM UTC
Resolved
Nov 26, 2024, 07:25 AM UTC
Duration
9h 3m
Affected: CMS / Main AppFetch APIGeneration APIDistribution APIPush Notifications APISMS / Text MessagingGuest PassesSFTP
Timeline · 3 updates
  1. investigating Nov 25, 2024, 10:22 PM UTC

    We are currently experiencing a service degradation resulting in intermittencies/Time-out errors. In some instances, you may also encounter a 500 Error when loading a section of the CMS. Our engineering team is actively working on this issue to identify the root cause and restore operational standards. Although we don't have ETA yet, we will keep you posted. Thank you for your understanding as we address the situation.

  2. monitoring Nov 26, 2024, 04:36 AM UTC

    We have implemented a fix for errors affecting our services in some locations. Our team is actively monitoring the system to ensure that all issues have been fully resolved. We appreciate your patience and will provide further updates as necessary.

  3. resolved Nov 26, 2024, 07:25 AM UTC

    We have confirmed that all systems are operating as expected. If you have any further questions or concerns, please don't hesitate to contact our support team. We apologize for any disruption this incident may have caused and thank you for your patience.

Read the full incident report →