And the error message is strange:
>There is no accout for zuora account id:2c92a00d6ff0e970016ffbde74ae767c (3,201)
It seems that everyone having issues is seeing the same error.
Unfortunately this provides a perverse incentive to NOT report an outage, as even a small outage would be a contract breach for a "many nines" SLA, whereas many small breaches added up over a month could also breach a contract for (relatively) smaller companies. If the client doesn't notice, then it doesn't count.
Anecdotally, the only status pages I've seen that update automatically have no monetary incentive to maintain the page.
Ain't that the truth !
I remember working with organisations that had Verizon leased lines.
100% SLA the Verizon sales reps would say, normally accompanied with a sheet of paper that said "100% SLA" in big bold letters.
Of course the line would go down. Some manager would the come to my desk, thumping his fist and talking about the 100% SLA. I'd say "sure, but did you read the small print".
In all my years, I don't think I ever saw anyone get a SLA payment from Verizon.
If you're just getting a phone number and a few extensions from them for small office telephony, no. If you're leasing multiple high-availability DIA circuits from them, far easier (but still absurdly difficult). Speaking from first-hand, nightmarish experience dealing with their "VEC".
Don't get me started on trying to get SLA payment when they goof up LNPs either.
Zuora seems to be a bit like Stripe? Maybe it's their outage, or maybe someone at Zoom forgot to pay the Zuora bill..
Gitlab had an outage today related to Zuora going down. My guess is the backends directly call to these APIs and they don't have any form of caching or storing the info from these APIs elsewhere.