Historial de interrupciones de Maxio

1. September 1, 2026 at 3:40 PM 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. September 1, 2026 at 3:57 PM UTCmonitoring

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

3. September 1, 2026 at 4:11 PM 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. July 24, 2026 at 11:21 AM 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. July 24, 2026 at 11:32 AM UTCresolved

   Este incidente ha sido resuelto.

3. July 24, 2026 at 11:56 AM 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. July 10, 2026 at 3:07 PM UTCinvestigating

   We are currently investigating this issue.

2. July 10, 2026 at 3:08 PM UTCmonitoring

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

3. July 10, 2026 at 3:11 PM UTCresolved

   This incident has been resolved.

1. July 7, 2026 at 11:55 AM UTCresolved

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

1. June 19, 2026 at 5:59 PM UTCinvestigating

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

2. June 19, 2026 at 6:42 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 19, 2026 at 7:17 PM UTCmonitoring

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

4. June 19, 2026 at 9:36 PM 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. June 15, 2026 at 7:30 PM 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. June 15, 2026 at 7:50 PM UTCidentified

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

3. June 15, 2026 at 8:21 PM UTCmonitoring

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

4. June 15, 2026 at 8:25 PM UTCresolved

   This incident has been resolved.

1. June 10, 2026 at 6:58 PM 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. June 10, 2026 at 7:27 PM UTCidentified

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

3. June 10, 2026 at 7:58 PM UTCmonitoring

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

4. June 10, 2026 at 8:47 PM 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. May 22, 2026 at 1:18 PM UTCresolved

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

1. May 8, 2026 at 1:44 PM 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. May 8, 2026 at 2:15 PM 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. April 20, 2026 at 4:24 PM 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. April 20, 2026 at 4:53 PM UTCinvestigating

   We are continuing to investigate this issue.

3. April 20, 2026 at 4:58 PM UTCidentified

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

4. April 20, 2026 at 5:29 PM 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. April 20, 2026 at 5:34 PM UTCresolved

   This incident has been resolved.

1. April 13, 2026 at 5:29 PM 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. April 13, 2026 at 5:54 PM UTCmonitoring

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

3. April 13, 2026 at 6:07 PM 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. April 13, 2026 at 8:39 PM 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. April 14, 2026 at 7:02 AM UTCresolved

   This incident has been resolved.

1. April 1, 2026 at 3:25 PM 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. April 1, 2026 at 3:25 PM UTCinvestigating

   We are continuing to investigate this issue.

3. April 1, 2026 at 4:06 PM 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. April 1, 2026 at 4:51 PM UTCmonitoring

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

5. April 1, 2026 at 8:58 PM 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. April 1, 2026 at 8:58 PM UTCresolved

   This incident has been resolved.

1. February 11, 2026 at 6:00 PM 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. February 11, 2026 at 6:17 PM 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. February 11, 2026 at 6:20 PM UTCresolved

   This incident has been resolved.

1. February 4, 2026 at 12:58 AM UTCinvestigating

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

2. February 4, 2026 at 1:25 AM UTCinvestigating

   We are continuing to investigate this issue.

3. February 4, 2026 at 1:28 AM UTCidentified

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

4. February 4, 2026 at 1:33 AM 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. January 27, 2026 at 4:50 PM 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. January 21, 2026 at 8:08 PM 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. January 21, 2026 at 8:13 PM UTCidentified

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

3. January 21, 2026 at 9:03 PM UTCmonitoring

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

4. January 21, 2026 at 9:11 PM UTCresolved

   This incident has been resolved.

1. January 17, 2026 at 9:29 AM 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. January 8, 2026 at 3:32 PM 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. January 8, 2026 at 3:39 PM UTCidentified

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

3. January 8, 2026 at 3:41 PM UTCmonitoring

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

4. January 8, 2026 at 3:43 PM UTCresolved

   This incident has been resolved.

1. December 3, 2025 at 9:27 PM 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. December 3, 2025 at 9:55 PM UTCmonitoring

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

3. December 3, 2025 at 9:55 PM UTCmonitoring

   We are continuing to monitor for any further issues.

4. December 3, 2025 at 10:30 PM UTCresolved

   This incident has been resolved.

1. November 24, 2025 at 10:11 PM UTCresolved

   Summary An update released earlier today introduced an unintended regression that caused human verification checks (via reCAPTCHA) to fail in Chargify.js. This prevented successful payment profile tokenizations with Chargify.js, and also prevented some customers from completing signups on Public Signup Pages and from updating payment information in the Billing Portal. Affected customers encountered an error stating that verification could not be completed. Impact From 11:43 AM CDT to 1:36 PM CDT, reCAPTCHA verification failed on pages utilizing Chargify.js, including in cases where the feature was not enabled. This blocked form submissions for impacted customers during that period. Resolution The issue was identified and the update responsible was promptly reverted, restoring normal functionality. Next Steps We are enhancing our release and validation processes to prevent similar issues in the future. We sincerely apologize for the disruption and appreciate your patience as we worked to address this matter.