Vendor reports: operationalResolved · vendor status “resolved”Official status API
Firewall module auto-installation on a subset of devices
Reported by Bitdefender GravityZone · Identity & Security · source last read 2 min ago
- Vendor start
- Nov 4, 2025, 20:24 UTC
- Vendor's clock
- Resolved
- Nov 10, 2025, 12:28 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 5 d 16 h
- 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
Affected products and regions
- Components: Windows, Management Console, Management Console.[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: 2025-11-10 12:28 UTC · summary s1, evidence e9fe0fedd68a0a16
Evidence (7)
- E1Bitdefender GravityZone reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Firewall module auto-installation on a subset of devices". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2025-11-04 20:24 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Windows, Management Console, Management Console. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2025-11-10 12:28 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Windows, Management Console, Management Console
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
Bitdefender GravityZone 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.
- Nov 4, 2025, 20:24 UTCVendor-reported startVendor time
- Nov 10, 2025, 12:28 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.