Aborted is the browser saying the request was called off, not that it failed on the network. Something cancelled it: you pressed stop or navigated away, the page itself replaced the request with a redirect or a fresh navigation, or (for developers) script cancelled a fetch. It appears in consoles constantly on healthy sites, because single-page apps cancel superseded requests as a matter of routine.
A full page that persistently aborts before rendering, on every network, is usually being redirected in a loop by the site or an extension until the browser gives up the attempt. Trying an incognito window separates the site (still fails) from your extensions (works).
Is ERR_ABORTED a server error? No. The server may have been mid-response, but the cancellation happened on the client side: a navigation, the stop button, an extension, or the page's own script. The server logs typically show the request simply stopping.
Why does my app's console fill with ERR_ABORTED on route changes? Frameworks fetch data per route; when the user navigates again before a fetch returns, the framework cancels the stale fetch, and the console logs it as aborted. It is bookkeeping noise unless the cancelled request was the only source of data the new screen needed.