Network status
Every domain in the group, probed from one vantage point. Failures are shown as failures.
| Domain | Role | State | Code | Time | Size |
|---|---|---|---|---|---|
| neverenders.io | Parent engine | serving | 200 | 414 ms | 16.3 KB |
| neverenders.tech | Forensics | serving | 200 | 198 ms | 12.4 KB |
| neverenders.shop | Case packages | serving | 200 | 196 ms | 15.0 KB |
| neverenders.blog | Editorial | serving | 200 | 272 ms | 7.6 KB |
| neverenders.art | Gallery | serving | 200 | 455 ms | 232.2 KB |
| neverenders.org | Foundation | serving | 200 | 198 ms | 7.5 KB |
| neverenders.me | Engagements | serving | 200 | 691 ms | 7.9 KB |
| plasmadonate.org | Directory | serving | 200 | 240 ms | 17.9 KB |
| neverenders.site | Status board | serving | 200 | this page | - |
Measured 2026-09-18 22:24 UTC. Freshly probed on this request. Machine readable at /status.json.
Summary
9 serving
Returned HTTP 200 with a real response body at the last measurement.
0 placeholder
Hosting is active and the domain resolves, but the host's parking page is what answers. A plain uptime check would wrongly call these green.
0 failing
Reached and returned a non 200, or could not be reached at all.
240 ms median
Median response across the serving domains, from this server. One vantage point, not a distributed monitor.
Why placeholder is its own state
A domain parked on its host answers HTTP 200 with a cheerful page saying the site is almost here. Every naive monitor calls that up, which means a network can report perfect uptime while several of its properties serve nothing at all.
Separating it is the entire reason this board is more useful than a green light. The method page sets out the probe, the timeouts, and what these numbers cannot tell you.