When an ASN Changes but the Server Does Not Move

When an ASN Changes but the Server Does Not Move

By WhatsMyIP Team · November 18, 2026 · 9 views

Observed condition

ASN origin change baseline

A stable service address or nearby replacement prefix begins appearing under a different origin after a routing or hosting change.

Evidence capture

Fields that make the result reproducible

Save prefix, origin ASN, collector views, registry holder, ROA state, DNS history, service fingerprint, and timestamps.

Claim boundary

Where the conclusion must stop

BGP observation alone cannot establish rack location, contractual ownership, or whether the change was authorized.

When an ASN Changes but the Server Does Not Move begins with an observable problem: A stable service address or nearby replacement prefix begins appearing under a different origin after a routing or hosting change. Treating ASN origin change as a measured event changes the work. It requires a baseline, an exact input, a timestamp, and a comparison that can fail. Those details stop a later recovery from being credited automatically to the last setting someone changed.

Several layers can influence the symptom, including BGP origin, announced prefix, autonomous system number, registry allocation, route object, and RPKI validity. Their values must remain separate until the causal path is understood. The definitions used here come from IETF BGP specification in RFC 4271 and IANA autonomous system number registry. IETF RPKI origin validation in RFC 6811 provides a third reference for the protocol or measurement boundary. The external standards anchor terminology and expected behavior, while the case record establishes what happened on the site, device, or route being examined.

The ASN origin change condition that must be isolated

Start with the narrow event, not a broad verdict. A stable service address or nearby replacement prefix begins appearing under a different origin after a routing or hosting change. The first record should say what was expected, what was returned, and which layer might connect the two. Collecting that statement before remediation protects the baseline from hindsight and keeps unrelated changes from being treated as proof.

The core record should include the address, longest matching prefix, origin ASN, registry holder, route visibility, ROA state, collector, and UTC timestamp. For this case, also do the following: Save prefix, origin ASN, collector views, registry holder, ROA state, DNS history, service fingerprint, and timestamps. Retain machine-readable values and exact errors, not only a screenshot. Preserve unsuccessful runs because an intermittent transition often contains more diagnostic information than the final success. Remove credentials and personal data before evidence is shared.

ASN origin change evidence record
Review stageEvidence to preserve
Baselinethe address, longest matching prefix, origin ASN, registry holder, route visibility, ROA state, collector, and UTC timestamp
Focused captureSave prefix, origin ASN, collector views, registry holder, ROA state, DNS history, service fingerprint, and timestamps.
Controlled comparisonSeparate an actual origin change from a more-specific announcement, multi-origin prefix, stale database, or changed DNS answer.
Decision boundaryBGP observation alone cannot establish rack location, contractual ownership, or whether the change was authorized.

With the evidence table prepared, identify the address's announcing network. That step connects the article to the exact tool or commercial guide that resolves its main question. Store the returned fields and any error. Do not rerun until the baseline is complete, because an updated answer would no longer describe the original ASN origin change event.

A controlled comparison for ASN origin change

The comparison design is specific: Separate an actual origin change from a more-specific announcement, multi-origin prefix, stale database, or changed DNS answer. Two simultaneous changes create an ambiguous success. Keep all other practical conditions fixed, note exceptions, and repeat in alternating order. When perfect control is impossible, say which factor moved and collect enough samples to show whether it dominates the result.

For every attempt, note input, UTC time, environment, changed variable, output, and error. Follow that table while you resolve the longest matching announced prefix, compare more than one routing view, and keep registry ownership separate from routing origin. Repeat both sides of the comparison rather than chasing only the failed side. The resulting series shows whether the mechanism is persistent, intermittent, source-dependent, or merely coincident with the proposed repair.

ASN origin change decision matrix
Decision stage
Evidence question
Article-specific action
Baseline
Which exact condition must be reproduced?
Save prefix, origin ASN, collector views, registry holder, ROA state, DNS history, service fingerprint, and timestamps.
Comparison
Which controlled change can separate the suspected mechanism?
Separate an actual origin change from a more-specific announcement, multi-origin prefix, stale database, or changed DNS answer.
Interpretation
Which recorded signal explains the observed result?
The service can remain in the same facility while a transit, mitigation, or hosting network changes the visible origin.
Correction
Which smallest change addresses the demonstrated cause?
Investigate routing evidence and provider notices before rewriting ownership labels or security rules.

Before interpreting the table, check that every row refers to the same intended subject and that no redirect, hostname change, address-family change, or account difference altered the scope. Mark missing responses separately from negative responses. Review the sequence as well as the totals, since clustered faults can disappear inside an acceptable overall rate. This quality pass is especially important for ASN origin change, where a clean state after recovery can otherwise overwrite the evidence from the transition.

Diagnostic process graph for ASN origin change. This shows workflow order, not measured performance.
  1. 1. Preserve baselineRecord the original ASN origin change condition before any edit.
  2. 2. Collect the primary signalUse the identify the address's announcing network with the same input and timestamp.
  3. 3. Compare controlled casesSeparate an actual origin change from a more-specific announcement, multi-origin prefix, stale database, or changed DNS answer.
  4. 4. Verify the correctionInvestigate routing evidence and provider notices before rewriting ownership labels or security rules.

What the recorded ASN origin change signals mean

The evidence supports this reading: The service can remain in the same facility while a transit, mitigation, or hosting network changes the visible origin. Resist extending it beyond the measured layer. A standards-compliant response does not promise the desired user outcome, and infrastructure context does not identify a person. Apparent contradictions often reveal different caches, regions, versions, routes, or identifiers, so align those conditions before reconciling the answers.

If the primary result does not explain the symptom, continue with From a List of IP Addresses to Defensible Network Groups. That article handles the neighboring mechanism most likely to alter the conclusion. Linking to a specific diagnostic question is more useful than a generic related-content block because readers can see why the next page belongs in the same evidence chain.

Repairing the measured ASN origin change problem

Remediation should follow the observation directly. Investigate routing evidence and provider notices before rewriting ownership labels or security rules. Keep unrelated records, routes, providers, and application settings unchanged for the confirmation run. This makes a failed fix informative and a successful fix attributable. Store the new output next to the original rather than overwriting the incident record.

ASN origin change evidence worksheet

Use this private browser checklist while testing. It is not submitted or stored.

Verification should include a fresh session, a clean cache or resolver when relevant, and an independent network for distributed systems. Monitor the narrow failure indicator rather than only a broad availability score. Include enough alert context for the owner to identify the layer without repeating the entire discovery process, and schedule another controlled check after major releases.

Evidence boundary for ASN origin change

BGP observation alone cannot establish rack location, contractual ownership, or whether the change was authorized. An origin ASN describes the network announcing a prefix at the time observed. It does not by itself identify the customer, server operator, or physical location.

The limits of the ASN origin change finding

The boundary is explicit: BGP observation alone cannot establish rack location, contractual ownership, or whether the change was authorized. In addition, An origin ASN describes the network announcing a prefix at the time observed. It does not by itself identify the customer, server operator, or physical location. Report what the controlled runs establish and what another source, region, application, or time could change. A responsible conclusion remains useful when the initial hypothesis is wrong because the preserved evidence still removes unsupported explanations and defines the next measurement.

Continue the ASN origin change investigation