About this page

What we promise

We aim for 99.9% availability each month for Creator Studio, Platform API, and Real-time Connections. Something counts as available when a check made from outside Aixa can reach it and gets back the answer it expected.

How we check

We check every part of Aixa once a minute, from outside it. The checks run on separate systems with their own sign-in, so they keep working and keep reporting even during an outage that takes the rest of Aixa down.

This page reads the results of those checks. It never asks Aixa how Aixa is doing — a status page that depended on the thing it reports on would go down with it, on the one day it matters.

What the uptime figures mean

• Every part of Aixa is checked once a minute.
• Slow still counts as working. The service answered, even if it answered badly. Slow minutes are reported separately rather than hidden.
• No answer counts as down. A request that never comes back is a request that failed.
• It takes three failed checks in a row to count as downtime. One dropped connection is not an outage, and calling it one would make this page cry wolf.
• Minutes we could not check are left out of the sum — and we say so. This is the important one. If our own checks stop working, those minutes do not quietly count as perfect uptime. They are taken out of the calculation, and we publish how much of the period we were actually able to check, right next to the figure. Where we checked too little of a period to say anything meaningful, we publish no percentage at all rather than an inflated one.
• The 90-day figure is total working minutes divided by total counted minutes — never the average of the daily percentages, which would weight a quiet day the same as a broken one.

When we cannot check

Sometimes our checks stop reporting, or the results we have get too old to trust. When that happens we mark everything as Not checked. We never leave a green tick standing on the strength of a result we did not take.

Not checked does not mean broken. It means we cannot currently tell you either way. If you see it, try Aixa as you normally would, and tell us if something is not working.

Anything we have already told you about stays on the page and stays accurate. Our checks going quiet never hides an incident we have published.

Services we rely on

Some things Aixa depends on are run by other companies — sign-in and payments, for example. We show their status so you can see when a problem is coming from somewhere else. They never change the overall status at the top of the page, and we publish no uptime figure for them: keeping an availability record for somebody else’s service is not ours to do, and a half-kept one would be worse than none.

Incidents

Incidents are written by a person, not generated. Each one keeps a timeline of what we knew and when we knew it, and the time we published it is recorded automatically — so it cannot be quietly moved afterwards to make our response look faster than it was.

Incidents stay on the record. We do not take them down once they are over.

Getting told, rather than checking

You can subscribe to updates in the reader app of your choice, and new incidents and updates will come to you. We do not ask for your email address: a subscriber list is customer data a public status page has no business holding.

Privacy

This page sets no cookies, runs no analytics, and loads nothing from anybody else. There is nothing to consent to, which is why you were not asked. Choosing light or dark is the only thing kept in your browser, and only if you choose one.

Something wrong that we have not reported?

Automated checks cannot see everything. If you are hitting a problem this page does not show, please tell us at support@iamaixa.com. A report from a customer is one of the most reliable signals we have.