Vendor reports: operationalResolved · vendor status “resolved”Official status API
Domain Categorization & System Load
Reported by DNSFilter · Identity & Security · source last read 3 min ago
- Vendor start
- Jun 20, 2025, 17:07 UTC
- Vendor's clock
- Resolved
- Jun 23, 2025, 12:51 UTC
- Vendor's clock
- First seen by Statuswall
- Before tracking began
- Statuswall's clock
- Duration
- 2 d 19 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: Domain Categorization.[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-06-23 12:51 UTC · summary s1, evidence fa802137bf9a67be
Evidence (7)
- E1DNSFilter reports operational. (vendor) source (opens in a new tab)
- E2Vendor title: "Domain Categorization & System Load". (vendor) source (opens in a new tab)
- E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
- E4Vendor-reported start: 2025-06-20 17:07 UTC. (vendor) source (opens in a new tab)
- E5The vendor did not state which regions are affected. (Statuswall)
- E6Components the vendor attached: Domain Categorization. (vendor) source (opens in a new tab)
- E7Vendor-reported resolution: 2025-06-23 12:51 UTC. (vendor) source (opens in a new tab)
Affected scope
Not stated by the vendor
Components: Domain Categorization
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
DNSFilter 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.
- Jun 20, 2025, 17:07 UTCVendor-reported startVendor time
- Jun 23, 2025, 12:51 UTCVendor-reported resolutionVendor time
No changes observed yet. Statuswall began recording changes on incidents in November 2026.