Phaxio Outage History

Phaxio had 8 outages in the last 2 years totaling 10h 53m of downtime — averaging 0.3 incidents per month.

There were 8 Phaxio outages since October 23, 2024 totaling 10h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: http://status.phaxio.com

Notice September 25, 2026

Auto-Recharge Currently Unavailable

Detected by Pingoru: Sep 25, 2026, 08:17 PM UTC
Resolved: Sep 25, 2026, 09:37 PM UTC
Duration: 1h 19m

Timeline · 2 updates

investigating Sep 25, 2026, 08:17 PM UTC

We are currently investigating an issue affecting the Auto-Recharge feature. Our team is working to restore functionality as quickly as possible. In the meantime, you can manually add funds to your account as needed. We will provide an update once Auto-Recharge has been restored.
resolved Sep 25, 2026, 09:37 PM UTC

We have identified the issue affecting the Auto-Recharge feature and have implemented a fix. The issue was caused by a software bug. Auto-Recharge functionality has been restored and should now operate as expected. We apologize for the inconvenience and appreciate your patience while we worked to resolve the issue.

Read the full incident report →

Notice August 6, 2026

Phaxio API Outage

Detected by Pingoru: Aug 06, 2026, 02:22 PM UTC
Resolved: Aug 06, 2026, 03:54 PM UTC
Duration: 1h 31m

Timeline · 4 updates

investigating Aug 06, 2026, 02:22 PM UTC

We are currently failing to process all outbound faxes. We are actively investigating the issue.
identified Aug 06, 2026, 02:46 PM UTC

The issue has been identified and a fix is being implemented.
monitoring Aug 06, 2026, 03:04 PM UTC

This incident has been resolved. Our engineering team is actively investigating the underlying cause of this issue and is working toward a permanent resolution. We will continue to provide updates as new information becomes available.
resolved Aug 06, 2026, 03:54 PM UTC

Root cause was identified as an outage of our temporary storage where documents are held for processing. During this time outbound faxes failed with the message “Document conversion error. Contact support.” In some cases, the API rejected new connections due to the congestion. There was no effect on inbound faxes during this time.

Read the full incident report →

Notice August 1, 2025

Phaxio Inbound/Outbound Faxing Event Notification 07/23/25

Detected by Pingoru: Aug 01, 2025, 01:32 PM UTC
Resolved: Aug 01, 2025, 01:32 PM UTC
Duration: —

Affected: Inbound FaxingOutbound Faxing

Timeline · 1 update

resolved Aug 01, 2025, 01:32 PM UTC

We experienced an issue with an AWS event. This resulted in a delay of inbound faxes, and also resulted in non-completed faxes on outbound for approximately 30 minutes. Some outbound faxes were not delivered, and were canceled. These faxes will need to be resent. The occurred between 8:15-8:46 PM ET on July 23, 2025 Please reach out to [email protected] with questions or concerns. Thank you, Phaxio Support

Read the full incident report →

Notice May 6, 2025

Phaxio Service Update Notification // Supported File Types Change // 05/06/25

Detected by Pingoru: May 06, 2025, 06:38 PM UTC
Resolved: May 06, 2025, 06:38 PM UTC
Duration: —

Affected: Inbound FaxingOutbound Faxing

Timeline · 1 update

resolved May 06, 2025, 06:38 PM UTC

Please be advised that support for .doc (application/msword) will stop immediately on Phaxio due to possible security vulnerabilities. The file type .doc is a legacy MIME type to the newer .docx and support is ending for this file extension by Microsoft in October 2025. In addition, we are removing support for .odt (application/vnd.oasis.opendocument.text) immediately due to overall security concerns and known exploits with that file type. You can find the support file types here: https://www.phaxio.com/faq#11 Please do not reply to this email as it is unmonitored. Please reach out to [email protected] with questions or concerns. Thank you, Phaxio Support

Read the full incident report →

Minor April 30, 2025

Phaxio Outbound Fax Conversion Issue // Event Notification

Detected by Pingoru: Apr 30, 2025, 02:29 PM UTC
Resolved: Apr 30, 2025, 08:33 PM UTC
Duration: 6h 3m

Affected: Outbound Faxing

Timeline · 4 updates

identified Apr 30, 2025, 02:29 PM UTC

We have identified an issue with some outbound faxes failing due to document conversion errors. We are actively investigating and will continue to provide updates.
monitoring Apr 30, 2025, 02:52 PM UTC

Services are now restored - we have restarted the applications and are currently monitoring. If you do experience more issues, please advise us at [email protected].
resolved Apr 30, 2025, 08:33 PM UTC

This incident has been resolved.
postmortem Apr 30, 2025, 08:50 PM UTC

**Start:** 12:58 UTC 04/30/25 **Stop:** 14:46 UTC 04/30/25 **Findings:** Document conversion servers experienced an issue resulting in document conversion failures on outbound faxes. **Resolution:** The servers were restarted to resolve the errors. We are analyzing the event to further determine root cause of the document conversion failures. **Customer Experience:** Some sent/outbound faxes would have received the following in the webhook notification for the fax: status: failure error\_type: documentConversion Error The fax will need to be resent. **Future:** Engineering is working on reviewing server logs and alerts to alleviate the issue from occurring in the future

Read the full incident report →

Minor March 12, 2025

Phaxio "Number of Pages" Event Notification

Detected by Pingoru: Mar 12, 2025, 09:01 PM UTC
Resolved: Mar 12, 2025, 10:44 PM UTC
Duration: 1h 43m

Affected: Inbound FaxingOutbound FaxingWeb Console

Timeline · 3 updates

investigating Mar 12, 2025, 09:01 PM UTC

We are observing an issue with the “Number of Pages” that are being posted for both Received and Sent faxes on the webhook and on the console for a fax log. Engineering is currently investigating the issue. Please note, the full fax is being processed, this is only a reporting issue for “Number of Pages” (Example: A 30 page fax will send/receive all 30 pages, but the webhook and console log for that fax will show “Number of Pages: 1”)
identified Mar 12, 2025, 09:28 PM UTC

Engineering has identified the issue and we are working on releasing this to production. Updates to follow.
resolved Mar 12, 2025, 10:44 PM UTC

Engineering has released the fix to production and we are monitoring at this time. Customers will only be billed for single page faxes, even if the fax contained multiple pages. Also, we will not be adjusting the page counts for faxes that were sent or received during this service issue. We apologize for any inconvenience this may have caused to you or your customers.

Read the full incident report →

Minor February 4, 2025

Phaxio Web Console Event Notification - SMS Verification

Detected by Pingoru: Feb 04, 2025, 08:29 PM UTC
Resolved: Feb 04, 2025, 08:45 PM UTC
Duration: 15m

Affected: Web Console

Timeline · 2 updates

investigating Feb 04, 2025, 08:29 PM UTC

We are currently experiencing an issue with our sms verification service. This will affect users being able to log into the dashboard as they will not receive their sms verification code. Inbound and outbound faxes are not affected. Should you have any questions or experience any service issues, please continue to reach us at [email protected].
resolved Feb 04, 2025, 08:45 PM UTC

The sms verification service issue has been identified and resolved at this time. If you are experiencing any further issues logging into the web console please contact support at [email protected]

Read the full incident report →

Notice October 23, 2024

Monitoring notifications email domain update // 10/23/24

Detected by Pingoru: Oct 23, 2024, 07:41 PM UTC
Resolved: Oct 23, 2024, 07:41 PM UTC
Duration: —

Affected: Email Alerts

Timeline · 1 update

resolved Oct 23, 2024, 07:41 PM UTC

Hi! We have updated our proactive monitoring email notifications domain. The new domain will be "notifications.sinch.com". You may see on some mail providers "[email protected]" on behalf of "[email protected]" . If you believe you are missing notifications, please validate you have added this email address to your safe senders list or check your junk/spam folder. Please do not reply to this email as it is unmonitored. Please reach out to [email protected] with questions or concerns.

Read the full incident report →