## Isolate the affected Splunk On-Call path Use the [Splunk On-Call status page](/downdetector/splunk-on-call) to compare login, incident ingestion, notifications, escalations, and integrations. - Verify the source incident independently. - Test a controlled nonproduction notification. - Record region, integration type, channel, and error. Do not expose routing keys, phone numbers, incident contents, schedules, or internal service names.