Vendor reports: operationalOpen · vendor status “monitoring”Official status API

Industry-wide PHP and Node.js security update

Reported by Gainsight · CRM, Marketing & Sales · source last read 2 min ago

Official source (opens in a new tab)
Vendor start
Oct 23, 2026, 21:24 UTC
Vendor's clock
Resolved
Not yet
Still open
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
Needs both vendor times

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Gainsight reports operational: "Industry-wide PHP and Node.js security update".[E1, E2]
  • It is not resolved yet (vendor status "monitoring").[E3, E7]

Affected products and regions

  • Components: Gainsight CS US1 Application, Gainsight CS US2 Application, Gainsight CS EU Application.[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.
  • When it will be resolved: no estimate is shown unless the vendor publishes one on its page.

Last update in these facts: 2026-10-23 21:24 UTC · summary s1, evidence ef5e02f75aa367bd

Evidence (7)
  1. E1Gainsight reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Industry-wide PHP and Node.js security update". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "monitoring". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-10-23 21:24 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Gainsight CS US1 Application, Gainsight CS US2 Application, Gainsight CS EU Application. (vendor) source (opens in a new tab)
  7. E7Not resolved by the vendor yet. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Gainsight CS US1 Application, Gainsight CS US2 Application, Gainsight CS EU Application

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

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

What to check on your side

Verification steps only. Statuswall cannot see your systems.

  • Check integrations and syncs that push to or pull from Gainsight.
  • Check error rates, latency and timeouts in your own monitoring for requests that depend on Gainsight.
  • Look at synthetic checks and alerts that exercise Gainsight.
  • Compare with recent deploys on your side, so a coincidental change is not blamed on the vendor.
  • Follow the vendor's official incident page for scope changes and resolution.

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. Oct 23, 2026, 21:24 UTCVendor-reported startVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.