Live / FortiSASE / Incident
FortiSASE: Datacenter Reachability Issue for Miami Tenants
FortiSASE · fortisase.comResolved2026-11-12 17:47 UTC
Public — what happened
Summary
FortiSASE said customers whose service runs through its Miami locations had a reachability problem, which it described as short-lived and which affected two points of presence, MIA-F3 and MIA-F4. It said it began at 16:24 UTC on 2026-11-12 and that traffic was automatically sent through other locations in the meantime. FortiSASE said it identified the cause, applied countermeasures, and saw traffic returning to normal, and the incident was marked resolved at 17:47 UTC.
Affected
Miami, FL, US (MIA-F3), Miami, FL, US (MIA-F4)
Timeline
- Started — 2026-11-12 16:24 UTC
- Monitoring — 2026-11-12 16:24 UTC
- Resolved — 2026-11-12 17:47 UTC · 1h 23m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach FortiSASE against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for FortiSASE: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the FortiSASE report →
More from FortiSASE
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.