When Rublon servers become unavailable, your users will not be able to undergo Multi-Factor Authentication (MFA) and will be bypassed or denied depending on the settings of each connector.
Check if Rublon API Is Down
Check the status of Rublon API. If Rublon API is operating normally, but servers become unavailable when your users log into their integrations, try opening this link on various computers in your company. If you get the Rublon Authentication Server works! messages on some machines, then the cause of the issue must have to do with your other machines for which this link does not work. Check your antivirus, firewall settings, and ensure port 443 is open.
If you cannot troubleshoot on your own, contact Rublon Support. Remember to include as much information as possible, including log files and screenshots.
Decide What Happens After Rublon Servers Become Unavailable
Rublon connectors allow you to decide what happens when a user logs into an integrated service while Rublon servers are unavailable. This option is most often called Fail Mode and usually takes one of these two values:
Bypass - 2FA will be omitted and the user will be logged in right away after they provide the correct login and password
Deny - the user will be denied access during the second step of authentication even if the login and password they provided were correct
While troubleshooting your issue, you might want to change the Fail Mode to bypass so that your users have uninterrupted access to the integration.
Refer to How to set Fail Mode in Rublon connectors? to learn how to set Fail Mode for each connector.