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

SCA Scans delays on SAAS environment

Reported by Mend.io · Identity & Security · source last read 4 min ago

Vendor start
Dec 18, 2024, 09:05 UTC
Vendor's clock
Resolved
Dec 18, 2024, 11:31 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
2 h 26 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

  • Mend.io reports degraded: "SCA Scans delays on SAAS environment".[E1, E2]
  • The vendor marked it resolved at 2024-12-18 11:31 UTC.[E3, E7]

Affected products and regions

  • Components: Scans Processing.[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: 2024-12-18 11:31 UTC · summary s1, evidence 536284a8944d4156

Evidence (7)
  1. E1Mend.io reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "SCA Scans delays on SAAS environment". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2024-12-18 09:05 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Scans Processing. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2024-12-18 11:31 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Scans Processing

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

Mend.io 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. Dec 18, 2024, 09:05 UTCVendor-reported startVendor time
  2. Dec 18, 2024, 11:31 UTCVendor-reported resolutionVendor time

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