FortiSASE experienced a major incident on May 5, 2026 affecting Sydney, Australia (SYD-O1), lasting 44m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 05, 2026, 09:51 PM UTC
We are investigating a network issue at the Sydney, Australia (SYD-O1) PoP. Traffic has been automatically re-routed to other PoPs. If you have any questions regarding this incident, please contact FortiCare Support (https://www.fortinet.com/support/contact) and reference FortiSASE Operations ticket #485163
- monitoring May 05, 2026, 10:05 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 05, 2026, 10:36 PM UTC
This incident has been resolved.
Looking to track FortiSASE downtime and outages?
Pingoru polls FortiSASE's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when FortiSASE reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track FortiSASE alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required