The problem is definitely a bit more complicated. While it's possible this issue did not involve an issue with Brave at all, it's also possible that it did. The

The problem is definitely a bit more complicated. While it's possible this issue did not involve an issue with Brave at all, it's also possible that it did. The behavior observed (inferring from the screenshot) suggests the user's access to this extension was denied at the time. A 401 response (Unauthorized) from Brave's proxy-endpoint (go-updater.brave.com in this case, I believe) would result in this message being shown. It is entirely possible the user happened to catch a rare, transient issue with our proxy. Sampson (Brave Team) Brave proxies Google endpoints to prevent users from making unintended contact with Google.