Resolved after 25 minutes, on December 5, 2025.
Splunk On-Call experienced an isolated network disruption between approximately 08:47 UTC - 09:12 UTC earlier today, December 5th. The functionality has since returned to operational. We apologize for any disruption or adverse impact this caused. Please contact Splunk On-Call support with any questions - https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support
Other major vendors with incidents that started within 30 minutes of this one
Update timeline
- resolved Dec 05, 2025, 09:52 PM UTC
Splunk On-Call experienced an isolated network disruption between approximately 08:47 UTC - 09:12 UTC earlier today, December 5th. The functionality has since returned to operational. We apologize for any disruption or adverse impact this caused. Please contact Splunk On-Call support with any questions - https://help.splunk.com/en/splunk-enterprise/alert-and-respond/splunk-on-call/introduction-to-splunk-on-call/getting-started-guide-for-splunk-on-call-admins/contact-splunk-on-call-support
Your product runs on more than Splunk OnCall
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.