Skip to main content

Is Maxio Down?

No — Maxio is up
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

Operational
Maxio's components, as its status page reports them
ComponentStatus
Main ApplicationOperational
Billing PortalOperational
APIOperational
Chargify.js (Maxio.js)Operational
Scheduled Payment ProcessingOperational
Email SendingOperational
Documentation SiteOperational
Integrations to 3rd Party ServicesOperational
WebhooksOperational
Maxio Hosted PagesOperational
Data ExportsOperational
Main ApplicationOperational
17 more, all operational · show all 29
All of Maxio's components
ComponentStatus
Maxio Advanced Billing
Main ApplicationOperational
Billing PortalOperational
APIOperational
Chargify.js (Maxio.js)Operational
Scheduled Payment ProcessingOperational
Email SendingOperational
Documentation SiteOperational
Integrations to 3rd Party ServicesOperational
WebhooksOperational
Maxio Hosted PagesOperational
Data ExportsOperational
Maxio Platform
Main ApplicationOperational
Integrations to 3rd Party ServicesOperational
Email SendingOperational
APIOperational
Maxio PaymentsOperational
e-InvoicingOperational
Maxio CPQ
Maxio CPQ ConsoleOperational
Maxio CPQ APIOperational
DocuSign IntegrationOperational
Revops eSignatureOperational
Salesforce IntegrationOperational
HubSpot IntegrationOperational
Stripe IntegrationOperational
RevOps DocumentationOperational
RevOps Public WebsiteOperational
WebhooksOperational
Intuit Developer Group QuickBooks Online APIOperational
Intuit Developer Group WebhooksOperational

FlareWarden checks

maxio.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
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
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Chicago88 ms4 ms11 ms124 ms
London38 ms3 ms13 ms78 ms
Los Angeles61 ms2 ms17 ms145 ms
San Jose29 ms2 ms12 ms112 ms
Singapore247 ms19 ms40 ms512 ms
Sydney296 ms1 ms10 ms320 ms
Tokyo189 ms1 ms11 ms494 ms
Toronto34 ms2 ms9 ms75 ms
We check that maxio.com loads, not every feature behind it. Test it yourself

History

Incidents Maxio reported

Since Oct 22, 32 days · from maxio.statuspage.io

Incidents
1
Major or critical
1
Median to resolve
24m
  1. 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 streak
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 32 checks
Nov 1: 100.00% uptime, 32 checks
Nov 2: 100.00% uptime, 32 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 32 checks
Nov 5: 100.00% uptime, 32 checks
Nov 6: 100.00% uptime, 32 checks
Nov 7: 100.00% uptime, 32 checks
Nov 8: 100.00% uptime, 32 checks
Nov 9: 100.00% uptime, 32 checks
Nov 10: 100.00% uptime, 32 checks
Nov 11: 100.00% uptime, 32 checks
Nov 12: 100.00% uptime, 32 checks
Nov 13: 100.00% uptime, 32 checks
Nov 14: 100.00% uptime, 32 checks
Nov 15: 100.00% uptime, 32 checks
Nov 16: 100.00% uptime, 32 checks
Nov 17: 100.00% uptime, 32 checks
Nov 18: 100.00% uptime, 32 checks
Nov 19: 100.00% uptime, 32 checks
Nov 20: 100.00% uptime, 32 checks
Nov 21: 100.00% uptime, 32 checks
Nov 22: 100.00% uptime, 24 checks
Oct 24 Today
No downtime Partial Downtime Not measurable No data

Measured 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.

Test it yourself

Related services

Maxio outage FAQ

Will renewals due during the outage be missed?
Scheduled Payment Processing is listed as its own component precisely because it can fail on its own, so a renewal due in the affected window may not have been attempted. Reconcile that window against your own records once the incident closes rather than assuming either outcome, because a charge that succeeded but did not report back looks identical to one that never ran.
Why is my own checkout broken when my application is fine?
Because Chargify.js, listed on the status page as Chargify.js (Maxio.js), is the embedded component that renders card fields inside your application and tokenizes the card. Your servers, your front end and your database can all be healthy; the piece that will not load is hosted by Maxio. That is why the failure appears inside your product and looks like your bug.
What happened to Chargify?
Chargify became part of Maxio and its status reporting moved to the Maxio page. The product now appears as Maxio Advanced Billing, which is the largest component group on that page, and the Chargify name survives in the Chargify.js (Maxio.js) row. If you are searching for Chargify status, maxio.statuspage.io is the page you want.
Does an outage affect my accounting integrations?
It can, and those are reported separately. The status page carries a RevOps group covering DocuSign, eSignature, Salesforce, HubSpot and Stripe integrations, and an Intuit Developer Group covering the QuickBooks Online API and its webhooks. A billing incident that leaves the main application working can still stop invoices syncing into your accounting system, which surfaces at month end rather than immediately.

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 403 or 429 means 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
Free plan available No credit card required