Summary
- Each ASN must be checked against its own registry, routing and origin-authorisation record.
- A directory entry or observed route can support a narrow conclusion, but neither proves a common topology, owner or service level.
The practical mistake is to turn several compatible records into a single story of control. AS212237 and AS141445 sit in different evidence contexts, and each source answers a different question: who maintains a registration, what an operator declares, what collectors can currently observe, and which origins are authorised. For procurement, incident response or due diligence, the useful method is therefore a two-column evidence ledger. Record each ASN separately, timestamp every observation and escalate only the facts that agree across independent sources.
PXNET Changgong Zhang may be the shared subject under review, but operational confidence begins by preserving the boundary between the two identifiers.
