Live  /  Providers  /  FortiSASE

FortiSASE

fortisase.comNo open incidents

Independent assessment — SquidGrid is not affiliated with FortiSASE. Provider-published information is labeled as such; SquidGrid’s own measurements are observations of network paths, not determinations of fault.

SaaS & business software · SquidGrid tracks FortiSASE’s own status and independently measures the internet paths that reach it, so you can tell a provider-side problem from a problem on the route to it.

Public — what FortiSASE is reporting

Current & recent incidents

Resolved

Datacenter Reachability Issue for Miami Tenants

None impact · 2026-11-12 17:47 UTC · source

Resolved

User Authentication Issue

None impact · 2026-09-27 14:28 UTC · source

Resolved

FortiSASE Endpoint Management Service Degradation

Minor impact · 2026-09-04 22:29 UTC · source

Resolved

FortiCare Authentication Issue

None impact · 2026-09-04 20:06 UTC · source

Incident titles and states as published by the provider. Times in UTC.

Track record

SquidGrid has archived 6 incidents from FortiSASE’s own status page since 2026-09-04.

Recent incidents in the archive

Computed by SquidGrid from the incidents FortiSASE published. Their own page shows only recent history; this archive keeps every one.

Independent path health

A status page tells you what FortiSASE has published. SquidGrid independently observes the actual routes from its own worldwide fleet against their own baselines — so when a path moves off its usual range before (or without) a status post, you still see it, and you see where.

FortiSASE runs its services on other companies’ networks rather than operating its own, so path measurements roll up to its hosting providers. SquidGrid’s assessment of FortiSASE is its published incident record, archived and analyzed above and kept after the provider’s own page forgets it.

SquidGrid is not affiliated with FortiSASE.