Status as of

Splunk Cloud logo

Splunk Cloud down?

Forwards to:www.splunk.com

Splunkcloud.com hosts customer instances of Splunk Cloud Platform, the software-as-a-service version of Splunk's data analytics platform, now part of Cisco. Organisations send machine data such as logs, metrics and events from applications, infrastructure and security tools to Splunk Cloud, where they can search, monitor, analyse and visualise it. Splunk Cloud supports security operations with Splunk Enterprise Security, IT operations and observability use cases, providing scalability, security and compliance without managing Splunk infrastructure.

Splunk Cloud status preview image

I have a problem with Splunk Cloud

Select the type of problem you're facing to help us and other users.

Recent User Report Trends for Splunk Cloud

Aggregated reports in the last 48 hours.

Official Status Unavailable

We couldn't load live incident data from the official status page for splunkcloud.com at this time. Please try again later.

User Reports for Splunk Cloud

Recent issues reported by users from around the world.

Experiencing an issue? Add your report:

Stop refreshing this page

We'll email you the moment Splunk Cloud goes down — and again when it's back.

How to fix Splunk Cloud not working

Splunk Cloud is a hosted service for searching and monitoring machine data such as logs and security events. Operations, security and developer teams use it. Find your symptom below. Most problems come from a sign-in, a data forwarder or input, a search or alert setting, or the platform itself.

Jump to what you are seeing

Login Failed

Sign-in to the Splunk Cloud instance is refused.

  1. Use the sign-in route your company set up, such as single sign-on.
  2. If the message says the password is wrong, reset it and check spam.
  3. Ask your administrator to confirm your role allows access to the indexes you need.

Search Not Working

A search returns no results, or it stops with an error.

  1. Check the time range and the index selected in the search.
  2. Check the search syntax. A wrong field name returns nothing.
  3. Narrow the time range and try again, then widen it.

Data Ingestion Delayed

Logs or events arrive late, or they do not arrive at all.

  1. Check the forwarder or input on the source is running and shows no errors.
  2. Check the network path to the cloud instance is not blocked.
  3. Check status.splunkcloud.com for an ingestion incident.
  4. If only one source is missing, check the source's own log for a send error.

Dashboard Not Loading

A dashboard stays blank, slow, or shows errors.

  1. Reload in a private window with extensions turned off.
  2. Shorten the time range, since a very wide range can time out.
  3. Check each panel's search. One failing search can stop the others loading.

API Error

Calls to the Splunk Cloud API fail or return an error.

  1. Check the status code. A 401 or 403 means the token or permission is wrong, a 429 means too many calls, and a 5xx means a platform-side problem.
  2. Confirm the token has not expired or been revoked.
  3. Retry with a growing delay.

Slow Performance

Searches or dashboards are slow, usually because of a very large search or a busy time.

  1. Narrow the search by index and time range.
  2. Check the search is not running over all data when it needs only one source.
  3. If it is slow for everyone, check the status page.

Alerting Issues

An alert does not fire, or it fires too often.

  1. Check the alert's search returns results over the period it checks.
  2. Check the alert's trigger condition and its schedule.
  3. Check the alert action, such as email or a ticket, is connected and working.

Still not working?

If it still does not work, contact your Splunk administrator first, since they manage inputs, indexes and access. For a platform-wide problem, contact Splunk support through the help option in the platform or on the Splunk website. Have your instance name, the search or alert name, the exact error text, and the time it started with your time zone. Never send tokens or log contents that include personal data in a support message. Live incident updates are on status.splunkcloud.com.

Most log-platform problems come from a forwarder, a time range or a search setting, and they usually clear once that one item is corrected. The status page shows live platform incidents, so you can see whether the problem is on Splunk's side.

Frequently asked questions about Splunk Cloud

Is Splunk Cloud down right now?

We cannot confirm an outage for Splunk Cloud (splunkcloud.com) at the moment, and we have no live automated check result to show for it. This page relies on incident updates and reports from users.

What should I do if Splunk Cloud is not working for me?

First rule out your side: reload the page, try another browser or device, clear the cache and cookies for splunkcloud.com, flush your DNS cache and turn off any VPN or proxy. Then compare with this page: if the status shows an incident, or many users reported problems in the last 48 hours, the issue is on the service's end and usually clears up without any action from you. The troubleshooting steps on this page go through each check in order.

How do I report a problem with Splunk Cloud?

Use the report buttons at the top of this page, or describe the problem in the user reports section. Every report is counted in the 48-hour trend chart and helps other people see whether the problem is widespread.

Where is the official Splunk Cloud status page?

The official status page for Splunk Cloud is status.splunkcloud.com.

Advanced Domain Info Unavailable

We couldn't load advanced domain and security information for splunkcloud.com at this time. Please try again later.