Revio 장애 기록

1. 2026년 10월 1일 오후 3:40 UTCinvestigating

   우리는 고객의 하위 세트에 대한 청구 작업에 영향을 미치는 성능의 조사 보고서입니다. Affected 고객은 청구 기능을 실행할 때 slower-than-normal 처리와 더 긴 응답 시간을 경험할지도 모릅니다. 우리의 팀은 적극적으로 정상적인 성과를 복원하고 일하고 있습니다. 우리는 우리가 더 많은 정보를 가지고 있기 때문에 업데이트합니다.

2. 2026년 10월 1일 오후 5:36 UTCmonitoring

   우리는 영향을받는 자원과 성능에 대한 올바른 조치를 취했습니다. 미터는 복구 및 상승을 계속합니다. 풀 복구 몇 시간 걸릴 수 있습니다.

3. 2026년 10월 2일 오후 12:10 UTCresolved

   이 사건은 해결됩니다. 우리는 청구 인프라에 정확한 변경을 적용하고, 성능은 정상으로 돌아갑니다. 빌링 가동은 가득 차있는 사업 일 주기를 통해서 안정되어 있었습니다. 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 10일 오후 11:06 UTCidentified

   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.

2. 2026년 8월 10일 오후 11:06 UTCresolved

   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.

1. 2026년 7월 30일 오후 4:10 UTCidentified

   우리는 PSA 웹 내의 Dispatch Board에 영향을 미치는 문제의 인식입니다. 일부 사용자는 Dispatch Board를 열 때 오류가 발생할 수 있습니다. PSA Web의 다른 영역은 비공개되지 않습니다. 우리의 팀은 원인을 확인하고 해결에 적극적으로 노력하고 있습니다. 이 문제는 7 월 30, 2026에 오전 10시 53분에서 시작되며 계속 유지됩니다. 우리는 우리가 더 많은 정보를 가지고 있기 때문에 업데이트합니다.

2. 2026년 7월 30일 오후 5:06 UTCmonitoring

   우리는 PSA 웹 내에서 Dispatch Board에 영향을 미치는 문제에 대한 수정을 배포했으며 이제 전체 복구를 확인하기 위해 모니터링합니다. 사용자는 Dispatch Board를 다시 열 수 있어야 합니다. 우리는 일단 우리가 문제점을 완전히 해결한 후에 최종 갱신을 포스트할 것입니다.

3. 2026년 7월 30일 오후 7:50 UTCresolved

   PSA Module에 영향을 미치는 Dispatch Board 분해는 해결되었습니다. the hotfix, 우리는 서비스를 모니터링하고 Dispatch Board를 확인하는 것은 통관없이 정상적으로 작동한다. 모든 기능은 완전히 복원됩니다. 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 24일 오후 1:37 UTCidentified

   PSA 웹에서 매표 모듈에 영향을 미치는 성능 확인했습니다. 우리의 팀은 문제점을 격리하고 그것을 감시하는 동안 적극적으로 일하고 있습니다. 더 많은 업데이트를 진행합니다.

2. 2026년 7월 24일 오후 4:54 UTCmonitoring

   PSA Web Ticketing 모듈에 영향을 미치는 degraded 성능에 대한 수정은 오늘 이전 배포되었습니다. Ticketing은 이제 정상적으로 수행되고, 문제를 해결하기 위해 긴밀히 모니터링하고 있습니다. 일단 안정성이 확인되면 최종 업데이트가 표시됩니다.

3. 2026년 7월 24일 오후 5:17 UTCresolved

   이 사건은 해결되었습니다. 수정은 오늘 이전 출시되었습니다 우리의 모니터링 창을 통해 및 PSA 웹 발권 모듈은 완전히 작동. 감사합니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 29일 오후 6:30 UTCidentified

   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.

2. 2026년 6월 29일 오후 7:11 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2026년 6월 29일 오후 8:04 UTCresolved

   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.

1. 2026년 6월 9일 오후 7:25 UTCinvestigating

   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.

2. 2026년 6월 9일 오후 7:47 UTCresolved

   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.

1. 2026년 6월 5일 오후 12:53 UTCinvestigating

   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.

2. 2026년 6월 5일 오후 1:26 UTCidentified

   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.

3. 2026년 6월 5일 오후 4:33 UTCresolved

   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.

1. 2026년 4월 24일 오후 8:57 UTCinvestigating

   Azure is currently experiencing issues in the East region. We are monitoring service statuses and our affected resources.

2. 2026년 4월 24일 오후 8:58 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2026년 4월 25일 오전 2:49 UTCidentified

   We are continuing to work on a fix for this issue.

4. 2026년 4월 25일 오전 2:50 UTCresolved

   This incident has been resolved.

1. 2026년 4월 21일 오후 5:49 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 4월 21일 오후 5:50 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2026년 4월 21일 오후 5:58 UTCresolved

   Authentication issue resolved.

1. 2026년 1월 22일 오후 8:46 UTCinvestigating

   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.

2. 2026년 1월 22일 오후 10:04 UTCinvestigating

   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.

3. 2026년 1월 22일 오후 10:05 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2026년 1월 22일 오후 10:06 UTCidentified

   The issue has been identified and a fix is being implemented.

5. 2026년 1월 23일 오후 1:50 UTCresolved

   Microsoft has returned service to a healthy state.

1. 2024년 12월 6일 오후 8:45 UTCidentified

   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

2. 2024년 12월 7일 오후 5:05 UTCresolved

   This incident was resolved by Paya yesterday evening. If you have any further questions or concerns, please reach out to the Client Success team.

1. 2024년 11월 25일 오후 4:42 UTCidentified

   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/

2. 2024년 11월 26일 오전 12:33 UTCresolved

   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.

1. 2024년 10월 8일 오후 6:24 UTCinvestigating

   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.

2. 2024년 10월 8일 오후 6:48 UTCmonitoring

   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.

3. 2024년 10월 8일 오후 8:00 UTCmonitoring

   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.

4. 2024년 10월 9일 오후 6:53 UTCresolved

   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.

1. 2024년 4월 11일 오후 3:59 UTCidentified

   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

2. 2024년 4월 11일 오후 4:04 UTCidentified

   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.

3. 2024년 4월 11일 오후 4:31 UTCmonitoring

   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.

4. 2024년 4월 11일 오후 6:45 UTCresolved

   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.

1. 2024년 4월 9일 오후 1:33 UTCidentified

   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.

2. 2024년 4월 9일 오후 4:53 UTCmonitoring

   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.

3. 2024년 4월 9일 오후 7:36 UTCresolved

   This incident has been resolved. Thanks for your attention and reach out to Client Success with any lingering questions.

1. 2024년 1월 29일 오후 1:26 UTCinvestigating

   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.

2. 2024년 1월 29일 오후 3:00 UTCinvestigating

   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.

3. 2024년 1월 29일 오후 4:16 UTCidentified

   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/

4. 2024년 1월 29일 오후 5:41 UTCidentified

   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.

5. 2024년 1월 29일 오후 6:27 UTCidentified

   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

6. 2024년 1월 29일 오후 7:52 UTCidentified

   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.

7. 2024년 1월 30일 오전 1:49 UTCidentified

   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.

8. 2024년 1월 30일 오후 1:24 UTCidentified

   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."

9. 2024년 1월 30일 오후 8:55 UTCidentified

   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.

10. 2024년 1월 31일 오전 2:44 UTCmonitoring

    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.

11. 2024년 1월 31일 오후 2:11 UTCmonitoring

    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.

12. 2024년 1월 31일 오후 2:11 UTCmonitoring

    We are continuing to monitor for any further issues.

13. 2024년 2월 2일 오후 5:49 UTCresolved

    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.

1. 2023년 8월 7일 오후 3:46 UTCinvestigating

   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.

2. 2023년 8월 7일 오후 4:22 UTCinvestigating

   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.

3. 2023년 8월 7일 오후 5:21 UTCidentified

   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.

4. 2023년 8월 7일 오후 6:46 UTCresolved

   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.

1. 2023년 7월 7일 오후 5:00 UTCmonitoring

   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.

2. 2023년 7월 7일 오후 8:08 UTCresolved

   After continued monitoring with no further issues, we are marking this morning's incident as resolved.

1. 2023년 6월 21일 오후 2:49 UTCinvestigating

   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.

2. 2023년 6월 21일 오후 2:50 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2023년 6월 21일 오후 3:23 UTCmonitoring

   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.

4. 2023년 6월 21일 오후 3:31 UTCresolved

   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.

1. 2023년 5월 11일 오전 2:33 UTCinvestigating

   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.

2. 2023년 5월 11일 오전 2:52 UTCmonitoring

   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

3. 2023년 5월 11일 오전 3:15 UTCresolved

   This incident should now be resolved. All client instances should be up and running as expected.