52 Revio incidents · 2020年7月 — official updates, affected components, duration and resolution details.
我们正在调查有关业绩退化的报告,这些报道影响到对一部分客户的收费业务。 受影响的客户在运行计费功能时可能会遇到比正常的处理速度更慢和反应时间更长的情况. 我们的团队正在积极调查并努力恢复正常的表现. 一旦掌握更多信息,我们将公布最新情况.
我们已经对受影响的资源采取了纠正行动,业绩正在改善。 计量持续恢复并上升. 完全康复可能需要几个小时.
此事已决. 我们修改了收费基础设施,业绩恢复正常。 计费业务在整个营业日周期内保持稳定。 谢谢你的耐心.
自动翻译自官方事件更新。
We are investigating a disruption affecting ticketing within the PSA platform. The issue originates in the billing platform service. Ticketing may be intermittently unavailable while we work to resolve it.
We experienced a brief disruption affecting ticketing within the PSA platform. The issue originated in the billing platform service and was resolved within a few minutes after the service was cycled. Ticketing is now fully operational. We are conducting a review to identify and address the root cause and to prevent recurrence.
我们知道PSA网络内有一个影响调度局的问题。 有些用户在打开调度板时可能会出错;PSA Web的其他领域没有受到影响. 我们的小组已经查明了原因,并正在积极拟订一项决议。 这个问题从2026年7月30日10:53AM ET开始,至今仍在进行. 一旦掌握更多信息,我们将公布最新情况.
我们已经在PSA Web内对影响调度委员会的问题作了处理,目前正在进行监测,以确认全面恢复。 用户应能够正常地再次打开调度委员会。 一旦我们确认问题已完全解决,我们将公布最后最新情况.
影响PSA模块的调度委员会退化问题已经得到解决。 之后,我们监测了服务,确认调度局正常运转,没有再次发生。 所有功能全部恢复. 谢谢你的耐心.
自动翻译自官方事件更新。
我们发现PSA Web的售票模块已退化。 我们的小组孤立了这一问题,并正在积极努力解决这一问题,同时密切监测。 随着进展,我们将公布进一步的最新情况.
今天早些时候,对影响PSA网络售票模块的退化性能进行了补救。 车票现在运行正常,我们正在密切监测,以确认这一问题已经完全解决。 一旦稳定得到确认,我们将公布最后最新情况.
这一事件已经得到解决。 今天早些时候部署的固定装置已经通过我们的监测窗口进行,PSA网络售票模块已全面投入使用。 谢谢你的耐心.
自动翻译自官方事件更新。
We have identified an issue affecting creation of ticketing for the PSA Web platform, and our team is working to restore functionality. Please refer to this page for further updates as our fix gets tested and deployed.
A fix has been implemented and we are monitoring the results.
This incident has been resolved. A full Root Cause Analysis will be available from our team, reach out to Client Success for any further questions or issues.
We are currently investigating reports of errors affecting PSA Web. Our team is actively looking into the issue and we will provide an update as soon as we have more information. We apologize for any inconvenience.
This incident has been resolved. The errors in PSA Web were caused by a component release that introduced a missing dependency. A rollback of that release has fully restored service, and PSA Web is now operating normally. A detailed root cause analysis (RCA) will follow. We apologize for any inconvenience.
We are currently investigating a subset of authentication errors affecting Rev.io PSA. Some users may experience intermittent errors when signing in. We are actively investigating and will provide updates as more information becomes available.
We have identified the cause of the authentication errors as an issue with an authentication token rotation process, impacting a small subset of users signing in to Rev.io PSA. Our team is implementing a fix and we will share another update shortly.
This incident has been resolved. The authentication errors were caused by an expired credential, which has been renewed. We have validated that sign-in to Rev.io PSA is functioning normally. We apologize for the disruption.
Azure is currently experiencing issues in the East region. We are monitoring service statuses and our affected resources.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
Authentication issue resolved.
There are global email outages affecting Google Gmail, Microsoft O365 Outlook, Twilio and others. Revio's support is built on Google, and responses/email updates are not being sent. This also is preventing MFA codes for client logins. Our team is monitoring the situation and hope it will be resolved soon.
The outage has been identified as affecting Microsoft 365 services. End users using Microsoft 365 to receive 2FA codes would not have received them. Rev.io's support has also been affected. We are continuing to monitor Microsoft's status for updates.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
Microsoft has returned service to a healthy state.
Paya has alerted us of an intermittent outage from their end that started at approximately 2:15pm ET this afternoon. They are working to resolve the issue, but have not provided an ETA yet. Clients and end-customers may experience errors with payments unable to process during this time. Please refer to the Paya Maintenance & Service page below for further updates. Official Paya Alerts: https://support.paya.com/44510-knowledgebase/308786
This incident was resolved by Paya yesterday evening. If you have any further questions or concerns, please reach out to the Client Success team.
There is a large-scale Microsoft Outlook/365 outage that may affect users with Outlook email inboxes. Microsoft has not provided any ETA for this being resolved, but we have had reports of intermittent email failures from clients using Outlook inboxes for their Rev.io communication. We are tracking the incident with the DownDetector status page below: https://downdetector.com/status/outlook/
Microsoft has resolved their outage and we expect all Outlook connections to resume normal activity. Please reach out to Client Success with any questions or concerns.
We are currently investigating reports of payments errors when attempting to make payments using Paya. We have reached out to their team for guidance, and have involved our Engineering team as well. As soon as more info is available, we will update this incident page. Please reach out to Client Success with any concerns or questions, and thanks for your attention to this matter.
A fix has been implemented by Paya and we are monitoring the results. Please reach out to Client Success with any questions. We will provide final guidance here once it's available.
We are continuing to wait for the final 'all-clear' from Paya. They have made progress but have still encountered intermittent slowness/errors. As soon as we have a root cause and final update we will update this thread.
This incident has been resolved. For any issues with payments made yesterday during the intermittent outage, please reach out to our Client Success team for assistance.
We are receiving reports of payments failures for clients using Paya as their payment processor. Paya has confirmed an outage on their side as the culprit, and are working quickly to restore access and payments flowing. We will keep this thread updated as we receive information. Please refer to Client Success with any questions in the meantime, and thank you for your continued support and patience. - The Rev.io Team
We are continuing to request info from Paya about their outage and time to resolve. More info will be sent here as soon as we can.
Paya has implemented a fix and we are monitoring the results. Please retry any missed payments and reach out to our Client Success team with any questions or continued issues.
Payments have been flowing successfully since Paya's fix was implemented. At this time, the incident is marked as resolved. For any lingering questions or issues, please reach out to Client Success.
We have identified an issue related to viewing and editing FTP sites within the Rev.io billing platform. All files are still flowing in, processing, and rating correctly. However, viewing and editing the FTP site produces an error. The team has already found the affected code and will be fixing this via a hotfix today. We will follow up with more information as soon as it's available. Please reach out to Client Success with any questions or concerns.
This issue has been resolved and full functionality of FTP sites should be restored. We will continue to monitor the situation and if you are still experiencing issues, please reach out to the Client Success team for us to assist further.
This incident has been resolved. Thanks for your attention and reach out to Client Success with any lingering questions.
We are currently receiving reports that clients who use CSI as their tax engine are not producing taxes on products or bills currently. CSI appears to be having an outage upstream from our platform. We have reached out to the CSI team for guidance and assistance. At this time, clients using CSI will be unable to run bills or create taxes until CSI has resolved the issue. We'll monitor closely and hope the CSI team is able to fix it quickly. Reach out to Client Success with any questions.
We are continuing to wait for guidance from the CSI and an estimated time for resolution. As soon as more information is received, we will update this thread.
CSI has identified the issue and is working to resolve it. We hope to have service restored by their team in the next 2 hours. As soon as we hear more information we will pass it along. CSI has created a status page as well, located here: https://compliancesolutionsinc.statuspage.io/
CSI's team is continuing to work on the issues from their side, and will provide another update this afternoon. Thank you for your patience as we wait for CSI to resolve their outage.
At this time we are still waiting on CSI to resolve their outage. We have not gotten a firm timeline from their team, and are hoping for resolution. Orders, charges, and bills will still be affected for any client using CSI until the outage is resolved. Please refer to CSI's status page as well as ours for any updates as they become available. https://compliancesolutionsinc.statuspage.io/incidents/xbwrsmypkfnt
We have spoken with CSI, and they are hopeful to have the outage resolved this evening. Our hope is for taxes to be flowing by the end of business today, but if not it should resume tomorrow morning. CSI is doing everything they can to restore service soon and are thankful for the patience from our clients. As soon as more info is available, it will be updated and distributed here.
We received the following update from CSI: Update - We are in QC process and are continuing to make progress on providing tax rating capabilities through our APIs. Currently, it appears we will have functionality restored later tonight. Will provide another update as we get closer. Thank you for your patience.
At this time, CSI is still down. They have provided the following update, pasted below. "Update - Still working to bring up the tax calc APIs at a minimum level for tax rating. Have faced several complications in this regard."
We are still waiting for CSI to resolve the outage, please refer to their status page for the most up to date information. For any clients who use CSI and also bill on the 1st of the month, we are offering to disable billing automation until the CSI outage is resolved. Reach out to Client Success with any questions or needs and thanks for your continued patience.
A fix has been implemented by CSI and they have provided the following guidance: Incident status: Monitoring Our Tax Rating APIs are now online using the same endpoints you currently have. We had to change the IP addresses of the systems, so it may take some time for the DNS to propagate throughout the world. If you would like the new IP address of the endpoint, please contact me at [email protected]. Thank you for your patience.
We are monitoring the results of the fix from CSI, and at this time taxes are flowing again. We highly recommend all clients who use CSI to run test transactions and validate taxes are correct via your team and/or tax compliance partner.
We are continuing to monitor for any further issues.
We have seen stable connections with CSI since their outage was resolved. As of this time we don't have any insight into the reason for the outage that the CSI tax engine experienced from 1/27-1/30. For this reason we ask that any questions be directed to CSI until a root cause is provided. Once a root cause is provided to rev.io we may ask that you take precautionary actions if the root cause warrants such a response.
We are currently investigating reports from a small number of clients, regarding automation issues from the weekend and this morning. Our team is working to resolve this as soon as possible. Please reach out to the Client Success team with any questions or concerns. Thank you for your support and partnership, this page will be updated as information becomes available.
We are continuing to investigate reports of billing queues and POP3 service issues from a segment of clients. Our team is working diligently to resolve it and hope to have more information available soon.
The issue has been identified and services are coming up slowly. We're continuing to monitor closely for lingering issues. Please reach out to Client Success with any questions or concerns.
This incident has been resolved, and our team will continue digging into the root cause. Reach out to Client Success with any questions and thank you for your patience.
We are aware of intermittent 500 errors and performance slowdowns occurring in Rev.io. We have mitigated the issue and are closely monitoring system performance as we working toward full resolution.
After continued monitoring with no further issues, we are marking this morning's incident as resolved.
We have identified an issue with users being unable to access the Print Queue in Rev.io and are currently working on a resolution. We will provide another update once the resolution is in place.
The issue has been identified and a fix is being implemented.
A fix is currently being deployed and users should begin seeing restored access to the Print Queue module shortly. We will continue to monitor until we are confident the issue has been resolved.
Access to the Print Queue module has been fully restored. Please reach out to the Rev.io Support team if you continue to see any issues.
We are aware of an issue with select client instances and the API being inaccessible and are investigating at this time. We will provide any additional updates into the situation as they become available.
All Rev.io instances are back online, but we are continuing to run tests and monitor to ensure the issue is fully resolved. Please await for further updates before this incident is deemed to be resolved
This incident should now be resolved. All client instances should be up and running as expected.
