Vendor reports: degradedResolved · vendor status “resolved”Vendor incident feed · inferred
New incident: "Container Vulnerability Scans via API/ CLI are experiencing delays"
Reported by FortiCNAPP (Lacework) · Identity & Security · source last read 3 min ago
- Vendor posted
- Feb 13, 2024, 00:57 UTC
- When the vendor's feed dated it
- Resolved
- Feb 14, 2024, 17:00 UTC
- Vendor's clock
- First seen by Statuswall
- Nov 11, 2026, 02:12 UTC
- Statuswall's clock
- Duration
- Not available
- This source does not publish reliable durations
Summary
Built from the facts below, no AI
Potential impact, not a confirmed outage of your systems.
What the vendor confirmed
What is unknown
Last update in these facts: 2026-11-11 02:12 UTC · summary s1, evidence 03b2e6b33f7c03d8
Evidence (8)
- E1FortiCNAPP (Lacework) reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "New incident: "Container Vulnerability Scans via API/ CLI are experiencing delays"". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor posted it: 2024-02-13 00:57 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2024-02-14 17:00 UTC. (vendor) source (opens in a new tab)
- E8First seen by Statuswall: 2026-11-11 02:12 UTC. (Statuswall)
Affected scope
Not stated by the vendor
Components: not stated by the vendor
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
FortiCNAPP (Lacework) 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.
- Feb 13, 2024, 00:57 UTCVendor posted this incidentVendor time
- Feb 14, 2024, 17:00 UTCVendor-reported resolutionVendor time
- Nov 11, 2026, 02:12 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall