Splunk Observability Cloud domain change

Product UI (SaaS URL)

Since March 2026, all new customers have accessed Splunk Observability Cloud at observability.splunkcloud.com.

For existing customers, the login URL changes only for users who sign in through SAML or Splunk Unified Identity. After their organization's domain update, these users must sign in using the new URL. Users who sign in with a username and password can continue using either domain; we recommend observability.splunkcloud.com. See What changes during the domain update.

Use the URL format that applies to your organization:

Replace realm or your-org with the value for your organization.

API and service URL changes

Existing signalfx.com ingest and API endpoints remain available. There is no planned retirement date for existing signalfx.com ingest endpoints. See API and Service URL mappings for the legacy and new endpoint URLs.

Purpose of the new domain

The new domain highlights that Splunk Observability Cloud is a fully integrated and supported part of the Splunk Cloud Platform. It also simplifies navigation and provides a consistent experience across the broader Splunk product portfolio.

Domain availability

All new customers have used observability.splunkcloud.com since March 2026. Existing customers are receiving the domain update in the following groups. The dates describe when product links and applicable detector references are updated; they do not indicate an account or data migration.

Required actions and recommendations

Follow the instructions emailed to your organization's administrators. If your organization uses SAML or an affected alert integration, complete the preparation described in those instructions and coordinate with Support if requested.

Make sure users can reach observability.splunkcloud.com. If your network uses domain-based filtering, firewalls, proxies, or allowlists, permit access to the new domain.

The domain update does not move your account or data, and it does not require changes to Collector, agent, SDK, OTLP, or other telemetry endpoint configurations.

What changes during the domain update

Product-generated communications that link to Splunk Observability Cloud, including alerts, reminders, and other product emails, will use observability.splunkcloud.com. Where applicable detector fields contain signalfx.com links, those links will be updated to observability.splunkcloud.com. The fields include runbookUrl, tip, parameterizedBody, and parameterizedSubject. Only links that reference the old domain are changed.

Recommendations for future planning

To ensure uninterrupted access and data ingest, confirm that your organization can reach Splunk Observability Cloud using the new domain (observability.splunkcloud.com). Review your infrastructure for any network or security updates to identify any required changes to your network, security, or configuration settings.

Areas to review

Access issues typically stem from controls in the following areas:

• Network controls: DNS (including custom/internal DNS), proxies, gateways, routing, firewall rules, and outbound (egress) allowlists

• Security controls: endpoint protection, web/application firewalls, TLS/SSL inspection, and destination allowlists/deny lists

Key checks

API and Service URLs changes

New endpoints are now available under the observability.splunkcloud.com domain. Existing endpoints will remain unchanged and fully supported.

The table below provides detailed mappings between the legacy and new URLs to support future planning and integration updates.

Getting more information

Next steps

Follow the instructions emailed to your organization's administrators. If your organization is scheduled for a guided domain update, we will email administrators with instructions for requesting and completing it. We will add further guidance to this page as it becomes available.