Scheduled Maintenance – ETHERFAX Core Services Transition to AWS – April 4-5, 2026

Scheduled Maintenance Report for ETHERFAX

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.
Posted Apr 06, 2026 - 00:35 EDT

Update

Engineers are continuing to monitor and validate the migration.
Posted Apr 05, 2026 - 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.
Posted Apr 05, 2026 - 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.
Posted Apr 05, 2026 - 17:11 EDT

Update

During verification we are seeing some delay issues with both inbound and outbound faxes. We are investigating this issue.
Posted Apr 05, 2026 - 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.
Posted Apr 05, 2026 - 13:38 EDT

Update

The team is beginning to modify DNS records. This will begin shifting traffic.
Posted Apr 05, 2026 - 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.
Posted Apr 04, 2026 - 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.
Posted Apr 04, 2026 - 11:52 EDT

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Apr 04, 2026 - 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
Posted Mar 19, 2026 - 15:31 EDT
This scheduled maintenance affected: U.S. API Services (U.S. REST Services, U.S. SMS Services), Canada API Services (Canada REST Services), DirectFax® Email-to-Fax Services (DirectFax® Email-to-Fax Services - U.S., DirectFax® Email-to-Fax Services - CA), Mobile & Container Applications (DirectFax® for Microsoft Teams), and Database Infrastructure, Customer Portal, Reseller Portal.