Vendor reports: degradedResolved · vendor status “resolved”Vendor incident feed · inferred
New incident: "Agentless on GCP failing to run within asia-east2 and asia-southeast1 regions"
Reported by FortiCNAPP (Lacework) · Identity & Security · source last read 4 min ago
- Vendor posted
- Apr 23, 2024, 09:31 UTC
- When the vendor's feed dated it
- Resolved
- Apr 24, 2024, 08:34 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
Affected products and regions
- Regions: asia-east2, asia-southeast1 (read from the title, so inferred).[E5]
What is unknown
- Which components are affected: the vendor did not say.[E6]
- 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 b504c8fb2ed07368
Evidence (8)
- E1FortiCNAPP (Lacework) reports degraded. (vendor) source (opens in a new tab)
- E2Vendor title: "New incident: "Agentless on GCP failing to run within asia-east2 and asia-southeast1 regions"". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor posted it: 2024-04-23 09:31 UTC. (vendor) source (opens in a new tab)
- E5Regions written in the title (inferred): asia-east2, asia-southeast1. (Statuswall) source (opens in a new tab)
- E6The vendor attached no components. (Statuswall)
- E7Vendor-reported resolution: 2024-04-24 08:34 UTC. (vendor) source (opens in a new tab)
- E8First seen by Statuswall: 2026-11-11 02:12 UTC. (Statuswall)
Affected scope
asia-east2, asia-southeast1
Components: not stated by the vendor
Read from region codes written in the incident title, so treat it as inferred.
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.
- Apr 23, 2024, 09:31 UTCVendor posted this incidentVendor time
- Apr 24, 2024, 08:34 UTCVendor-reported resolutionVendor time
- Nov 11, 2026, 02:12 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall