FortiSASE incident

FortiGuard Web Category Misclassification in Dallas and Plano

Resolved after 5 hours 23 minutes, affecting Dallas, TX, US (DFW-F1) and Dallas, TX, US (DFW-F2) and 1 more, on July 8, 2026.

monitoring Jul 08, 2026, 03:54 PM UTC

A fix has been implemented and we are monitoring the results.

Started
Jul 08, 2026, 03:06 PM UTC
Resolved
Jul 08, 2026, 08:30 PM UTC
Duration
5h 23m
Detected by Pingoru
Jul 08, 2026, 03:06 PM UTC

Affected components

Dallas, TX, US (DFW-F1)Dallas, TX, US (DFW-F2)Plano, TX, US (DFW-F3)Plano, TX, US (DFW-F4)

Update timeline

  1. investigating Jul 08, 2026, 03:06 PM UTC

    We are investigating an issue affecting customers connected to the Dallas and Plano PoPs where domains with an established rating in FortiGuard may be incorrectly classified as "Unrated" or "Newly Observed Domain" during category lookups. Domains that display a valid web category rating on fortiguard.com are being returned with an incorrect classification, which may result in unexpected policy enforcement behavior for affected traffic. This is being escalated to the FortiGuard team for review. We will provide updates as they become available. If you have questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #542286.

  2. monitoring Jul 08, 2026, 03:54 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jul 08, 2026, 08:30 PM UTC

    This incident has been resolved.

Your product runs on more than FortiSASE

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →