Splunk Observability Cloud domain change
This page announces the introduction of the new domain for Splunk Observability Cloud, discusses legacy and new domains, how it impacts new and existing customers, and helps customers prepare for the change.
We are introducing a new domain in March 2026: observability.splunkcloud.com. This domain provides an additional way to access Splunk Observability Cloud and its associated services.
-
data ingest configuration
-
Single Sign-On (SSO) setup
-
organization creation
-
user invitations
-
login and access workflows
Both the legacy (signalfx.com) and new domains will remain available until further notice, and we will continue to provide guidance as support for the new domain expands.
Product UI (SaaS URL)
New customers in March 2026 or later will access the Splunk Observability Cloud experience using the new domain observability.splunkcloud.com.
Existing customers will continue to access the Splunk Observability experience using the legacy domain signalfx.com.
| Legacy URL | New URL |
|---|---|
https://app.realm.signalfx.com |
https://app.realm.observability.splunkcloud.com |
https://your-org.realm.signalfx.com |
https://your-org.realm.observability.splunkcloud.com |
API and Service URL endpoints
Both new and existing customers can access the API and service URL endpoints through the legacy or the new domains. These endpoints include ingestion, integrations, CDNs, Synthetic Runners, and streaming. 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
The new domain will be introduced to new and existing customers over the next three months. During this period, updates to documentation and platform components will reflect the new domain. These changes are informational only and will not affect any existing configurations.
Starting in March 2026, all new customers will access Splunk Observability Cloud exclusively through the new domain. Existing customers may continue using signalfx.com or choose to begin using observability.splunkcloud.com.
Domain rollout timeline
observability.splunkcloud.com domain will be introduced between February and May 2026:
-
March 2026: Initial availability of the new domain
observability.splunkcloud.com. -
March - May 2026: Updates to default configurations and documentation across the data ingest ecosystem. All public product and developer documentation will be revised to reflect the new domain.
Required actions and recommendations
No immediate action is required. You can continue using Splunk Observability Cloud with your current SaaS configuration, URLs, and service endpoints (signalfx.com) without any changes.
Additional updates and required actions will be communicated separately as they become available.
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
End-user access (web application)
Verify that users can open and sign in to the Splunk Observability Cloud web UI using the new domain from all relevant environments (e.g., corporate network, VPN, VDI). Any saved or bookmarked URLs pointing to the old domain would need to be updated to the new domain.
API and tooling access (integrations and automation)
-
API calls used by scripts and services
-
CI/CD runners and deployment tooling
-
Third-party integrations that connect to Splunk Observability Cloud endpoints
Ensure that your instrumented environments can continue exporting telemetry data to the new domain, including:
-
Hosts, containers, Kubernetes clusters, and application instrumentation (agents/SDKs)
-
Gateway components (e.g., OpenTelemetry Collector running as a gateway)
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.
| Product Feature | Legacy URL | New URL |
|---|---|---|
| Integrations | https://login.signalfx.com/#/integrations/integration |
https://login.observability.splunkcloud.com/#/integrations/integration |
| Ingest | https://ingest.realm.signalfx.com |
https://ingest.realm.observability.splunkcloud.com |
https://rum-ingest.realm.signalfx.com |
https://rum-ingest.realm.observability.splunkcloud.com |
|
| Stream | https://stream.realm.signalfx.com |
https://stream.realm.observability.splunkcloud.com |
| APIs | https://api.realm.signalfx.com |
https://api.realm.observability.splunkcloud.com |
| CDN | https://cdn.signalfx.com |
https://cdn.observability.splunkcloud.com |
| Runner | https://runner.realm.signalfx.com |
https://runner.realm.observability.splunkcloud.com |
AWS PrivateLink URLs
|
Splunk Observability Cloud realm |
AWS region |
Legacy ingest endpoint URL |
New ingest endpoint URL |
|---|---|---|---|
|
jp0 |
AWS AP Tokyo (ap-northeast-1) |
|
|
|
au0 |
AWS AP Sydney (ap-southeast-2) |
private-ingest.au0.signalfx.com |
|
|
eu1 |
AWS EU Frankfurt (eu-central-1) |
|
|
|
eu0 |
AWS EU Dublin (eu-west-1) |
|
|
|
eu2 |
AWS EU London (eu-west-2) |
|
|
|
us0 |
AWS US East Virginia (us-east-1) |
|
|
|
us1 |
AWS US West Oregon (us-west-2) |
|
|
| sg0 | AWS AP Singapore (ap-southeast-1) |
|
ingest.sg0.observability.splunkcloud.com |
|
Splunk Observability Cloud realm |
AWS region |
Legacy API endpoint URL |
New API endpoint URL |
|---|---|---|---|
|
jp0 |
AWS AP Tokyo (ap-northeast-1) |
|
|
|
au0 |
AWS AP Sydney (ap-southeast-2) |
|
|
|
eu1 |
AWS EU Frankfurt (eu-central-1) |
|
|
|
eu0 |
AWS EU Dublin (eu-west-1) |
|
|
|
eu2 |
AWS EU London (eu-west-2) |
|
|
|
us0 |
AWS US East Virginia (us-east-1) |
|
|
|
us1 |
AWS US West Oregon (us-west-2) |
|
|
| sg0 | AWS AP Singapore (ap-southeast-1) | private-api.sg0.signalfx.com |
api.sg0.observability.splunkcloud.com |
|
Splunk Observability Cloud realm |
AWS region |
Legacy stream endpoint URL |
New stream endpoint URL |
|---|---|---|---|
|
jp0 |
AWS AP Tokyo (ap-northeast-1) |
|
stream.jp0.observability.splunkcloud.com |
|
au0 |
AWS AP Sydney (ap-southeast-2) |
|
stream.au0.observability.splunkcloud.com |
|
eu1 |
AWS EU Frankfurt (eu-central-1) |
|
stream.eu1.observability.splunkcloud.com |
|
eu0 |
AWS EU Dublin (eu-west-1) |
|
stream.eu0.observability.splunkcloud.com |
|
eu2 |
AWS EU London (eu-west-2) |
|
stream.eu2.observability.splunkcloud.com |
|
us0 |
AWS US East Virginia (us-east-1) |
|
stream.us0.observability.splunkcloud.com |
|
us1 |
AWS US West Oregon (us-west-2) |
|
stream.us1.observability.splunkcloud.com |
| sg0 | AWS AP Singapore (ap-southeast-1) | private-stream.sg0.signalfx.com |
stream.sg0.observability.splunkcloud.com |
Getting more information
For questions about the new domain and how it may affect your account or usage of Splunk Observability Cloud, contact your account representative or customer support team. They can provide guidance tailored to your environment and configuration.Next steps
There are no immediate actions required.
Future updates will be communicated through email notifications and updates on this documentation page. If specific actions become necessary, they will be announced in advance.