Status Page
Investigating - 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.
Apr 07, 2026 - 17:52 EDT

About This Site

Welcome to ETHERFAX's home for real-time information on system performance and security. Here you will find live and historical data on system performance as well as any service interruptions, and scheduled maintenance. You are able to subscribe to real-time notifications.

Database Infrastructure Operational
Customer Portal Operational
Reseller Portal Operational
Telephony Operational
U.S. Inbound Toll-Free Operational
U.S. Inbound DID Operational
International Inbound Telephony Operational
Canada Inbound Telephony Operational
U.S. Outbound Operational
Canada Outbound Operational
International Outbound Operational
U.S. API Services Operational
U.S. REST Services Operational
U.S. SMS Services Operational
Canada API Services Operational
Canada REST Services Operational
Mobile & Container Applications Operational
DirectFax® for Microsoft Teams Operational
DirectFax® Email-to-Fax Services Operational
DirectFax® Email-to-Fax Services - U.S. Operational
DirectFax® Email-to-Fax Services - CA Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
U.S. REST Uptime
Fetching
U.S. REST Response Time
Fetching
U.S. REST 2.0 Uptime
Fetching
U.S. REST 2.0 Response Time
Fetching
U.S. - DirectFax® Email-to-Fax Services
Fetching
Canada REST Uptime
Fetching
Canada REST Response Time
Fetching
Canada - DirectFax® Email-to-Fax Services
Fetching
Apr 8, 2026

No incidents reported today.

Apr 7, 2026
Resolved - 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.

Apr 7, 17:48 EDT
Update - 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.
Apr 7, 14:51 EDT
Monitoring - 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.

Apr 6, 23:34 EDT
Update - We have just identified and addressed an performance issue with push notifications (web sockets).
Apr 6, 21:44 EDT
Update - Additional fixes have been rolled out to REST services to address additional issues affecting application connectivity to ETHERFAX.
Apr 6, 20:11 EDT
Update - Fixes have just rolled out for interim fax status and latest connected on timestamps.
Apr 6, 17:00 EDT
Update - 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.
Apr 6, 15:09 EDT
Update - 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.
Apr 6, 12:55 EDT
Update - The team is continuing to address several issues within the platform. We are working as expeditiously as possible to address and fix.
Apr 6, 12:54 EDT
Investigating - 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.
Apr 6, 09:47 EDT
Apr 6, 2026
Completed - Work has been completed and systems are validated. If any customers are experiencing issues with the service please reach out to support@etherfax.net.
Apr 6, 00:35 EDT
Update - Engineers are continuing to monitor and validate the migration.
Apr 5, 20:43 EDT
Verifying - We have deployed fixes for the two issues mentioned in the prior update. We are seeing additional customer accounts restore connections. We'll provide additional updates after another round of validations are completed.
Apr 5, 18:25 EDT
Update - The ETHERFAX engineering team has determined there are two issues currently being addressed in the new environment. One issue is causing the delays on inbound and outbound faxing. A second issue was identified with regards to an error on an API call returning account information. This is often used to verify account information on startup. The appropriate teams are addressing those issues now and we hope to have a fix deployed soon. We are already seeing improvement in the delayed jobs issue.
Apr 5, 17:11 EDT
Update - During verification we are seeing some delay issues with both inbound and outbound faxes. We are investigating this issue.
Apr 5, 15:14 EDT
Update - ETHERFAX Engineers have completed the cutover of core services to AWS. We are still seeing some customers lagging on receiving the DNS update, possibly due to host file entries or other factors related to their environment. While engineers are still closely watching the system and continuing further validation checks the initial metrics show the move was successful and we are in an operational state. We will begin re-enabling the alerting mechanisms within AWS.
Apr 5, 13:38 EDT
Update - The team is beginning to modify DNS records. This will begin shifting traffic.
Apr 5, 11:43 EDT
Update - The ETHERFAX engineering team has completed the scheduled work for today's planned tasks. They will continue their work beginning tomorrow morning.
Apr 4, 23:11 EDT
Update - Update from the ETHERFAX Team
Day-of preparations and checklist reviews are in progress. Everything is proceeding smoothly and as planned.

Apr 4, 11:52 EDT
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 4, 00:00 EDT
Scheduled - We are writing to inform you of a planned maintenance window for ETHERFAX core services as we complete a significant infrastructure upgrade.
Maintenance Details:

What: Transition of core ETHERFAX services to enhanced AWS cloud infrastructure.
When: Weekend of April 4-5, 2026 (Saturday, April 4 through Sunday, April 5).
Expected Duration: Work will occur primarily during off-peak hours to minimize impact; however, the full window may span intermittent periods across the weekend.

Our engineering team has thoroughly scripted and tested the migration process to ensure a smooth transition and reduce downtime as much as possible. That said, due to the complexity of moving live services, some interruptions should be anticipated. These may include:

- Temporary unavailability of sending/receiving fax services
- Brief connectivity issues for API integrations or portal access
- Potential delays in historical data availability (e.g., older faxes, logs, or records may take additional time to fully sync and appear in the ETHERFAX portal)

We will monitor the process closely and provide real-time updates via our status page at https://status.etherfax.net/ if any unexpected issues arise.

Action Required for Customers with Outbound Filtering / Firewall Rules:
As part of this migration, we will be publishing new IP addresses for ETHERFAX outbound traffic. To prevent any service disruptions after the cutover:

Please review and allowlist the updated IP ranges in your firewalls, security groups, or outbound filtering policies. These updates are only required if you currently have rules in place to allow traffic to ETHERFAX's current IP list.

IPv4:
API: 15.197.95.44, 13.248.177.255, 99.83.164.54, 166.117.91.254
Push: 52.223.17.196, 76.223.67.44, 15.197.128.239, 99.83.179.2, 15.197.230.197, 166.117.254.53

For customers receiving inbound webhooks from ETHERFAX you'll need to include the following IPs:
3.150.107.183, 3.150.153.61, 3.140.98.225, 16.52.210.150, 15.156.161.107, 3.98.194.93

IPv6:
API: 2600:9000:a709:229e:a279:9514:ea38:7e0c, 2600:9000:a606:e5cf:5849:16c5:3841:a197, 2600:9000:a709:229e:db6b:dc5d:b917:6af7, 2600:9000:a606:e5cf:a90b:814e:201d:4c84

Push: 2600:9000:a709:229e:fb6a:2674:bdc9:3d11, 2600:9000:a606:e5cf:6320:1a59:b3a1:9a63, 2600:9000:a606:e5cf:af62:e5fa:9028:d28, 2600:9000:a709:229e:acb8:f767:d7f7:26d5, 2600:9000:a606:e5cf:cdec:f3c9:9781:d5be, 2600:9000:a709:229e:926d:7633:5f12:eaee

Should you have any questions please reach out to the ETHERFAX support team (support@etherfax.net)

Best regards,
The ETHERFAX Team

Mar 19, 15:31 EDT
Apr 5, 2026
Apr 4, 2026
Apr 3, 2026

No incidents reported.

Apr 2, 2026

No incidents reported.

Apr 1, 2026

No incidents reported.

Mar 31, 2026

No incidents reported.

Mar 30, 2026

No incidents reported.

Mar 29, 2026

No incidents reported.

Mar 28, 2026

No incidents reported.

Mar 27, 2026

No incidents reported.

Mar 26, 2026

No incidents reported.

Mar 25, 2026

No incidents reported.