Some workers getting 403 for 5-10 minutes, then going back to normal.

[j-at-se]

It's not browser specific, and it surely doesn't look like a session cookie issue or something.

It would make sense on a multi-user browser session where the worker has, for example, their personal Google account signed in at the same time as their company Google account signed in.

We're using Google SSO for authentication and when this happens it's like the worker gets locked out of their session for a good 15-30 minutes until it resolves itself.

Any pointers to start troubleshooting it?

Thank you in advance,

[Hildy]

I'm almost certain that that's the DoS prevention kicking in. It's not Cerb itself that's doing it, but the firewalls in front of Cerb Cloud registering a large volume of requests from a single source and implementing a temp ban. It probably just needs the threshold adjusted upwards a little bit.

Can you email 'team@cerb.ai' with more information (like the gateway IP those requests are coming from)?

[j-at-se]

Oh, interesting. I'll gather that info and email them. THANKS!