it's really tough to figure out because it's a cloudflare-specific catch-all error, so it basically gives us no information about what actually went wrong. but yeah they definitely seem to be one-off errors and not related to bigger problems since they're like one page and they're gone, but since 520 is a cloudflare status code and not an actual http status code, we essentially can't even match up where something went wrong with our own logs (because our own error logs wouldn't ever show a 520 status). :/