Splunk incident

Splunkbase is Down

Critical Resolved View vendor source →

Splunk experienced a critical incident on July 31, 2026 affecting Login, lasting 47m. The incident has been resolved; the full update timeline is below.

Started
Jul 31, 2026, 12:34 AM UTC
Resolved
Jul 31, 2026, 01:22 AM UTC
Duration
47m
Detected by Pingoru
Jul 31, 2026, 12:34 AM UTC

Affected components

Login

Update timeline

  1. investigating Jul 31, 2026, 12:34 AM UTC

    Splunk is investigating an issue currently affecting Splunkbase at "splunkbase.splunk.com". As a result, users may be unable to access Splunkbase and may receive a "500" error. Users may also be unable to download apps or install apps in Splunk Cloud through the UI. We understand the impact this may have on your operations and are working to resolve the issue. We will provide another update in 1 hour, or sooner if more information becomes available.

  2. investigating Jul 31, 2026, 12:35 AM UTC

    We are continuing to investigate this issue.

  3. resolved Jul 31, 2026, 01:22 AM UTC

    Splunk has resolved the issue affecting Splunkbase at splunkbase.splunk.com. Users should now be able to access Splunkbase, download apps, and install apps in Splunk Cloud through the UI as expected. We apologize for the disruption and appreciate your patience while we worked to restore service.