SKNK Field Notes · Point by point
Routing identity, BGP configuration, incident response, and network-change dependencies define the operational ownership model.
Reviewed against public documentation: 2 August 2026
Compare point by point
Option one · Own ASN and external routing policy
Your organisation uses its own ASN or another documented routing identity.
Option two · Provider-managed routing
The provider supplies the routing identity within its documented service scope.
Option one · Own ASN and external routing policy
Your team configures and operates BGP with compatible upstreams.
Option two · Provider-managed routing
The provider runs the routing service inside its stated scope.
Option one · Own ASN and external routing policy
Your organisation defines the target policy within upstream acceptance and filtering conditions.
Option two · Provider-managed routing
The provider's product and policy set the available announcements and changes.
Option one · Own ASN and external routing policy
Your team owns configuration, monitoring, incident response, and coordination.
Option two · Provider-managed routing
The provider's published service boundary and agreement allocate responsibility.
Where this model fits
An own-ASN model fits networks that need to define an external routing policy across compatible upstreams.
Provider-managed routing fits a documented service boundary where the provider carries routing work.
Confirmation items before an application or change
Routing identity portability at service end
Upstream acceptance of the planned prefix and origin ASN
Operational changes caused by new upstreams, prefix changes, or service exit
Policies, resource relationships, service boundaries, and upstream filters vary by situation. Formal pages and the responsible party confirm price, eligibility, ownership, and service-end arrangements.
SKNK · Sources and scope
Each source supports one kind of conclusion. Source pages, registry records, and routing observations update at different times, so read every result with its source and timestamp.
Registry and IRR records
Useful for checking
Whether a public object exists for this ASN or prefix, who it is registered to, and who maintains it.
Needs a separate check
Live BGP observations show the current announcement state.
Current service boundaries
Useful for checking
What SKNK publicly states about BGP and network-operations responsibility.
Needs a separate check
Each upstream provides its own acceptance and filtering policy.
