Historial de interrupciones de Maxio

1. 18 de septiembre de 2026 a las 23:02 UTCinvestigating

   Estamos investigando un problema que hace que algunas exportaciones avanzadas de facturación CSV permanezcan en un estado de procesamiento más largo de lo esperado. Proporcionaremos otra actualización a medida que se disponga de más información.

2. 18 de septiembre de 2026 a las 23:18 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 18 de septiembre de 2026 a las 23:32 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 18 de septiembre de 2026 a las 23:53 UTCresolved

   Se ha resuelto la cuestión que afecta a algunas exportaciones de facturación avanzada de los VCS, y las nuevas exportaciones se están completando normalmente. Las exportaciones que se quedaron atascadas antes de la fijación pueden no completarse y tendrán que ser removidas y repetidas. Sinceramente nos disculpamos por la perturbación y apreciamos su paciencia mientras trabajamos para resolver este problema.

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

1. 1 de septiembre de 2026 a las 15:40 UTCinvestigating

   Estamos investigando un problema que afecta el acceso a Maxio CPQ. Los usuarios están experimentando errores al intentar acceder a la aplicación. Nuestro equipo está investigando y trabajando activamente para restaurar el servicio normal. Proporcionaremos actualizaciones adicionales a medida que se disponga de más información.

2. 1 de septiembre de 2026 a las 15:57 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

3. 1 de septiembre de 2026 a las 16:11 UTCresolved

   Este incidente ha sido resuelto. Gracias por su paciencia mientras trabajamos para restaurar el servicio, y sinceramente nos disculpamos por la perturbación.

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

1. 24 de julio de 2026 a las 11:21 UTCmonitoring

   Somos conscientes de los problemas que afectan el acceso a Maxio Advanced Billing debido a un problema de servicio de terceros. Estamos monitoreando activamente la situación y proporcionaremos actualizaciones a medida que se disponga de más información.

2. 24 de julio de 2026 a las 11:32 UTCresolved

   Este incidente ha sido resuelto.

3. 24 de julio de 2026 a las 11:56 UTCpostmortem

   El **24 de julio de 2026**, entre 10:58 UTC y 11:10 UTC, Maxio Advanced Billing experimentó una breve interrupción del servicio causada por un problema con un proveedor de servicios externos. Durante el incidente, las solicitudes de API a Maxio Advanced Billing pueden haber fallado o devuelto errores. Si sus integraciones se encontraron con solicitudes de API fallidas durante la interrupción, recomendamos reiniciar cualquier solicitud que no haya completado con éxito. Nos disculpamos por la molestia y apreciamos su paciencia mientras el tema fue investigado y resuelto.

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

1. 10 de julio de 2026 a las 15:07 UTCinvestigating

   We are currently investigating this issue.

2. 10 de julio de 2026 a las 15:08 UTCmonitoring

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

3. 10 de julio de 2026 a las 15:11 UTCresolved

   This incident has been resolved.

1. 7 de julio de 2026 a las 11:55 UTCresolved

   Maxio Core encountered issues with UI Elements not displaying correctly within the application. Our engineering team quickly identified and resolved the issue.

1. 19 de junio de 2026 a las 17:59 UTCinvestigating

   We are currently investigating reports of e-invoice emails not being sent.

2. 19 de junio de 2026 a las 18:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 19 de junio de 2026 a las 19:17 UTCmonitoring

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

4. 19 de junio de 2026 a las 21:36 UTCresolved

   This incident has been resolved. As part of our remediation efforts, we identified invoices impacted by the issue and are actively resending any affected e-Bills that had not already been resent manually after the fix was released. No further customer action is required at this time. We apologize for the disruption this caused and appreciate your patience while our team investigated and resolved the issue.

1. 15 de junio de 2026 a las 19:30 UTCinvestigating

   We are currently investigating an issue affecting the Maxio HubSpot integration. Some merchants may be unable to create subscriptions from HubSpot deals. Our team has identified a likely source of the issue and is actively working on mitigation. We will provide another update once we have more information.

2. 15 de junio de 2026 a las 19:50 UTCidentified

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

3. 15 de junio de 2026 a las 20:21 UTCmonitoring

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

4. 15 de junio de 2026 a las 20:25 UTCresolved

   This incident has been resolved.

1. 10 de junio de 2026 a las 18:58 UTCidentified

   A recent API behavior change is causing some merchant requests with unexpected or unsupported fields to fail with validation errors (422 responses). This is impacting multiple workflows and merchants, including the HubSpot integration. We have identified the underlying issue and are actively working to restore expected behavior as quickly as possible.

2. 10 de junio de 2026 a las 19:27 UTCidentified

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

3. 10 de junio de 2026 a las 19:58 UTCmonitoring

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

4. 10 de junio de 2026 a las 20:47 UTCresolved

   This incident has been resolved. Our team has implemented a fix and confirmed that impacted requests are processing normally again, including affected integration workflows. We sincerely apologize for the disruption and appreciate your patience while we worked to restore service.

1. 22 de mayo de 2026 a las 13:18 UTCresolved

   Maxio encountered issues with icons not displaying within the application. Our engineering team quickly identified and resolved the issue.

1. 8 de mayo de 2026 a las 13:44 UTCinvestigating

   We are currently investigating elevated 503 errors. Some customers may experience intermittent errors or degraded availability. Our engineering team is actively working to identify the root cause and mitigate the impact. We will provide another update as soon as we have more information.

2. 8 de mayo de 2026 a las 14:15 UTCresolved

   The incident causing unexpected 503 errors during today’s platform release has been resolved. Some customers may continue to briefly experience cached errors for the next few minutes as systems fully recover.

1. 20 de abril de 2026 a las 16:24 UTCinvestigating

   We are currently investigating an issue where some Advanced Billing invoices are returning 500 errors when accessed via the application UI. Our team is actively working to identify the root cause. We will provide updates as more information becomes available.

2. 20 de abril de 2026 a las 16:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 20 de abril de 2026 a las 16:58 UTCidentified

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

4. 20 de abril de 2026 a las 17:29 UTCmonitoring

   A fix has been implemented and we are currently monitoring the results. Our investigation determined that the 502 errors were caused by timeouts and occurred for users when viewing consolidated invoices directly in the application UI or when accessing invoice PDFs via the API. While initial reports suggested broader API impact, we have since confirmed that standard invoice API endpoints and public invoice URLs were not affected, with the exception of PDF retrieval. No underlying invoice data was impacted.

5. 20 de abril de 2026 a las 17:34 UTCresolved

   This incident has been resolved.

1. 13 de abril de 2026 a las 17:29 UTCidentified

   We are currently investigating and fixing an issue impacting E-Billing where customers may encounter errors when attempting to access e-billing related pages. Thank you for your patience while we work to resolve this.

2. 13 de abril de 2026 a las 17:54 UTCmonitoring

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

3. 13 de abril de 2026 a las 18:07 UTCmonitoring

   We have implemented a partial fix for an issue impacting E-Billing where customers may encounter errors when attempting to access e-billing related pages. We are continuing to investigate and work on additional changes to fully resolve the issue.

4. 13 de abril de 2026 a las 20:39 UTCmonitoring

   We have implemented changes to address an issue impacting E-Billing where customers may encounter errors when attempting to access e-billing related pages. We are monitoring progress as updates continue to take effect. Thank you for your patience.

5. 14 de abril de 2026 a las 7:02 UTCresolved

   This incident has been resolved.

1. 1 de abril de 2026 a las 15:25 UTCinvestigating

   We are currently investigating degraded performance impacting some areas of our system, which may affect processing times and related functionality. Our team is actively working to restore normal performance as quickly as possible. We will continue to share updates as we have more information. Thank you for your patience.

2. 1 de abril de 2026 a las 15:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 1 de abril de 2026 a las 16:06 UTCidentified

   We have identified the issue causing degraded system performance. Our team is actively working on implementing a solution, and you may start seeing improvements as we continue to restore normal performance. We will continue to share updates as progress is made. Thank you for your patience.

4. 1 de abril de 2026 a las 16:51 UTCmonitoring

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

5. 1 de abril de 2026 a las 20:58 UTCmonitoring

   The root cause of the issue has been fully identified and resolved, and system performance has returned to normal. We have been monitoring closely and are confident the platform is operating as expected. No action is required at this time. Thank you for your patience.

6. 1 de abril de 2026 a las 20:58 UTCresolved

   This incident has been resolved.

1. 11 de febrero de 2026 a las 18:00 UTCidentified

   Earlier today, we released an update to our Stripe integration within Advanced Billing to support enhanced validation requirements for Commercial Enhanced Data Program (CEDP) data. This update introduced an unintended regression that caused some payments to fail due to stricter validation of certain line-item values. This behavior is limited to Stripe processing within Advanced Billing. We are in the process reverting the release to restore normal processing and will provide an update once the rollback is complete.

2. 11 de febrero de 2026 a las 18:17 UTCmonitoring

   We have rolled back the earlier release that caused Stripe payment failures within Advanced Billing. Payment processing has been restored and we are actively monitoring. Any payments that failed due to this issue can now be safely retried, either manually or through automatic dunning where enabled. We sincerely apologize for the disruption and appreciate your patience.

3. 11 de febrero de 2026 a las 18:20 UTCresolved

   This incident has been resolved.

1. 4 de febrero de 2026 a las 0:58 UTCinvestigating

   We are currently investigating reports of Integration syncs and exports not running in the Maxio Platform.

2. 4 de febrero de 2026 a las 1:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 de febrero de 2026 a las 1:28 UTCidentified

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

4. 4 de febrero de 2026 a las 1:33 UTCresolved

   We have deployed a fix and this incident is now resolved. Background jobs for integration syncs and exports/imports are running normally again. We will also be implementing additional safeguards to help prevent this issue from recurring.

1. 27 de enero de 2026 a las 16:50 UTCresolved

   Resolved — Advanced Billing experienced a very brief period of degraded performance lasting approximately 1 minute and 10 seconds between 01:32 UTC and 01:33 UTC on 1/27/2026. During this time, some requests may have returned 500-level responses. Normal processing continued, and the service quickly returned to full operational status.

1. 21 de enero de 2026 a las 20:08 UTCinvestigating

   We’re currently investigating an issue where the horizontal scroll bar is missing on the Create Transactions screen (including when creating contracts with transactions), which prevents users from scrolling to view and enter values in all required columns.

2. 21 de enero de 2026 a las 20:13 UTCidentified

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

3. 21 de enero de 2026 a las 21:03 UTCmonitoring

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

4. 21 de enero de 2026 a las 21:11 UTCresolved

   This incident has been resolved.

1. 17 de enero de 2026 a las 9:29 UTCresolved

   Between 2026-01-17 06:40:01 UTC and 2026-01-17 08:51:29 UTC Advanced Billing merchants using exchange rates experienced intermittent HTTP 500 errors on the Product Catalog and Subscription API endpoints due to a third-party service disruption with Open Exchange Rates. No data loss occurred (request/response errors only). This was mitigated on our end as of 2026-01-17 08:51:29 UTC, and service is operating normally.

1. 8 de enero de 2026 a las 15:32 UTCinvestigating

   We are currently investigating an issue preventing some customers from adding ACH info via Plaid to pay e-Bills and update their e-Bill Billing Profile.

2. 8 de enero de 2026 a las 15:39 UTCidentified

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

3. 8 de enero de 2026 a las 15:41 UTCmonitoring

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

4. 8 de enero de 2026 a las 15:43 UTCresolved

   This incident has been resolved.

1. 3 de diciembre de 2025 a las 21:27 UTCidentified

   We are currently experiencing unexpected errors related to today’s release that may prevent some users from logging in or navigating the system. Our development team is actively investigating the cause and working to restore full functionality as quickly as possible. We will continue to share updates as we make progress. Thank you for your patience.

2. 3 de diciembre de 2025 a las 21:55 UTCmonitoring

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

3. 3 de diciembre de 2025 a las 21:55 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3 de diciembre de 2025 a las 22:30 UTCresolved

   This incident has been resolved.