Maxio incident
Advanced Billing Subscriptions API endpoints rejecting unrecognized fields
Resolved after 1 hour 48 minutes, affecting API and Integrations to 3rd Party Services, on June 10, 2026.
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.
Affected components
Update timeline
- identified Jun 10, 2026, 06:58 PM UTC
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.
- identified Jun 10, 2026, 07:27 PM UTC
We are continuing to work on a fix for this issue.
- monitoring Jun 10, 2026, 07:58 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 10, 2026, 08:47 PM UTC
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.
Your product runs on more than Maxio
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services