All Systems Operational

About This Site

The FortiMail Cloud - Hosted Status page provides up to date information on the current service health. Please subscribe for updates.

Uptime over the past 90 days. View historical uptime.
FortiGuard Network Operational
90 days ago
100.0 % uptime
Today
FortiMail Cloud - Hosted Portal Operational
90 days ago
100.0 % uptime
Today
Datacenters Operational
90 days ago
99.95 % uptime
Today
(CANADA) Vancouver Operational
90 days ago
100.0 % uptime
Today
(CANADA) Toronto Operational
90 days ago
100.0 % uptime
Today
(US) San Jose Operational
90 days ago
99.81 % uptime
Today
(US) Dallas Operational
90 days ago
99.38 % uptime
Today
(US) Miami Operational
90 days ago
100.0 % uptime
Today
(US) Plano Operational
90 days ago
100.0 % uptime
Today
(EMEA) Frankfurt Operational
90 days ago
100.0 % uptime
Today
(EMEA) London Operational
90 days ago
100.0 % uptime
Today
(EMEA) Paris Operational
90 days ago
100.0 % uptime
Today
(EMEA) Dubai Operational
90 days ago
100.0 % uptime
Today
(EMEA) Madrid Operational
90 days ago
100.0 % uptime
Today
(Japan) Tokyo Operational
90 days ago
100.0 % uptime
Today
(Japan) Japan KMG Operational
90 days ago
100.0 % uptime
Today
(APAC) Singapore Operational
90 days ago
100.0 % uptime
Today
(APAC) Sydney Operational
90 days ago
100.0 % uptime
Today
(APAC) Bangalore Operational
90 days ago
100.0 % uptime
Today
(APAC) Pune Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Jun 6, 2026

No incidents reported today.

Jun 5, 2026
Scheduled Maintenance for Japan KMG site
Completed - All maintenance has been completed.
Jun 5, 19:04 UTC
Verifying - All maintenance has been completed and we are monitor and verifying the change to make sure all service running as expected.
Jun 5, 18:58 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 5, 15:00 UTC
Scheduled - We are writing to inform you that an upcoming activity will be performed on the FortiMail Cloud Japan KMG DC site as part of internal site changes. This activity will result in changes to the inbound IP addresses used by your service.

As part of this activity, the following inbound IP addresses for the Japan KMG site will be updated as follows:
IP Address Change Details:
• 154.52.29.130 —> 176.23.144.130 (For LDAP and remote logging)
• 154.52.29.131 —> 176.23.144.131 (Email Delivery (SMTP))
• 154.52.29.132 —> 176.23.144.132 (MX Record (-1/-2))

The following changes are required on your side:
1. Whitelist 176.23.144.131 to allow email delivery from the FortiMail Cloud tenant to your SMTP server, if the Recipient Address Verification (RAV) server and the SMTP server use the same IP address.
2. Allow 176.23.144.130 if you are using Recipient Address Verification (RAV) and LDAP server IP differs from your SMTP server IP.

Maintenance Window:
JST: June 6, 2026 | 12:00 AM – 5:00 AM
EDT: June 5, 2026 | 11:00 AM – 4:00 PM

Important Notes:
• There is no change to MX records; your mail routing configuration remains unaffected.
• Email delivery and security filtering services are expected to continue operating normally.
• If you require any further clarification or assistance, please feel free to reach out to the SE at any time.

This activity is intended to support High Availability (HA) pairing and to maintain service stability and performance for FortiMail Cloud customers.
May 14, 14:05 UTC
Jun 4, 2026

No incidents reported.

Jun 3, 2026

No incidents reported.

Jun 2, 2026

No incidents reported.

Jun 1, 2026

No incidents reported.

May 31, 2026

No incidents reported.

May 30, 2026

No incidents reported.

May 29, 2026

No incidents reported.

May 28, 2026

No incidents reported.

May 27, 2026

No incidents reported.

May 26, 2026

No incidents reported.

May 25, 2026

No incidents reported.

May 24, 2026

No incidents reported.

May 23, 2026
FortiMail Cloud Madrid Data Center Maintenance
Completed - Infra team has confirmed that the maintenance has been completed.
May 23, 00:30 UTC
Verifying - The maintenance has been complete and all service should restore as normal now. FortiMail Cloud Admin team will continue to monitor the service.
May 23, 00:28 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
May 22, 23:00 UTC
Scheduled - This scheduled maintenance that may result in temporary service impact. These maintenance activities are required to support continued service operation.

No action is required on your part. All existing IP addresses (IPs) and fully qualified domain names (FQDNs) will remain unchanged.

Maintenance Window:
Date: May 22, 2026
Time: 7:00 PM EDT to 11:59 PM EDT

Expected Impact:
• During the maintenance window, the service may experience brief periods of degradation.
• Access to new and historical message logs and quarantined emails will be temporarily unavailable during the maintenance window.
• During the maintenance, email traffic will be routed to your secondary/backup tenant.
• Configuration changes will be temporarily unavailable during the maintenance window.

After the maintenance is completed:
• Access to new and historical data, including quarantined emails accumulated on the secondary tenant, will be restored.
• Message logs generated while traffic is routed to the secondary tenant will be restored to the primary tenant.

Further Information:
• Updates are provided throughout the maintenance process.
• The latest service updates can be found at: https://fortimailcloud.statuspage.io/

If you have any questions or concerns, please open a support ticket with our Technical Assistance Center (TAC), and our team will be happy to assist you.

Thank you for your understanding and cooperation as we work to enhance our email security services. We appreciate your continued trust in our products.

Kind regards,
FortiMail Cloud Admin
May 13, 18:04 UTC
← Incident History Powered by Atlassian Statuspage