Maxio outage history

We are investigating an issue affecting access to Maxio CPQ. Users are currently experiencing errors when attempting to access the application. Our team is actively investigating and working to restore normal service. We will provide additional updates as more information becomes available.

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

This incident has been resolved. Thank you for your patience while we worked to restore service, and we sincerely apologize for the disruption.

We are aware of and investigating issues affecting access to Maxio Advanced Billing due to a third-party service issue. We are actively monitoring the situation and will provide updates as more information becomes available.

This incident has been resolved.

On **July 24, 2026**, between 10:58 UTC and 11:10 UTC, Maxio Advanced Billing experienced a brief service disruption caused by an issue with a third-party service provider outage. During the incident, API requests to Maxio Advanced Billing may have failed or returned errors. If your integrations encountered failed API requests during the disruption, we recommend retrying any requests that did not complete successfully. We apologize for the inconvenience and appreciate your patience while the issue was investigated and resolved.

We are currently investigating this issue.

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

This incident has been resolved.

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

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

We are continuing to investigate this issue.

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

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.

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.

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

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

This incident has been resolved.

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.

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

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

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.

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

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.

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.

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.

We are continuing to investigate this issue.

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

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.

This incident has been resolved.

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.

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

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.

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.

This incident has been resolved.

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.

We are continuing to investigate this issue.

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.

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

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.

This incident has been resolved.

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.

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.

This incident has been resolved.

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

We are continuing to investigate this issue.

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

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.

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.

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.

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

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

This incident has been resolved.

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.

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.

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

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

This incident has been resolved.

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.

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

We are continuing to monitor for any further issues.

This incident has been resolved.

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.