Current network information may require authorized, up-to-date portability or routing data. This static prototype has no such live feed.
Why the prefix can mislead
A person may keep the same number after switching providers. The old range assignment then remains visible in static metadata.
Do not rename the field
If the source gives original carrier, present original carrier. Do not silently label it “current operator.”
Know when to stop
Without verified live data, report current carrier as unknown rather than guessing from a familiar prefix.
The same digits can outlive a provider
Consider a hypothetical number first assigned to Provider A, then ported to Provider B. The number string stays the same.
Initial allocation
Record available: Range → Provider A
Conclusion: Original allocation is A
After a port
Record available: The same old range record
Conclusion: A is still the historical allocation
Current service
Record available: Up-to-date authorised routing data required
Conclusion: B cannot be inferred from the old record
NumInfo has no current routing feed. Its examples must therefore leave current carrier unknown, rather than pretending that an allocation lookup is a live query.