What can break, and who runs it

Most of Novus Learn has no server to go down. The status page separates what runs on your device, what this site serves, and what somebody else runs, and describes the failure each would actually produce. That is more useful than a green tick, because it tells you where to look.

A status number is only worth reading if something measures it. There is no uptime monitor, no synthetic check and no incident feed behind this site, so quoting a percentage would be an invention. The page says that outright and reports architecture instead.

The threat model, the response headers the site sets, how third-party content is isolated, and how to report a problem. The short version: your files are parsed in the browser under a same-origin policy, formal answer keys never reach the browser at all, and nothing you create is stored on a server.

Check the on-device list on the status page first. If the feature is there, a reload usually resolves it. If a single topic will not open, try a different one: that separates an upstream outage from a problem with one article.