mFax Intermittent Inbound Fax Failures - Incident details - UCaaS Status Page - Status

mFax Intermittent Inbound Fax Failures

Resolved

Operational

Started about 1 year agoJuly 14, 2025Lasted 1 dayJuly 14, 20254:38 PMJuly 15, 20255:43 PMUTC

Affected

Core Services

Ashburn (IAD) Voice

Atlanta (ATL) Voice

Grand Rapids (GRR) Voice

Las Vegas (LAS) Voice

Phoenix (PHX) Voice

Updates

Resolved
July 15, 2025 at 5:43 PMUTC
Resolved
July 15, 2025 at 5:43 PMUTC
As of 2:58am, July 15, 2025 mfax is showing the implemented fix performed by their telecom provider is successful and all inbound faxes are working as intended.
After 24 hours of monitoring with no additional inbound fax failures, This incident is now considered resolved.
Monitoring
July 14, 2025 at 6:40 PMUTC
Monitoring
July 14, 2025 at 6:40 PMUTC
Current Status: A fix has been implemented with successful faxes received.
Next Steps: We will continue to monitor for the next 24 hours.
Next Update: 2:35 PM ET June 15, 2025
Update
July 14, 2025 at 5:30 PMUTC
Update
July 14, 2025 at 5:30 PMUTC
What Is Affected: mFax

When It Began: 11:45 AM ET June 14, 2025

Current Status: The vendor is currently investigating.

Next Steps: No action required.

Next Update: 2:35 PM ET June 14, 2025
Investigating
July 14, 2025 at 4:38 PMUTC
Investigating
July 14, 2025 at 4:38 PMUTC
At 11:45 AM ET, the mFax vendor reported a subset of inbound numbers failing with a "no fax tone detected" error. This is due to one of the vendor's upstream telecom providers experiencing intermittent failures.

What Is Affected: mFax

When It Began: 11:45 AM ET June 14, 2025

Current Status: The vendor is currently investigating.

Next Steps: No action required.

Next Update: 1:35 PM ET June 14, 2025