Störungsverlauf von Maxio

1. 1. September 2026 um 15:40 UTCinvestigating

   Wir untersuchen ein Problem, das den Zugang zu Maxio CPQ betrifft. Benutzer haben derzeit Fehler beim Versuch, auf die Anwendung zuzugreifen. Unser Team untersucht und arbeitet aktiv daran, den normalen Service wiederherzustellen. Wir werden zusätzliche Updates bereitstellen, sobald weitere Informationen verfügbar sind.

2. 1. September 2026 um 15:57 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

3. 1. September 2026 um 16:11 UTCresolved

   Dieser Vorfall wurde behoben. Vielen Dank für Ihre Geduld, während wir daran gearbeitet haben, den Service wiederherzustellen, und wir entschuldigen uns aufrichtig für die Störung.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 24. Juli 2026 um 11:21 UTCmonitoring

   Wir kennen und untersuchen Probleme, die den Zugang zu Maxio Advanced Billing aufgrund eines Serviceproblems von Drittanbietern betreffen. Wir beobachten die Situation aktiv und werden Updates bereitstellen, sobald mehr Informationen verfügbar sind.

2. 24. Juli 2026 um 11:32 UTCresolved

   Dieser Vorfall wurde behoben.

3. 24. Juli 2026 um 11:56 UTCpostmortem

   Am 24. Juli 2026 zwischen 10:58 UTC und 11:10 UTC erlebte Maxio Advanced Billing eine kurze Serviceunterbrechung, die durch ein Problem mit einem Ausfall eines Drittanbieters verursacht wurde. Während des Vorfalls sind API-Anfragen an Maxio Advanced Billing möglicherweise fehlgeschlagen oder haben Fehler zurückgegeben. Wenn Ihre Integrationen während der Störung auf fehlgeschlagene API-Anforderungen stießen, empfehlen wir, alle Anfragen, die nicht erfolgreich abgeschlossen wurden, erneut zu wiederholen. Wir entschuldigen uns für die Unannehmlichkeiten und schätzen Ihre Geduld, während das Problem untersucht und gelöst wurde.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 10. Juli 2026 um 15:07 UTCinvestigating

   We are currently investigating this issue.

2. 10. Juli 2026 um 15:08 UTCmonitoring

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

3. 10. Juli 2026 um 15:11 UTCresolved

   This incident has been resolved.

1. 7. Juli 2026 um 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. Juni 2026 um 17:59 UTCinvestigating

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

2. 19. Juni 2026 um 18:42 UTCinvestigating

   We are continuing to investigate this issue.

3. 19. Juni 2026 um 19:17 UTCmonitoring

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

4. 19. Juni 2026 um 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. Juni 2026 um 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. Juni 2026 um 19:50 UTCidentified

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

3. 15. Juni 2026 um 20:21 UTCmonitoring

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

4. 15. Juni 2026 um 20:25 UTCresolved

   This incident has been resolved.

1. 10. Juni 2026 um 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. Juni 2026 um 19:27 UTCidentified

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

3. 10. Juni 2026 um 19:58 UTCmonitoring

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

4. 10. Juni 2026 um 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. Mai 2026 um 13:18 UTCresolved

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

1. 8. Mai 2026 um 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. Mai 2026 um 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. April 2026 um 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. April 2026 um 16:53 UTCinvestigating

   We are continuing to investigate this issue.

3. 20. April 2026 um 16:58 UTCidentified

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

4. 20. April 2026 um 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. April 2026 um 17:34 UTCresolved

   This incident has been resolved.

1. 13. April 2026 um 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. April 2026 um 17:54 UTCmonitoring

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

3. 13. April 2026 um 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. April 2026 um 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. April 2026 um 07:02 UTCresolved

   This incident has been resolved.

1. 1. April 2026 um 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. April 2026 um 15:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 1. April 2026 um 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. April 2026 um 16:51 UTCmonitoring

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

5. 1. April 2026 um 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. April 2026 um 20:58 UTCresolved

   This incident has been resolved.

1. 11. Februar 2026 um 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. Februar 2026 um 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. Februar 2026 um 18:20 UTCresolved

   This incident has been resolved.

1. 4. Februar 2026 um 00:58 UTCinvestigating

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

2. 4. Februar 2026 um 01:25 UTCinvestigating

   We are continuing to investigate this issue.

3. 4. Februar 2026 um 01:28 UTCidentified

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

4. 4. Februar 2026 um 01: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. Januar 2026 um 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. Januar 2026 um 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. Januar 2026 um 20:13 UTCidentified

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

3. 21. Januar 2026 um 21:03 UTCmonitoring

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

4. 21. Januar 2026 um 21:11 UTCresolved

   This incident has been resolved.

1. 17. Januar 2026 um 09: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. Januar 2026 um 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. Januar 2026 um 15:39 UTCidentified

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

3. 8. Januar 2026 um 15:41 UTCmonitoring

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

4. 8. Januar 2026 um 15:43 UTCresolved

   This incident has been resolved.

1. 3. Dezember 2025 um 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. Dezember 2025 um 21:55 UTCmonitoring

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

3. 3. Dezember 2025 um 21:55 UTCmonitoring

   We are continuing to monitor for any further issues.

4. 3. Dezember 2025 um 22:30 UTCresolved

   This incident has been resolved.

1. 24. November 2025 um 22:11 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.