New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages — May 2026
Services Pricing Dashboard

Boomi Outage History

Uptime record, past incidents, and downtime history for Boomi.

Checking current status...
83.5% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Feb 25May 25

Monthly Uptime

Month Uptime Days Tracked Days with Issues
May 2026 96% 25 1
April 2026 83.3% 30 5
March 2026 77.4% 31 7
February 2026 60% 5 2

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Feb 24 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

April 2026
Boomi - Process Reporting Document Metadata Degraded - Resolved
major

Started: Apr 25, 10:35 AM

monitoring
Our engineering team implemented corrective actions to resolve the issues with the Boomi Process Reporting Document Metadata. We are monitoring the situation to ensure continued availability.
Apr 25, 12:30 PM
investigating
Our engineering team continue to investigate the issue and we will provide an update once we have more information. We apologize for any inconvenience this incident has caused.
Apr 25, 11:43 AM
investigating
The Boomi Process Reporting Document Metadata is currently operating at a higher-than-normal latency. You may experience degraded performance during this time. Our engineering team is investigating the issue and we will provide an update once we have more information. We apologize for any inconvenience this incident has caused.
Apr 25, 10:35 AM
March 2026
Boomi - MFT Automated File Sharing - Degraded - Monitoring
major

Started: Mar 31, 1:26 AM

monitoring
Our engineering team implemented corrective actions to resolve the issues with the Boomi Managed File Transfer Cloud. We are monitoring the situation to ensure continued availability.
Mar 31, 2:32 AM
identified
We have identified the cause of the degraded performance you may have experienced on the MFT Automated File Transfer. Our engineering team is working to resolve the issue and we will provide an update once the issue is resolved. We apologize for any inconvenience this incident may have caused.
Mar 31, 1:26 AM