We are experiencing issues with our Auth provider ...
# announcements
f
We are experiencing issues with our Auth provider on GrowthBook Cloud. We're currently investigating and will update here as we learn more
h
This outage only affects accessing GrowthBook Cloud. This outage does not affect the delivery of feature flag and experiments via SDKs, nor event tracking through our Managed Warehouse. Please stay tuned for more information.
👍 1
👀 1
f
We're still seeing some intermittent errors when first logging in, but things seem to be improving.
Some more info: Cloudflare is having an outage (https://www.cloudflarestatus.com/) which our Auth provider (Auth0) relies on. On every request to our app, we were hitting Auth0/Cloudflare to validate the auth tokens. We implemented a temporary fix for this on our end, so per-request token validation should work consistently now. Initial logins and refresh tokens may still have issues though.
Cloudflare has resolved their issue and we are no longer seeing auth errors on our end. Let us know if you are still encountering any issues
n
Hi GB Team, We started having a lot of timeouts at about the same time as this issue was happening. After a couple of days the number of timeouts went down a bit but still is like 20 times more than we had before August 21. const gb = new GrowthBook(..) ; await gb.init(..); was hitting 30s timeout and we had to stop using it. Not sure if this is related but the timing is a bit suspicious. Would appreciate your advice on solving this
👀 1
Just following up on this, we are still experiencing a much higher rate of timeouts than before.
f
Just to confirm, are you using cdn.growthbook.io as the api host? We use Fastly for our CDN, so unrelated to the auth issue above. Can you start a new thread in #C01T6Q1SVFV about this so we can track it separately?