Summary

Observed status. Minimal interpretation.
Overall
operational as before
Incidents (30d)
0 reported
Degradations (30d)
0 confirmed
Last change
n/a no lasting change recorded
Note: “operational” here means responses were observed. It does not imply reliability, correctness, or safety.

Systems

Current state by component.
Component Status Last observed Detail
HTTP operational 200 response observed.
TLS (via platform) operational Termination handled upstream. Outcome unchanged.
Static assets operational Served without transformation.
DNS unchanged Resolution observed. No action required.
view incident history

Incident history

Documented events. No implied progress.
  1. investigating
    Reports of slowness
    Increased latency was reported. No causal mechanism was confirmed. The state remained serviceable.
  2. unchanged
    Outcome unchanged
    The condition was observed to be within expected variance. No corrective action was required.
  3. degraded
    Asset fetch failures
    A subset of requests failed due to upstream constraints. Impact was limited and short-lived.
  4. unchanged
    No lasting change recorded
    Normal behavior resumed. This did not alter long-term state.
What counts as an incident?

An incident is any recorded event where the observed state differed from normal expectations. Recording an incident does not imply fault, preventability, or future relevance.

If nothing changed, the most accurate resolution is: unchanged.

Design reference

Common components used across unchanged.fyi projects.
Typography
Heading sample
Body text should be calm, declarative, and literal.
monospace: 2026-01-18 00:00Z
Badges
operational investigating degraded unchanged
Links
reference link underlined, consistent, non-persuasive.
Buttons
disabled by default when action is not implemented.
This page is intentionally static. It serves as a reference, not an operational control surface.