ASN standard product · Application-based IPv4 /24 · Other requirements assessed individually
ASN sponsorship follows a standardized delivery path. IPv4 /24 leasing has public term pricing and an application path; IPv6, PI resources, RIR transfers, and other registry requirements receive an individual review.
A clear, verifiable delivery path for eligible applicants who require ASN, IPv4, or IPv6 resource services.
Apply for a /24 resource with public quarterly and annual pricing. Use rights, term, IP reputation, abuse workflow, and the scope of route, ROA, and LOA work are recorded in the Order for each case. The agreement can cover, including but not limited to, reverse DNS, Geofeed, location records, Anycast, multiple origins, technical changes, and support.
Confirm before ordering
The standard service covers the published route/route6 and PA-prefix ROA responsibilities for the covered standard product. Registry records, technical changes, and support can be added through a written Order.
RIPE NCC operates the database. Customers maintain their own Access, organisation, contact, and maintainer records; SKNK provides setup guidance, handles the sponsoring-LIR side of the application and resource-registration coordination, and maintains the covered prefix's route/route6 object.
SKNK prepares, submits, and follows up on the application. RIPE NCC independently decides under its policies whether to make the assignment, which is made to the approved End User.
The standard service includes creating and continuously maintaining the covered prefix's IRR route/route6 object. AS-SET follows the actual filtering need and available maintainer authority; IRR work for other resources follows each resource's scope.
Customers choose upstreams, configure and operate BGP, and announce the prefix with the authorized origin ASN. SKNK does not provide BGP configuration, transit, or managed routing.
For a PA /48 from SKNK's LIR address space, SKNK controls RPKI authority and creates, maintains, or withdraws the ROA. Contact SKNK before changing the intended origin ASN; customers cannot modify this ROA themselves in the RIPE Portal.
Reverse DNS, Geofeed, location records, Anycast, multiple origins, technical changes, implementation coordination, and support can be agreed for the applicable resource and operating model.
Tell us the upstream's IRR source, exact-match, and Origin ASN requirements before the route is announced. We will confirm the covered prefix, resource authorization, and any custom registry, technical-change, or support scope in the Order.
Areas open for enquiry
These areas follow an application-based review. Availability, eligibility, pricing, and scope are confirmed after the request is reviewed.
IPv6 address-space and deployment requirements beyond the standard ASN package.
EnquireSponsorship, maintenance, or transfer assessment for existing IPv4 Provider Independent resources.
EnquireSponsorship and application paths for eligible organizations requiring independent IPv6 space.
EnquireRegional or inter-RIR resource transfers where the registered resource holder changes.
EnquireMove the sponsorship of an existing ASN or PI resource while the End User remains the resource holder.
EnquireIndividually assessed coordination for an IPv4 or IPv6 prefix changing Origin ASN, including only the approved ROA, IRR, LoA, and upstream steps.
EnquireA starting point for special requirements that do not fit a standard service or one of the listed workflows.
EnquireAssessment and quotation
Describe your organization, existing resources, target region, and intended use. SKNK will confirm the applicable scope and provide a written scope and quotation before paid work begins.
