Precios
Historial de estadoActualizaciones RSSAPI de estado

Desarrollado por Uptimus

    Historial de interrupciones de Revio

    52 incidentes de Revio registrados desde julio de 2020, con actualizaciones oficiales, componentes afectados, duración y detalles de resolución.

    Volver al estado actual

    Rendimiento de facturación degradado

    Comenzó 1 de octubre de 2026 a las 15:40 UTC · 20h 30m

    OutageIncidente mayor
    Componentes afectados
    Recurring Billing
    1. 1 de octubre de 2026 a las 15:40 UTCinvestigating

      Estamos investigando informes de rendimiento degradado que afectan las operaciones de facturación para un subconjunto de clientes. Los clientes afectados pueden experimentar procesos más lentos que normales y tiempos de respuesta más largos al ejecutar funciones de facturación. Nuestro equipo está investigando y trabajando activamente para restaurar el rendimiento normal. Publicaremos una actualización tan pronto como tengamos más información.

    2. 1 de octubre de 2026 a las 17:36 UTCmonitoring

      Hemos tomado medidas correctivas sobre los recursos afectados y el rendimiento está mejorando. Las métricas siguen recuperándose y aumentando. La recuperación completa puede tardar unas horas.

    3. 2 de octubre de 2026 a las 12:10 UTCresolved

      Este incidente está resuelto. Aplicamos cambios correctivos en la infraestructura de facturación, y el rendimiento volvió a la normalidad. Las operaciones de facturación se han mantenido estables a través de un ciclo completo de día de trabajo. Gracias por su paciencia.

    Traducido automáticamente desde la actualización oficial del incidente.

    Ticketing Service Disruption

    Comenzó 10 de agosto de 2026 a las 22:01 UTC · 5m

    OutageIncidente mayor
    Componentes afectados
    PSA Module
    1. 10 de agosto de 2026 a las 23: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. 10 de agosto de 2026 a las 23: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.

    PSA Web — Dispatch Board Degradado

    Comenzó 30 de julio de 2026 a las 16:10 UTC · 3h 40m

    IssuesIncidente menor
    Componentes afectados
    PSA Module
    1. 30 de julio de 2026 a las 16:10 UTCidentified

      Somos conscientes de una cuestión que afecta a la Junta de Despacho dentro de PSA Web. Algunos usuarios pueden encontrar un error al abrir la Junta de Despacho; otras áreas de PSA Web no son afectadas. Nuestro equipo ha identificado la causa y está trabajando activamente en una resolución. Esta cuestión comenzó a las 10:53 AM ET el 30 de julio de 2026 y sigue en curso. Publicaremos una actualización tan pronto como tengamos más información.

    2. 30 de julio de 2026 a las 17:06 UTCmonitoring

      Hemos implementado una solución para la cuestión que afecta a la Junta de Despacho dentro de PSA Web y ahora estamos monitoreando para confirmar la recuperación completa. Los usuarios deben poder abrir la Junta de Despacho normalmente de nuevo. Publicaremos una actualización final una vez que hayamos confirmado que la cuestión está totalmente resuelta.

    3. 30 de julio de 2026 a las 19:50 UTCresolved

      Se ha resuelto la degradación de la Junta de Despacho que afecta al Módulo PSA. Siguiendo el hotfix, monitoreamos el servicio y confirmamos que la Junta de Despacho está operando normalmente sin recurrencia. Toda la funcionalidad está completamente restaurada. Gracias por su paciencia.

    Traducido automáticamente desde la actualización oficial del incidente.

    PSA Web — Módulo de Ticketing Performance degradado

    Comenzó 24 de julio de 2026 a las 13:37 UTC · 3h 41m

    IssuesIncidente menor
    Componentes afectados
    PSA Module
    1. 24 de julio de 2026 a las 13:37 UTCidentified

      Hemos identificado el rendimiento degradado que afecta al módulo de ticketing en PSA Web. Nuestro equipo ha aislado el tema y está trabajando activamente para resolverlo mientras supervisa de cerca. Publicaremos nuevas actualizaciones a medida que se avance.

    2. 24 de julio de 2026 a las 16:54 UTCmonitoring

      A principios de hoy se implementó una solución para el rendimiento degradado que afecta al módulo de ticketing PSA Web. Ticketing se está ejecutando normalmente, y estamos monitoreando de cerca para confirmar que el problema está totalmente resuelto. Publicaremos una actualización final una vez que se confirme la estabilidad.

    3. 24 de julio de 2026 a las 17:17 UTCresolved

      Este incidente ha sido resuelto. La fijación desplegada hoy en día se ha mantenido a través de nuestra ventana de monitoreo y el módulo de ticketing PSA Web está completamente operativo. Gracias por su paciencia.

    Traducido automáticamente desde la actualización oficial del incidente.

    Ticket Creation Incident - June 29th, 2026

    Comenzó 29 de junio de 2026 a las 18:30 UTC · 1h 34m

    IssuesIncidente menor
    Componentes afectados
    PSA Module
    1. 29 de junio de 2026 a las 18: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. 29 de junio de 2026 a las 19:11 UTCmonitoring

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

    3. 29 de junio de 2026 a las 20: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.

    Investigating errors in PSA Web

    Comenzó 9 de junio de 2026 a las 19:25 UTC · 22m

    OutageIncidente mayor
    Componentes afectados
    PSA Module
    1. 9 de junio de 2026 a las 19: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. 9 de junio de 2026 a las 19: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.

    Investigating authentication errors in Rev.io PSA

    Comenzó 5 de junio de 2026 a las 12:53 UTC · 3h 40m

    IssuesIncidente menor
    Componentes afectados
    PSA Module
    1. 5 de junio de 2026 a las 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. 5 de junio de 2026 a las 13: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. 5 de junio de 2026 a las 16: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.

    Azure service issues

    Comenzó 24 de abril de 2026 a las 19:45 UTC · 4h 45m

    OutageIncidente mayor
    Componentes afectados
    REST APIPSA ModuleSOAP APIRev.io WebBillCenter.net WebAgentClick WebDeveloper Documentation (developers.rev.io)
    1. 24 de abril de 2026 a las 20:57 UTCinvestigating

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

    2. 24 de abril de 2026 a las 20:58 UTCidentified

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

    3. 25 de abril de 2026 a las 2:49 UTCidentified

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

    4. 25 de abril de 2026 a las 2:50 UTCresolved

      This incident has been resolved.

    PSA login looping

    Comenzó 21 de abril de 2026 a las 17:49 UTC · 10m

    OutageIncidente mayor
    Componentes afectados
    PSA Module
    1. 21 de abril de 2026 a las 17:49 UTCinvestigating

      We are currently investigating this issue.

    2. 21 de abril de 2026 a las 17:50 UTCidentified

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

    3. 21 de abril de 2026 a las 17:58 UTCresolved

      Authentication issue resolved.

    Global Email Outages

    Comenzó 22 de enero de 2026 a las 20:46 UTC · 17h 4m

    IssuesIncidente menor
    Componentes afectados
    Rev.io WebBillCenter.net WebAgentClick Web
    1. 22 de enero de 2026 a las 20: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. 22 de enero de 2026 a las 22: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. 22 de enero de 2026 a las 22:05 UTCmonitoring

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

    4. 22 de enero de 2026 a las 22:06 UTCidentified

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

    5. 23 de enero de 2026 a las 13:50 UTCresolved

      Microsoft has returned service to a healthy state.

    Paya Intermittent Outage - 12/6/24

    Comenzó 6 de diciembre de 2024 a las 20:45 UTC · 20h 20m

    Pending
    Componentes afectados
    Rev.io Web
    1. 6 de diciembre de 2024 a las 20: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. 7 de diciembre de 2024 a las 17: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.

    Microsoft Outlook/365 Outage

    Comenzó 25 de noviembre de 2024 a las 16:42 UTC · 7h 51m

    Pending
    Componentes afectados
    Rev.io Web
    1. 25 de noviembre de 2024 a las 16: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. 26 de noviembre de 2024 a las 0: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.

    Paya Degraded Performance - October 8th, 2024

    Comenzó 8 de octubre de 2024 a las 18:24 UTC · 1d 0h

    IssuesIncidente menor
    Componentes afectados
    Rev.io Web
    1. 8 de octubre de 2024 a las 18: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. 8 de octubre de 2024 a las 18: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. 8 de octubre de 2024 a las 20: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. 9 de octubre de 2024 a las 18: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.

    Paya Payments Outage - 4/11/24

    Comenzó 11 de abril de 2024 a las 15:59 UTC · 2h 46m

    IssuesIncidente menor
    Componentes afectados
    Rev.io Web
    1. 11 de abril de 2024 a las 15: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. 11 de abril de 2024 a las 16: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. 11 de abril de 2024 a las 16: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. 11 de abril de 2024 a las 18: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.

    Minor FTP Site UI Errors

    Comenzó 9 de abril de 2024 a las 13:33 UTC · 6h 4m

    IssuesIncidente menor
    Componentes afectados
    File TransferRev.io Web
    1. 9 de abril de 2024 a las 13: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. 9 de abril de 2024 a las 16: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. 9 de abril de 2024 a las 19:36 UTCresolved

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

    CSI Taxation Engine Outage

    Comenzó 29 de enero de 2024 a las 13:26 UTC · 4d 4h

    IssuesIncidente menor
    Componentes afectados
    Rev.io Web
    1. 29 de enero de 2024 a las 13: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. 29 de enero de 2024 a las 15: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. 29 de enero de 2024 a las 16: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. 29 de enero de 2024 a las 17: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. 29 de enero de 2024 a las 18: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. 29 de enero de 2024 a las 19: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. 30 de enero de 2024 a las 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. 30 de enero de 2024 a las 13: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. 30 de enero de 2024 a las 20: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. 31 de enero de 2024 a las 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. 31 de enero de 2024 a las 14: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. 31 de enero de 2024 a las 14:11 UTCmonitoring

      We are continuing to monitor for any further issues.

    13. 2 de febrero de 2024 a las 17: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.

    Rev.io Service Issues

    Comenzó 7 de agosto de 2023 a las 15:46 UTC · 3h 1m

    IssuesIncidente menor
    Componentes afectados
    Rev.io Web
    1. 7 de agosto de 2023 a las 15: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. 7 de agosto de 2023 a las 16: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. 7 de agosto de 2023 a las 17: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. 7 de agosto de 2023 a las 18: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.

    Intermittent Performance Slowdowns and 500 Errors

    Comenzó 7 de julio de 2023 a las 17:00 UTC · 3h 9m

    IssuesIncidente menor
    Componentes afectados
    Rev.io Web
    1. 7 de julio de 2023 a las 17: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. 7 de julio de 2023 a las 20:08 UTCresolved

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

    Print Queue Module Currently Inaccessible

    Comenzó 21 de junio de 2023 a las 14:49 UTC · 42m

    OutageIncidente mayor
    Componentes afectados
    Rev.io Web
    1. 21 de junio de 2023 a las 14: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. 21 de junio de 2023 a las 14:50 UTCidentified

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

    3. 21 de junio de 2023 a las 15: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. 21 de junio de 2023 a las 15: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.

    Rev.io Inaccessible For Certain Instances

    Comenzó 11 de mayo de 2023 a las 2:33 UTC · 42m

    OutageIncidente mayor
    Componentes afectados
    REST APIRev.io Web
    1. 11 de mayo de 2023 a las 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. 11 de mayo de 2023 a las 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. 11 de mayo de 2023 a las 3:15 UTCresolved

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