we are seeing 504 gateway timeouts when getting the token
Hi,
all our apps are down. Like I said in the title we are seeing 504 responses when getting the token. Can someone look into it.
10 Replies
Happy to help, but need a bit more info please. Can you please tell me your business name and data region? When it started, is it still happening? What SDK and version you are using. Thanks.
thank you, the region is Sydney AU the business name is ankor.io. The sdk we are using is @kinde-oss/kinde-auth-pkce-js 3.1.0. The 504 started happening last night
apologies for the misinformation it seems the 504 is only hitting 2 of our apps the others are working fine. All our apps make a call to https://login.ankor.io/oauth2/token but for some reason it times out for 2 of our apps
the one app that still works uses password authentication, the 2 that get the 504 are setup with email verification code
It seems to be working now. Could you please let us know what was going on?
yes, it would be great to have an idea of what the issue was for our internal incident report
I've asked the team to investigate.
Will update this thread when I have more information
Can I clarify if you are all from same company?
If you have any logs or other info you can send, please open a ticket in the #🤫┃confidential-support channel
Yes, we're all in the same company. Unfortunately we don't have any logs on our side -- usesrs never managed to get in, as the initial auth flow was borked -- , just the as I mentioned, the initial call to login.ankor.io/oath2/token was timing out with 504. To be clear, login.ankor.io is a cname record to ankor.kinde.com.
Okay, we did detect some downtime in our logs. We are still investigating as it looks like the 504s arose only for your company in a unique state, and it was not pervasive across AU region. Our investigating dev thinks a deployment his morning might have fixed things. Can you confirm which apps are still down if any?
We're not dropping it and will keep looking into.
Confirming all our apps are working now. They started working again around 10am this morning. Please let us know if you have any other info and thank you for your help
Glad things are back on track. Apologies if this was caused by something our end. We are still trying to find the root cause and will report back 🙂