ETHERFAX Outage History

Started Oct 30, 2026, 09:30 PM UTC· resolved Oct 30, 2026, 10:43 PM UTC

1. investigating Oct 30, 2026, 09:30 PM UTC

   ETHERFAX Telecom Engineers are engaged with one of our toll-free carrier support team to determine the cause for dead air on some inbound calls to toll free numbers. At this time the issue is affecting some portion of calls and is not a complete outage. ETHERFAX engineers have identified in call traces the differences between a successful an failing call and have provided that information to the carrier for further analysis.

2. monitoring Oct 30, 2026, 10:07 PM UTC

   Carrier has identified and corrected the routing issue. The ETHERFAX team is seeing successful call completions and normal call completion metrics on the affected circuits.

3. resolved Oct 30, 2026, 10:43 PM UTC

   We are continuing to see normal call completions and no evidence of the routing issue present any longer.

Read the full incident report →

Started Oct 21, 2026, 04:08 PM UTC· resolved Oct 22, 2026, 08:00 AM UTC

1. monitoring Oct 21, 2026, 04:08 PM UTC

   As a precaution, we have temporarily restricted public access to the ETHERFAX corporate website. This step aligns with guidance from leading cybersecurity firms regarding a recently disclosed critical PHP vulnerability.Production systems are unaffected. All ETHERFAX production services including API, client portals, partner portals, APIs, and all customer environments continue to operate normally. Those environments do not utilize PHP. We expect to restore website access once our hosting provider confirms a patched PHP version is in place. For assistance in the meantime, contact support at [email protected]. Thank you for your patience.

2. monitoring Oct 21, 2026, 04:38 PM UTC

   Patches and mitigating steps for the PHP vulnerabilities have begun to be released. Our corporate website hosting provider is working to roll these updates out across platforms as soon as possible. Protective mitigations have also already been deployed at the CDN layer. We will share further updates as deployment progresses. Once again this DOES NOT affect the ETHERFAX Production systems.

3. resolved Oct 22, 2026, 08:00 AM UTC

   The corporate website hosting provider has completed patching. Additional protection mitigations remain attached to the CDN layer should this vulnerability evolve over the coming days. The ETHERFAX security team has restored access to the corporate website. Thank you for your patience.

Read the full incident report →

Started Aug 18, 2026, 10:16 PM UTC· resolved Aug 20, 2026, 08:23 AM UTC

1. investigating Aug 18, 2026, 10:16 PM UTC

   ETHERFAX is investigating a possible carrier outage affecting some inbound and outbound circuits servicing our New York telecom POP. We have shifted traffic away from these circuits/carrier as we investigate with the carrier further. At this time there should be no impact to customers. Prior to our mitigation efforts some customers may have seen a higher than normal outbound failure rate or reports from senders of inbound busy signals. The team is engaged with the carrier for resolution.

2. identified Aug 19, 2026, 07:19 AM UTC

   The affected carrier has technicians working on the affected circuits. Once again, customer traffic has been moved off of those circuits. The next update will occur once we have feedback from carrier side.

3. resolved Aug 20, 2026, 08:23 AM UTC

   Carrier has addressed an issue with an upstream regional OC48 (fiber backbone) circuit. ETHERAX team is now seeing the affected circuits back up. Testing has been conducted and circuits have resumed normal service within our network.

Read the full incident report →

Started May 27, 2026, 02:41 PM UTC· resolved Jun 09, 2026, 08:40 PM UTC

1. investigating May 27, 2026, 02:41 PM UTC

   Engineers are currently reviewing reports of some ERIS instances pulling inbound faxes multiple times. This incident at this time appears isolated to installs of ERIS.

2. identified May 27, 2026, 03:44 PM UTC

   Engineers are addressing these issues on the affected customer accounts to prevent the duplicates.

3. monitoring May 27, 2026, 09:51 PM UTC

   Engineers have continuned to monitor those customer's accounts who are utilizing the ERIS product and are affected by this. This issue is being addressed from two different angles, one on the ETHERFAX API side to understand a condition that causes ERIS to make multiple attempts to retrieve a job and second, from the ERIS side to help guard against this condition should it be encountered.

4. resolved Jun 09, 2026, 08:40 PM UTC

   Engineers have continued monitoring this and have put additional alerting in place to guard against this on the API side. Additionally, developers are continuing to work on a fix for this issue inside of ERIS.

Read the full incident report →

Started May 11, 2026, 02:35 PM UTC· resolved May 11, 2026, 02:48 PM UTC

1. investigating May 11, 2026, 02:35 PM UTC

   Engineers are looking into some outbound faxing delays on the platform.

2. resolved May 11, 2026, 02:48 PM UTC

   Engineers responded to metric alarms indicating some minor delays. After analyzing the logs, alerts, and the system performance overall the team determined that there was no impact.

Read the full incident report →

Started Apr 28, 2026, 05:00 PM UTC· resolved Apr 28, 2026, 05:00 PM UTC

1. resolved Apr 28, 2026, 09:45 PM UTC

   After a routine update of our email publisher service engineers determined that users subscribed to our fax to email services were receiving fax attachments as TIFF versus PDF files. The attachments were named with a .pdf extension causing some viewers to indicate they were corrupt. Users are able to open the files by changing the file extension to a .tiff rather than a .pdf. Engineers performed an update to the address the issue around 15:30 EDT.

Read the full incident report →

Started Apr 07, 2026, 09:52 PM UTC· resolved Apr 09, 2026, 04:23 PM UTC

1. investigating Apr 07, 2026, 09:52 PM UTC

   Engineers are currently investigating the error code E-e83 SENx 1M30 when sending SENx payloads between Lexmark devices. Transmissions are completed but do not show success on the sending device.

2. identified Apr 08, 2026, 05:39 PM UTC

   Engineers have identified the issue with SENx payloads between Lexmark devices. This affects transmissions between two Lexmark devices on ETHERFAX. Final validation checks are being performed and a fix will be rolling out shortly after.

3. monitoring Apr 08, 2026, 05:54 PM UTC

   The fix for transmissions between two Lexmark devices on ETHERFAX has been deployed.

4. investigating Apr 08, 2026, 06:58 PM UTC

   Engineers have observed an abnormality with this change and are reverting for further investigation.

5. monitoring Apr 08, 2026, 11:13 PM UTC

   A new update has been released to address this issue.

6. resolved Apr 09, 2026, 04:23 PM UTC

   Continued monitoring and validations confirm this issue is resolved.

Read the full incident report →

Started Apr 06, 2026, 01:47 PM UTC· resolved Apr 07, 2026, 09:48 PM UTC

1. investigating Apr 06, 2026, 01:47 PM UTC

   Engineers are continuning to monitor some issues with ETHERFAX affecting certain integrations. Currently we are seeing an issue affecting customers using GFI FaxMaker and those customers connecting directly to our EPIC endpoint. Our engineering and development teams are actively working on these issues. We will post any additional findings,updates, or issues to this incident.

2. investigating Apr 06, 2026, 04:54 PM UTC

   The team is continuing to address several issues within the platform. We are working as expeditiously as possible to address and fix.

3. investigating Apr 06, 2026, 04:55 PM UTC

   Some customers may be receiving erroneous alerts indicating they are not connected, however, they are in fact connecting. Please check your application and you can also confirm fax transactions within the ETHERFAX portal.

4. investigating Apr 06, 2026, 07:09 PM UTC

   The team has fixes for the connection alerts and connected on timestamps and those will be deploying shortly. We also are addressing an issue with interim fax status not getting updated.

5. investigating Apr 06, 2026, 09:00 PM UTC

   Fixes have just rolled out for interim fax status and latest connected on timestamps.

6. investigating Apr 07, 2026, 12:11 AM UTC

   Additional fixes have been rolled out to REST services to address additional issues affecting application connectivity to ETHERFAX.

7. investigating Apr 07, 2026, 01:44 AM UTC

   We have just identified and addressed an performance issue with push notifications (web sockets).

8. monitoring Apr 07, 2026, 03:34 AM UTC

   Our engineers and developers have completed their work for the day. All ongoing maintenance and improvements have been successfully implemented, and the platform is currently stable with normal performance across all services. We do realize that some customers utilizing GFI FaxMaker are still having issues connecting. We will be reaching out to those customers tomorrow for further instructions and troubleshooting efforts. The infrastructure team will continue to monitor system metrics and performance closely throughout tomorrow. If you experience any issues tomorrow, please reach out to us individually via support ticket or your dedicated account contact so we can assist you promptly. Thank you for your patience and continued trust in our platform. We appreciate your partnership.

9. monitoring Apr 07, 2026, 06:51 PM UTC

   Engineers have continued to monitor the system through today and we are still seeing good metrics from the system as well as customer and device connections. An additional fix was rolled out to address a few customers on REST 1.0 API. This mainly affected GFI FaxMaker customers. We continue to monitor the system very closely.

10. resolved Apr 07, 2026, 09:48 PM UTC

    ETHERFAX engineers continue to observe stable performance across the platform. One remaining issue has been identified, affecting a small percentage of traffic involving Lexmark devices connected to ETHERFAX when exchanging SENx payloads. This issue is currently under investigation and will be addressed separately. A new incident will be created to track and manage this specific issue. The current incident will be closed. Additionally, ETHERFAX will publish a Root Cause Analysis and Resolution Summary (RFO) to address the issues encountered during the recent migration. We greatly value the business of our customers and partners and sincerely appreciate their patience and continued support during this time.

Read the full incident report →

Started Mar 24, 2026, 06:29 PM UTC· resolved Mar 25, 2026, 01:24 AM UTC

1. monitoring Mar 24, 2026, 06:29 PM UTC

   ETHERFAX is aware of an issue with the DirectFax for Microsoft Teams application. This is currently related to an ongoing Microsoft incident regarding Microsoft Teams and their bot services. We are continuing to monitor this incident with Microsoft.

2. monitoring Mar 24, 2026, 07:43 PM UTC

   We are continuing to monitor our error metrics and have begun to see some restoral related to the Microsoft Teams issue (Issue ID# TM1260604). Inbound faxes that were pending delivery to Teams endpoints are resuming delivery.

3. resolved Mar 25, 2026, 01:24 AM UTC

   Microsoft has resolved the issue affecting Microsoft Teams Bot Services endpoints and the ETHERFAX team is seeing successful API calls to the service via the Microsoft Graph API.

Read the full incident report →

Started Sep 04, 2025, 08:10 PM UTC· resolved Sep 05, 2025, 02:11 AM UTC

1. investigating Sep 04, 2025, 08:10 PM UTC

   ETHERFAX engineers are currently engaged with a single carrier regarding inbound failures. This is affecting some US inbound DID numbers on the ETHERFAX platform.

2. investigating Sep 04, 2025, 09:21 PM UTC

   Engineers are still working to identify the cause of the failures.

3. investigating Sep 04, 2025, 10:31 PM UTC

   The ETHERFAX team is still working with carrier team to restore service.

4. identified Sep 04, 2025, 11:43 PM UTC

   We are seeing partial restoration of services at this time. The team is continuing to monitor.

5. monitoring Sep 04, 2025, 11:57 PM UTC

   ETHERFAX have continued to monitor calls and all metrics are looking normal. We'll continue to monitor closely for the next few hours.

6. resolved Sep 05, 2025, 02:11 AM UTC

   Monitoring has continued to show positive metrics. This incident will be marked as resolved.

Read the full incident report →

Started Aug 22, 2025, 08:06 PM UTC· resolved Aug 23, 2025, 01:20 AM UTC

1. investigating Aug 22, 2025, 08:06 PM UTC

   ETHERFAX engineering is currently investigating an increase in call failures with one of our carrier partners. At this time some inbound faxes may be failing at a higher than expected rate or callers may be encountering busy signals. The team is working with the carrier partner and is working to push calls over alternate paths.

2. investigating Aug 22, 2025, 09:08 PM UTC

   We are continuing to investigate this issue with our carrier partner.

3. identified Aug 22, 2025, 09:27 PM UTC

   ETHERFAX engineers have successfully pushed calls to an alternate path and we are seeing partial restoration. We're continuing to monitor and ensure acceptable levels of service.

4. monitoring Aug 22, 2025, 10:33 PM UTC

   We're continuing to monitor but results and metrics continue to be positive.

5. resolved Aug 23, 2025, 01:20 AM UTC

   This incident has been resolved.

Read the full incident report →

Started Mar 23, 2025, 05:14 PM UTC· resolved Mar 24, 2025, 01:36 AM UTC

1. investigating Mar 23, 2025, 05:14 PM UTC

   Engineers are currently aware of an issue affect a hardware switch in our Denver data center. The team is working to route calls off this switch to alternate paths.

2. investigating Mar 23, 2025, 05:22 PM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 23, 2025, 05:46 PM UTC

   ETHERFAX staff have worked with personnel inside data center to power cycle the equipment. It has returned to normal operation. Numbers have been rerouted around this issue and engineers are monitoring.

4. resolved Mar 24, 2025, 01:36 AM UTC

   Monitoring has continued to show normal call completions. We are going to go ahead and close this incident.

Read the full incident report →

Started Mar 06, 2025, 01:16 AM UTC· resolved Mar 19, 2025, 06:24 PM UTC

1. investigating Mar 06, 2025, 01:16 AM UTC

   ETHERFAX engineers are investigating an ISP level routing issue impacting connectivit to the API. Changes have been initiated to route around the impacted ISP.

2. identified Mar 06, 2025, 01:42 AM UTC

   Our primary ISP has reported a widespread issue. We have completed DNS updates to route API traffic around the affected provider. Engineers are continuing to monitor services and failover processes.

3. identified Mar 06, 2025, 03:26 AM UTC

   Most services have restored fully through alternate paths. Engineers continue to work with our ISP and monitor performance.

4. monitoring Mar 06, 2025, 05:45 AM UTC

   All services are operating as expected. For any applications that remain unable to access our API or endpoints, ensure that outbound firewall rules permit this access. DNS changes made during failover events mean that hard-coded IP address rules or DNS entries may prevent normal operation. Engineers will continue to monitor performance of the network into tomorrow.

5. monitoring Mar 06, 2025, 04:07 PM UTC

   Engineers are beginning to move some services back to primary ISP. An issue was noted with DirectFax Email Services rejecting emails due to a configuration error with our domain validation check. This was just resolved.

6. resolved Mar 19, 2025, 06:24 PM UTC

   The affected ISP has issued their RFO and advised a hardware card failure on their network backbone. An ISP field engineer dispatch was required to move traffic off. A new card was shipped to site and was replaced by the field engineer. Note, ETHERFAX kept the incident open although in a monitoring state until the repair was completed by the ISP.

Read the full incident report →

Started Dec 05, 2024, 03:25 PM UTC· resolved Dec 12, 2024, 09:44 PM UTC

1. investigating Dec 05, 2024, 03:25 PM UTC

   ETHERFAX is aware of a possible carrier incident affecting some inbound toll-free numbers. While some mitigation steps have been taken on the carrier side failed calls are still being reported which are not reaching the ETHERFAX network. ETHERFAX is actively engaged with both carrier and RESPOrg parties involved in the toll-free routing process.

2. investigating Dec 05, 2024, 04:56 PM UTC

   ETHERFAX is still actively engaged with both RESPOrg and Carrier contacts to coordinate a restoration.

3. investigating Dec 05, 2024, 07:42 PM UTC

   While the affected carrier is still performing investigations on the actual circuit, we initiated a routing template update with the RespOrg across all of our affected toll-free numbers. This has now been 95% completed and we are seeing positive results. As mentioned, investigation continues with the affected carrier to determine and address root cause.

4. monitoring Dec 06, 2024, 02:35 AM UTC

   The situation is stable at this time as a result of the routing updates earlier in the day. ETHERFAX continues to be engaged with our carrier partner experiencing the issue while they continue to investigate and determine the root cause.

5. resolved Dec 12, 2024, 09:44 PM UTC

   ETHERFAX's carrier partners have returned the toll-free routing the pre-incident configuration. We have continued to monitor the situation and all we are receiving positive indicators on all monitoring. A full post-mortem will be published on this incident in the coming days.

Read the full incident report →