Resolved after 8 hours 17 minutes, affecting Vancouver, Canada (YVR-F2), on July 16, 2025.
During our monitoring, everything was nominal, so we're proceeding to resolve this incident. For any further queries or still particular pertaining issue, please contact FortiCare Support.
Affected components
Update timeline
- investigating Jul 16, 2025, 07:43 AM UTC
A network issue has been identified at the Vancouver PoP and is currently being investigated. Traffic has been automatically re-routed to other PoPs. If you have any questions regarding this incident, please contact FortiCare Support ( and reference FortiSASE Operations ticket #370389.
- investigating Jul 16, 2025, 10:29 AM UTC
Some affected instances are recovering, but there's more affected still. We're actively working on it.
- investigating Jul 16, 2025, 12:23 PM UTC
A partial fix has been implemented and we're seeing many resolutions in our monitoring, but we're still actively working with the infrastructure team to address the caused incident.
- monitoring Jul 16, 2025, 01:22 PM UTC
Situation has now normalized, we'll keep monitoring the affected tenants for any weird behaviours or resurgence.
- resolved Jul 16, 2025, 04:01 PM UTC
During our monitoring, everything was nominal, so we're proceeding to resolve this incident. For any further queries or still particular pertaining issue, please contact FortiCare Support.
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.
Amazon Web Services