You'll notice
Useful2 Signal3
Server errors while listing peer sessions are recognised properly and treated as retryable.
What's wrong with this entry?
Anonymous. No account, no email.
What
Errors while listing peer sessions were only recognised as server-side when formatted as "HTTP 5xx". Any message containing a 5xx status code now matches too, so these are correctly treated as not your fault and bucketed as a server error rather than surfacing as an actionable failure.
Evidence
bridge_http_5xx
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.