Vendor reports: degradedResolved · vendor status “resolved”Official status API

DNS synchronization issue affecting HEC dash DNS records | #cinc-66607_cloud_multiple(Degraded Performance)

Reported by Splunk Cloud · Observability & Incident · source last read just now

Official source (opens in a new tab)
Vendor start
May 28, 2026, 06:22 UTC
Vendor's clock
Resolved
May 28, 2026, 07:21 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:12 UTC
Statuswall's clock
Duration
1 h 0 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Splunk Cloud reports degraded: "DNS synchronization issue affecting HEC dash DNS records | #cinc-66607_cloud_multiple(Degraded Performance)".[E1, E2]
  • The vendor marked it resolved at 2026-05-28 07:21 UTC.[E3, E7]

Affected products and regions

  • Components: Ingest Processor.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:12 UTC · summary s1, evidence 2be5a08f884a9004

Evidence (8)
  1. E1Splunk Cloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "DNS synchronization issue affecting HEC dash DNS records | #cinc-66607_cloud_multiple(Degraded Performance)". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-05-28 06:22 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Ingest Processor. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-05-28 07:21 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:12 UTC. (Statuswall)

Affected scope

Not stated by the vendor

Components: Ingest Processor

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Splunk Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. May 28, 2026, 06:22 UTCVendor-reported startVendor time
  2. May 28, 2026, 07:21 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:12 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall