Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Maxio Outage History

Every past Maxio outage tracked by IsDown, with detection times, duration, and resolution details.

There were 45 Maxio outages since August 2023. The 16 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major April 20, 2026

April 2026: Advanced Billing: Invoice Viewing Errors (UI & API)

Detected Apr 20, 2026 12:24 PM EDT · Resolved Apr 20, 2026 1:36 PM EDT · Duration about 1 hour

Maxio's Advanced Billing service experienced 502 timeout errors for 1.2 hours that prevented users from viewing consolidated invoices in the application UI and accessing invoice PDFs via the API. The issue was caused by timeouts and affected the main application and API components, though standard invoice API endpoints and public invoice URLs remained functional. A fix was implemented and the incident was resolved with no impact to underlying invoice data.

Minor April 13, 2026

April 2026: Maxio Platform E-Billing Degradation

Detected Apr 13, 2026 1:29 PM EDT · Resolved Apr 14, 2026 3:03 AM EDT · Duration about 14 hours

Maxio experienced a 13.6-hour degradation of their E-Billing platform where customers encountered errors when trying to access e-billing related pages. The incident also affected email sending functionality. The issue was resolved through multiple fixes implemented over the course of the incident, with full resolution confirmed after monitoring the effectiveness of the changes.

Major April 1, 2026

April 2026: Advanced Billing System Performance Degradation

Detected Apr 1, 2026 11:25 AM EDT · Resolved Apr 1, 2026 4:59 PM EDT · Duration about 6 hours

Maxio's Advanced Billing System experienced major performance degradation for 5.6 hours, affecting processing times and related functionality across the main application. The team identified the root cause and implemented a fix, followed by a monitoring period to ensure stability. The incident was fully resolved after normal performance was restored.