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

Delayed Cloud Alerts on Instance G

Reported by ThreatLocker · Identity & Security · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Nov 10, 2026, 16:15 UTC
Vendor's clock
Resolved
Not yet
Still open
First seen by Statuswall
Nov 11, 2026, 02:12 UTC
Statuswall's clock
Duration
Not available
Needs both vendor times

Affected scope

Not stated by the vendor

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

ThreatLocker 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 sign-in, SSO and token-refresh success rates.
  • Check whether users are being locked out or prompted unexpectedly.
  • Check error rates, latency and timeouts in your own monitoring for requests that depend on ThreatLocker.
  • Look at synthetic checks and alerts that exercise ThreatLocker.
  • 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. Nov 10, 2026, 16:15 UTCVendor-reported startVendor time
  2. Nov 11, 2026, 02:12 UTCFirst seen by Statuswall (vendor status: monitoring)Seen by Statuswall