Summary
- An ASN or directory record identifies one layer of responsibility; it does not prove complete topology, facility ownership or service performance.
- Operational review should timestamp every observation and keep declared fields separate from measured behaviour.
The useful question is not whether one record looks authoritative, but which control surface it actually describes. A registry entity can identify the maintainer of AS59795. An operator directory can preserve declared facilities or prefix counts. Route collectors show what was visible from particular observation points at a particular time. PerfGrid’s own incident posts add attributed accounts of DNS, cache and hardware work, but they are not independent availability measurements. Procurement and incident teams should therefore maintain a layer-by-layer ledger: source owner, observation time, claim scope and unresolved dependency.
That method makes updates comparable without promoting a registration, declaration or incident narrative into proof of the whole hosting system.
