Live  /  Sprinklr  /  Incident

Sprinklr: Potential Compute VM Issue

Sprinklr · sprinklr.comResolved2026-10-16 08:43 UTC
Public — what happened

Summary

Sprinklr said it began looking into a possible problem with compute virtual machines in one region on 2026-10-13 at 07:06 UTC. The company said its application stayed stable and it had seen no customer impact at that point. Sprinklr said its engineers were working with Microsoft Azure to assess the situation and decide on next steps. The incident was marked resolved on 2026-10-16 at 08:43, and the text provided does not name a cause.

Affected

EMEA (Prod3)

As listed on Sprinklr’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Sprinklr against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Sprinklr: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Sprinklr report →

More from Sprinklr

Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.

The full archive is on the Sprinklr status & history page.

Related: Sprinklr status & history. SquidGrid is not affiliated with Sprinklr.