目前无法使用自动充电
Pending
- investigating
我们正在调查一个影响自动充电功能的问题。 我们的团队正在努力尽快恢复功能. 在此期间,您可以根据需要手动在您的账户中添加资金. 一旦恢复自动充电,我们将提供最新情况.
- resolved
我们确定了影响自动充电功能的问题,并实施了固定措施。 这个问题是由软件错误引起的. 自动再充电功能已经恢复,现在应当按预期运行. 我们为不便而道歉,并感谢你在我们努力解决问题时的耐心.
自动翻译自官方事件更新。
14 Phaxio incidents · 2023年4月 — official updates, affected components, duration and resolution details.
我们正在调查一个影响自动充电功能的问题。 我们的团队正在努力尽快恢复功能. 在此期间,您可以根据需要手动在您的账户中添加资金. 一旦恢复自动充电,我们将提供最新情况.
我们确定了影响自动充电功能的问题,并实施了固定措施。 这个问题是由软件错误引起的. 自动再充电功能已经恢复,现在应当按预期运行. 我们为不便而道歉,并感谢你在我们努力解决问题时的耐心.
自动翻译自官方事件更新。
We are currently failing to process all outbound faxes. We are actively investigating the issue.
The issue has been identified and a fix is being implemented.
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.
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.
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
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
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.
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].
This incident has been resolved.
**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
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”)
Engineering has identified the issue and we are working on releasing this to production. Updates to follow.
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.
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].
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]
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.
We have identified an issue with delayed delivery of Outbound faxes for customer using the v1 API only. We are working on clearing the backlog for these faxes and will update as soon as that is completed. If you have any questions please contact our support team at [email protected]
The issue has been identified and a fix is being implemented.
We have cleared the queue and delivery of faxes for v1 API users is back to normal.
We have identified an issue with fax completion issues to Germany (+49800) and Italy (+39800) Toll Free numbers. We are working on correcting the issue and will update as soon as we have one. If you have any questions please contact our support team at [email protected]
We have worked with the vendor and the issue is now corrected. Should you have any questions or experience any service issues, please continue to reach us at [email protected]
We are currently investigating and event causing Inbound/Outbound faxes to fail.. We will update you as soon as we have more information Should you have any questions or experience any service issues, please continue to reach us at [email protected].
We have isolated the issue to API/Outbound faxes and Engineering is working on implementing a fix at this time. We will update you as soon as we have more information Should you have any questions or experience any service issues, please continue to reach us at [email protected].
Engineering has deployed a fix and we are observing faxes (both Inbound and Outbound) and API calls processing successfully. We are continuing to monitor and test to further validate the resolution. Should you have any questions or experience any service issues, please continue to reach us at [email protected].
This incident has been resolved.
On Friday September 15 at 17:36 pm UTC our team noticed a significant drop in successful faxes being sent and received through Phaxio. We immediately began troubleshooting the issue and updated our Status Page \([status.phaxio.com](http://status.phaxio.com)\). Investigation into the degraded service found issues with our document conversion servers and a hot fix was released to our production network. At 20:05 pm UTC all servers confirmed the hot fix in place and all faxes began to process normally. If you have any questions please reach out and let us know at [[email protected]](mailto:[email protected])
We have updated our Porting notifications FROM email address. The new address is "[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 reach out to [email protected] with questions or concerns.
Phaxio by Sinch is excited to announce several enhancements to the 'Port A Number' page in the Phaxio Console. Numbers to Port You can now add multiple numbers to a port request. The primary number on the order is what will appear visible on the Port Requests page. Notes This is a new field that has been created. You can add things like a Port Out PIN or anything you think we may need to know for the request. This field is limited to 50 characters. This has replaced the Contact number field. Authorized Signer's Name We have relabeled the Account Name field to Authorized Signer to facilitate a faster porting process. Port Request Page You will see "All Numbers To Port" field. This field will list all the numbers included in that port request. NOTE: Please remember that all Toll-Free number requests require a current Billing Statement and a signed LOA dated within 30 days. Please send these documents to [email protected] Please reach out to [email protected] with questions or concerns.
We have updated our Statuspage notifications FROM email address. The new address is "[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 reach out to [email protected] with questions or concerns.