Don't forget to request your credit per their SLA[0]. You have 10 days to request your credit, which by my calculations should be 10% of this months' charge. Not a fair trade for leaving us dead in the water, but SLAs in general are worthless.
Oh no, it's not down, it's just "experiencing elevated error rates" /s. After the appalling outage they had last spring, it's too soon to be dealing with this again. And there have been a couple of small outages in between then and now.
AWS single az failures can frequently cause general failures across other AWS services like lambda, Kinesis etc. Your app might tolerate the failure but be taken out by events beyond your control.
Ideally you'd want a way to fail traffic over to another region.
May not be related but I recently had an incident where we finally started opening up our beta and got a few signups. That day coincidentally we started getting a mismatch nonce error from Auth0 which prevented people from logging in. I assume I must have done something to break it but could not figure out what. So I ended up taking most of the night making an independent authentication system using an existing module I made before.
Their support first replied by saying that no, it wasn't a priority because of my lack of support plan or something. The next sentence was about how they could not do anything until I generated a custom log file.
Just didn't seem worth it anymore for what we actually need.
Don't forget to request your credit per their SLA[0]. You have 10 days to request your credit, which by my calculations should be 10% of this months' charge. Not a fair trade for leaving us dead in the water, but SLAs in general are worthless.
[0]: https://auth0.com/docs/support/services-level-descriptions