Splunk Cloud logo

Is Splunk Cloud Down?

Developer ToolsLive status, outages, and incident history

No. Splunk Cloud is up right now.

Every monitored Splunk Cloud system is operational as of August 24, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive, rechecked every 60s
How we know: the official Splunk Cloud status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Splunk Cloud Component Status

The main Splunk Cloud systems on this page. All 8 are operational right now.

8operational
Cloud Connect » Detection Studio
Operational
Cloud Connect » Threat Intel Management
Operational
Index
Operational

5 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Infrastructure, Ingest » Edge Processor, Ingest » Ingest Processor, Login, Search.

Create a free account

Component statuses may change independently during partial outages.

Recent Splunk Cloud Outages & Incidents

Incident history from the official Splunk Cloud status page, including resolution updates.

Splunkbase is DownResolved Jul 31, 2026 · 47 minResolved

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. --- [2026-07-31T00:35:14.751Z] (investigating) We are continuing to investigate this issue. --- [2026-07-31T00:34:29.888Z] (investigating) 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.

Expected Restart(s) Following Maintenance ActivityResolved May 29, 2026 · 53h 28mResolved

This incident has been resolved. --- [2026-05-31T03:22:48.895Z] (monitoring) We continue to monitor the rolling restart activities affecting some environments with ITSI. Communications have been sent to customers whose environments may experience potential impact. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. Remaining restart activities continue to be coordinated for midnight local time in the applicable cloud provider region to provide a more controlled customer experience. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required. --- [2026-05-30T20:50:34.531Z] (monitoring) We continue to monitor the rolling restart activities affecting some environments with ITSI. Communications have been sent to customers whose environments may experience potential impact. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. Remaining restart activities continue to be coordinated for midnight local time in the applicable cloud provider region to provide a more controlled customer experience. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required. --- [2026-05-30T09:31:52.500Z] (monitoring) We continue to monitor the rolling restart activities affecting some environments with ITSI. Communications have been sent to customers whose environments may experience potential impact. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. Remaining restart activities continue to be coordinated for midnight local time in the applicable cloud provider region to provide a more controlled customer experience. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required. --- [2026-05-30T06:56:57.570Z] (monitoring) We have identified the cause of the rolling restart activity affecting some environments with ITSI and continue to monitor impacted environments. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. To provide a more controlled customer experience, remaining restart activities are being coordinated to occur at midnight local time for the applicable cloud provider region. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required. --- [2026-05-30T02:33:50.644Z] (monitoring) We have identified the cause of the rolling restart activity affecting some environments with ITSI and continue to monitor impacted environments. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. To provide a more controlled customer experience, remaining restart activities are being coordinated to occur at midnight local time for the applicable cloud provider region. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required. --- [2026-05-29T23:34:32.146Z] (monitoring) We have identified the cause of the rolling restart activity affecting some environments with ITSI and continue to monitor impacted environments. Customers may continue to observe restart notifications, reload prompts, or intermittent search disruptions while rolling restart activities complete. To provide a more controlled customer experience, remaining restart activities are being coordinated to occur at midnight local time for the applicable cloud provider region. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required. --- [2026-05-29T22:14:13.506Z] (investigating) Update: Rolling restart activities may be occurring at midnight local time for the applicable cloud provider region for some environments with ITSI. Customers may continue to observe restart notifications or reload prompts within the UI while these activities complete. Customer environments that may see restart notifications include: Splunk Cloud Platform Splunk Cloud Platform for FedRAMP Moderate Splunk Cloud Platform for FedRAMP High Splunk Cloud Platform for IL5 No customer action is required. --- [2026-05-29T21:35:31.375Z] (investigating) As part of a recent maintenance activity, some environments with ITSI may experience a rolling restart of the environment. Customers may temporarily see restart notifications or reload prompts within the UI while these activities complete.

Admin Config Service (ACS) Maintenance WindowScheduled for May 29, 2026 · 3h 0mScheduled

The scheduled maintenance has been completed. --- [2026-05-29T16:00:07.477Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-05-26T22:31:53.559Z] (scheduled) What's Happening? The objective of this maintenance window is to test Regional Resiliency feature where in we will failover to a backup ACS region and perform tests. This applies to all Splunk Cloud Commercial customers and is part of our commitment to unlocking enhanced functionality in future ACS releases while ensuring optimal performance for your Splunk Cloud environment? Service Impact: - ACS Services: APIs, CLI, and Terraform Splunk Cloud Provider (SCP) integrations will be offline. - IP Allow Lists will continue to be enforced throughout the update and will persist after this upgrade - IP Allow List UI page and API calls will not be accessible - ACS Helper App - Viewing or Editing Maintenance Window Schedules (CMC App) - Viewing or editing maintenance windows will be unavailable - Existing Maintenance Windows and settings will persist after this upgrade - Existing Configurations: (e.g., IP Allow Lists, user roles) will remain active and unaffected. Services with no impact: - Splunk Cloud Platform features such as environment access, search, and data ingestion will remain fully operational - Federated Searches and existing Federated Connections will continue to operate - Federated Search settings will persist and Cloud admins will regain CRUD Customer Notes: - No other maintenance windows or changes to your environments are scheduled during this time. Additionally, this upgrade will not affect your current Splunk Cloud Platform version or ACS version. - No P1 Tickets: Please refrain from opening Priority 1 tickets for impacted services (Admin Config Service) during the maintenance window. If issues persist after the maintenance window has concluded (5/29/2026 19:00 UTC), submit a support request as needed. Thank you for your patience as we make these critical upgrades. For questions, contact our support team.

Splunk Cloud Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Splunk Cloud incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history91 days observed
May 2697.42% average · 6 days with incidentsAug 24

Going further back: Splunk Cloud uptime by month and every recorded Splunk Cloud outage.

Live Splunk Cloud Outage Reports

Problems reported by engineers using Splunk Cloud. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Splunk Cloud problems reported yet.

Something wrong with Splunk Cloud on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Splunk Cloud

Splunk Cloud is the enterprise SIEM and observability platform for security operations, IT ops, and business intelligence through machine data analysis. Splunk Cloud outages reduce security visibility. Track Splunk Cloud status and outages here.

Over the past 30 days, PulsAPI has measured Splunk Cloud uptime at 99.99%. Response times, incident history, and SLA tracking for Splunk Cloud are available on the PulsAPI dashboard.

Splunk Cloud Status FAQ

Is Splunk Cloud down right now?

PulsAPI checks Splunk Cloud every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Splunk Cloud status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Splunk Cloud is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Splunk Cloud recovers.

How do I check Splunk Cloud uptime history?

PulsAPI tracks Splunk Cloud uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 99.99%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Splunk Cloud.

How fast does PulsAPI detect Splunk Cloud outages?

PulsAPI polls the official Splunk Cloud status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Splunk Cloud components?

Yes. PulsAPI monitors 8 individual Splunk Cloud components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Splunk Cloud goes down?

Yes. Create a PulsAPI account and subscribe to Splunk Cloud. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Splunk Cloud status changes.

How do I report an issue with Splunk Cloud to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Splunk Cloud problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Splunk Cloud?

Yes. PulsAPI's Starter plan includes up to 25 monitored services with Slack and email alerts, and the 30-day free trial requires no credit card. You can monitor Splunk Cloud alongside up to 24 other services at pulsapi.com/signup.

Track Splunk Cloud with the rest of your stack

Monitor 2463+ cloud services from one dashboard and get alerts when Splunk Cloud status changes.

Start free trial