Appendix E - Monthly maintenance
This topic describes the monthly maintenance schedule and impact for FortiSASE.
Monthly maintenance impact
During a scheduled maintenance window, Fortinet performs a rolling software update, which means not all instances are upgraded at the same time, with some instances still running the previous software version.
There is potential for short connectivity impact (approximately one to two minutes) for each customer instance and the configuration portal while these components are updated.
Endpoint management functionalities, including endpoint profile configuration and some zero trust network access (ZTNA) functionality, may be intermittently inaccessible while the upgrade is occurring.
For a list of new features included in the FortiSASE software release, see What’s new.
Monthly maintenance schedule
To change your FortiSASE instance’s maintenance window, contact Fortinet Support to request a change through a new technical support ticket. See Security PoPs for details on the impact of any security PoP changes.
Typically, Fortinet performs monthly software upgrades for customers’ FortiSASE instances during the first or second week of the month.
To minimize customer impact, rolling software upgrades are performed per region within an eight-hour maintenance window outside of business hours for the customer’s primary security PoP at the equivalent local time:
| Group | Time range EST (UTC) | Time range EDT (UTC) |
|---|---|---|
| Maintenance window group 1 | 12 PM to 8 PM EST (17:00-01:00 UTC) | 12 PM to 8 PM EDT (16:00-00:00 UTC) |
| Maintenance window group 2 | 6 AM to 2 PM EST (11:00-19:00 UTC) | 6 AM to 2 PM EDT (10:00-18:00 UTC) |
| Maintenance window group 2 (Japan) | 9 AM to 5 PM EST (14:00-22:00 UTC) | 9 AM to 5 PM EDT (13:00-21:00 UTC) |
| Maintenance window group 3 | 4 PM to 12 AM EST (next day) (21:00-05:00 UTC) | 4 PM to 12 AM EST (next day) (20:00-04:00 UTC) |
To change your default upgrade window to a preferred maintenance time slot, see Software audit & version.
In addition to these maintenance window groupings, there is a Later group that a tenant can request to be included in, which schedules their upgrade during the last possible maintenance window (group 3) for upgrades. Contact Fortinet Support to request a schedule change through a new technical support ticket.
Maintenance window group 1: 12 PM to 8 PM EST/EDT
|
Fortinet cloud locations |
Public cloud locations |
|---|---|
|
Bangalore |
Amsterdam |
|
Dubai |
Auckland |
|
Frankfurt |
Damman |
|
Hong Kong |
Doha |
|
Istanbul |
Dubai |
|
Johannesburg |
Frankfurt |
|
Madrid |
Hamina |
|
Paris |
Hong Kong |
|
Pune |
Jakarta |
|
Valbonne |
Johannesburg |
|
Madrid |
|
|
|
Manila |
|
Melbourne |
|
|
Milan |
|
|
Mumbai |
|
| Paris | |
|
|
Perth |
|
|
St.Ghislain |
|
|
Taipei |
|
|
Tel Aviv |
|
|
Warsaw |
|
|
Zurich |
Maintenance window group 2: 6 AM to 2 PM EST/EDT
|
Fortinet cloud locations |
Public cloud locations |
|---|---|
|
Dallas/Plano |
Chicago |
|
San Jose |
Dallas |
|
Singapore |
Las Vegas |
|
Sydney |
Portland |
| Vancouver |
Querétaro |
|
|
Seoul |
|
|
Singapore |
Maintenance window group 2 (Japan): 9 AM to 5 PM EST/EDT
|
Fortinet cloud locations |
Public cloud locations |
|---|---|
| Komagome | Osaka |
| Tokyo |
This maintenance window is the default for new instances with Japanese security PoPs selected, and for existing instances with Japanese security PoPs with this window selected by their administrators.
Maintenance window group 3: 4 PM to 12 AM EST/EDT
| Fortinet cloud locations | Public cloud locations |
|---|---|
| Ashburn | Ashburn |
|
London |
Buenos Aires |
| Miami | Dublin |
|
Ottawa |
Lima |
|
Sao Paulo |
London |
| Toronto | Miami |
|
|
Santiago |
|
|
Sao Paulo |
|
|
Toronto |
The Later group of instances to be upgraded is included in this maintenance window. See the note in Monthly maintenance schedule.