Cuseum incident

High volume causing processing delays

Minor Resolved View vendor source →

Cuseum experienced a minor incident on April 29, 2025 affecting Fetch API and Generation API and 1 more component, lasting 10h 50m. The incident has been resolved; the full update timeline is below.

Started
Apr 29, 2025, 05:21 PM UTC
Resolved
Apr 30, 2025, 04:12 AM UTC
Duration
10h 50m
Detected by Pingoru
Apr 29, 2025, 05:21 PM UTC

Affected components

Fetch APIGeneration APIDistribution APIPush Notifications APISMS / Text MessagingGuest PassesSFTP

Update timeline

  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.