- Service Status
- /
- Maxio
Is Maxio Down?
- Maxio's status page
- Operational · no open incidents
- FlareWarden checks
- Website reachable · 8 of 8 regions · 238 ms
Right now
The verdict is the worse of these two. How we decide
Maxio's status page
maxio.statuspage.io · read · checked every 3 minutes
| Component | Status |
|---|---|
| Main Application | Operational |
| Billing Portal | Operational |
| API | Operational |
| Chargify.js (Maxio.js) | Operational |
| Scheduled Payment Processing | Operational |
| Email Sending | Operational |
| Documentation Site | Operational |
| Integrations to 3rd Party Services | Operational |
| Webhooks | Operational |
| Maxio Hosted Pages | Operational |
| Data Exports | Operational |
| Main Application | Operational |
17 more, all operational · show all 29
| Component | Status |
|---|---|
| Maxio Advanced Billing | |
| Main Application | Operational |
| Billing Portal | Operational |
| API | Operational |
| Chargify.js (Maxio.js) | Operational |
| Scheduled Payment Processing | Operational |
| Email Sending | Operational |
| Documentation Site | Operational |
| Integrations to 3rd Party Services | Operational |
| Webhooks | Operational |
| Maxio Hosted Pages | Operational |
| Data Exports | Operational |
| Maxio Platform | |
| Main Application | Operational |
| Integrations to 3rd Party Services | Operational |
| Email Sending | Operational |
| API | Operational |
| Maxio Payments | Operational |
| e-Invoicing | Operational |
| Maxio CPQ | |
| Maxio CPQ Console | Operational |
| Maxio CPQ API | Operational |
| DocuSign Integration | Operational |
| Revops eSignature | Operational |
| Salesforce Integration | Operational |
| HubSpot Integration | Operational |
| Stripe Integration | Operational |
| RevOps Documentation | Operational |
| RevOps Public Website | Operational |
| Webhooks | Operational |
| Intuit Developer Group QuickBooks Online API | Operational |
| Intuit Developer Group Webhooks | Operational |
FlareWarden checks
maxio.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours
- Regions up
- 8 of 8
- Response
- 238 ms
- Checked
By region
- Chicago reachable, 131 ms
- London reachable, 87 ms
- Los Angeles reachable, 151 ms
- San Jose reachable, 119 ms
- Singapore reachable, 516 ms
- Sydney reachable, 324 ms
- Tokyo reachable, 497 ms
- Toronto reachable, 79 ms
Timing by region
| Region | DNS | TCP | TLS | TTFB |
|---|---|---|---|---|
| Chicago | 88 ms | 4 ms | 11 ms | 124 ms |
| London | 38 ms | 3 ms | 13 ms | 78 ms |
| Los Angeles | 61 ms | 2 ms | 17 ms | 145 ms |
| San Jose | 29 ms | 2 ms | 12 ms | 112 ms |
| Singapore | 247 ms | 19 ms | 40 ms | 512 ms |
| Sydney | 296 ms | 1 ms | 10 ms | 320 ms |
| Tokyo | 189 ms | 1 ms | 11 ms | 494 ms |
| Toronto | 34 ms | 2 ms | 9 ms | 75 ms |
History
Incidents Maxio reported
Since Oct 22, 32 days · from maxio.statuspage.io
- Incidents
- 1
- Major or critical
- 1
- Median to resolve
- 24m
- lasted 24m
Maxio website availability
Measured by FlareWarden · maxio.com
- Last 7 days
- 100%
- Last 30 days
- 100%
- Last 90 days
- 100%
- Avg response, 30 days
- 236ms
Last 30 days
90-day clean streakMeasured by FlareWarden's own checks of maxio.com from multiple regions every 6 hours. Maxio's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 90 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
What Maxio does
Maxio handles subscription billing, invoicing and revenue recognition for B2B software companies, including usage-based metering and rating. It connects to more than 20 payment gateways, among them Stripe and Braintree, and produces GAAP and IFRS reporting for finance teams. Maxio Advanced Billing is the product that carries the former Chargify lineage, still visible in the Chargify.js component name on the status page.
What an outage looks like
Embedded card forms built on Chargify.js fail to render, so signup and checkout break inside your own application while the rest of it works. Scheduled payment processing does not run, leaving renewals uncharged for the window. Webhooks to your systems stop arriving, so entitlements are not updated and paying customers can be locked out. Billing portal and hosted pages return errors to customers.
What to do about it
Read maxio.statuspage.io, which groups components under Maxio Platform, Maxio Advanced Billing, Maxio Payments, Hosted Pages, CPQ, Data Exports and RevOps. Advanced Billing breaks out its Main Application, Billing Portal, API, Chargify.js, Scheduled Payment Processing, Email Sending, Webhooks and integrations. After recovery, reconcile the renewal window rather than assuming payments simply failed, and watch for webhooks that arrived late instead of not at all.
Is it down for everyone, or just you?
If this page says Maxio is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.
Related services
Maxio outage FAQ
Will renewals due during the outage be missed?
Why is my own checkout broken when my application is fine?
What happened to Chargify?
Does an outage affect my accounting integrations?
How we measure this
- We request Maxio's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Maxio publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Maxio itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.
Get alerted when Maxio goes down
We check Maxio every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring


