Skip to main content

Is Maxio Down?

No — Maxio is up

Reachable from all 8 checked regions

Average response time: 352ms

Last checked · checks run every 6 hours

Official status page: https://maxio.statuspage.io

Maxio uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
234ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 30 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

30-day clean streak
Aug 25: 100.00% uptime, 24 checks
Aug 26: 100.00% uptime, 32 checks
Aug 27: 100.00% uptime, 32 checks
Aug 28: 100.00% uptime, 32 checks
Aug 29: 100.00% uptime, 32 checks
Aug 30: 100.00% uptime, 32 checks
Aug 31: 100.00% uptime, 32 checks
Sep 1: 100.00% uptime, 32 checks
Sep 2: 100.00% uptime, 24 checks
Sep 3: 100.00% uptime, 30 checks
Sep 4: 100.00% uptime, 21 checks
Sep 5: 100.00% uptime, 30 checks
Sep 6: 100.00% uptime, 32 checks
Sep 7: 100.00% uptime, 32 checks
Sep 8: 100.00% uptime, 30 checks
Sep 9: 100.00% uptime, 32 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 16 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 31 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 37 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 8 checks
Aug 25 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
288ms
DNS 133ms TCP 3ms TLS 14ms TTFB 277ms
arn
344ms
DNS 143ms TCP 1ms TLS 10ms TTFB 333ms
bom
742ms
DNS 378ms TCP 2ms TLS 14ms TTFB 730ms
ord
99ms
DNS 60ms TCP 1ms TLS 12ms TTFB 88ms
sin
522ms
DNS 443ms TCP 1ms TLS 13ms TTFB 512ms
sjc
204ms
DNS 65ms TCP 2ms TLS 14ms TTFB 192ms
syd
539ms
DNS 307ms TCP 1ms TLS 12ms TTFB 527ms
yyz
82ms
DNS 31ms TCP 1ms TLS 12ms TTFB 71ms

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 18 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.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Maxio goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required