Frequently Asked Questions

Jungle Labs provides ASN registration support, RIPE Sponsoring LIR services, IPv6 resource services, BGP announcement and implementation, RPKI/ROA assistance, RIPE Database administration and managed LIR support. The exact scope is confirmed in your order or service agreement.

Eligibility depends on the requested resource, the organisation's network use case and the RIPE policies in force at the time. Applicants normally need verifiable legal-entity details, authorised contacts and a genuine technical need within the RIPE NCC service region.

No. Final approval and assignment decisions are made by the RIPE NCC under the applicable policies. We review the information, prepare the request and coordinate questions, but no LIR can guarantee approval.

Typical requirements include current company-registration evidence, registered address, authorised representative details, administrative and technical contacts, an abuse contact, and technical information relevant to the request. Additional evidence may be requested during verification.

Verification helps confirm that the applicant is authorised to represent the organisation, protects Internet number resources from misuse, and supports RIPE policy, contractual, fraud-prevention and legal compliance requirements.

Send a short description of your organisation, required resources, intended network use and deployment region through our contact page. We will identify the appropriate service and any information needed before ordering.

Log in to the Jungle Labs client portal, choose the ASN service and provide the requested organisation, contact, upstream-network and routing-policy information. We review the submission before coordinating the request with RIPE NCC.

The request must demonstrate a routing need that cannot be met by using an upstream provider's ASN, commonly multihoming or a distinct external routing policy. RIPE NCC may request details of the external networks, their AS numbers and the planned BGP relationships.

Internet number resources are not property and are not sold. An ASN is registered for use by the approved organisation, subject to RIPE policy, accurate registration data and any applicable sponsorship or contractual requirements.

Timing varies with document completeness, technical complexity and RIPE NCC response times. A complete and consistent submission usually moves faster, but no fixed approval time can be guaranteed.

ASNs are normally assigned from the available pool and a particular number cannot usually be promised. Modern network equipment should support 32-bit ASNs; requests for a specific format remain subject to policy and availability.

Where RIPE policy permits, sponsorship can normally be moved to another qualified Sponsoring LIR through an administrative process. The resource holder must remain verified and continuous sponsorship should be arranged to avoid compliance issues.

Under a sponsoring service, Jungle Labs can maintain the relevant organisation, contact and routing-related records within the agreed scope. The End User remains responsible for providing accurate information and reporting changes promptly.

Prefix size depends on the selected service, documented need and current availability. A /48 is common for an organisation or site, while larger requirements require an addressing plan and separate confirmation before ordering.

This depends on the service agreement and routing arrangement. Where customer-originated BGP is supported, the origin ASN, LOA, route objects and ROA configuration must be agreed before announcement.

Processing begins after verification, cleared payment and technical approval. Timing depends on the requested records and third-party systems; the expected activation window is confirmed with your order rather than guaranteed in advance.

Possibly, but each cloud provider has different prefix-length, registration, LOA, RPKI and resource-holder requirements. Confirm the platform and region with us before ordering; compatibility with every BYOIP programme is not guaranteed.

Where technically and contractually applicable, we can assist with route objects, origin-AS records and ROA configuration. The authorised origin and maximum prefix length must match the approved routing plan.

Reverse DNS delegation may be available for eligible prefixes. Provide the authoritative name servers and ensure they are correctly configured before requesting an ip6.arpa delegation.

You must stop announcing and using the prefix by the termination date unless a written renewal or replacement arrangement is in place. Plan renumbering and DNS changes early to avoid disruption.

A Sponsoring LIR maintains the contractual and administrative relationship required for eligible independent Internet number resources used by an End User. It coordinates registration data and policy-related communication with RIPE NCC.

A direct RIPE NCC member operates its own LIR and manages membership obligations. Sponsorship lets an eligible End User maintain independent resources through an existing LIR without becoming a direct member.

New LIR Setup assists an organisation with establishing direct registry membership and its initial configuration. Managed LIR provides ongoing administrative support for an existing LIR, such as RIPE Database, RPKI and registry workflows. Resource eligibility remains policy-dependent.

Where the resource is eligible, we can review the registration and coordinate a sponsorship change. Proof of the resource holder, authorised signatory and current resource records is normally required.

A sponsorship change is primarily administrative and does not itself change your BGP sessions. However, route objects, RPKI, LOAs and maintainer permissions should be reviewed in advance to avoid operational problems.

RIPE NCC may contact the resource holder and require a valid contractual arrangement within the applicable process and deadline. Continued non-compliance can place the registration at risk, so replacement sponsorship should be arranged promptly.

The legal entity, address, authorised contacts, technical contacts, abuse contact and resource-use information must remain accurate. Material changes should be reported to the Sponsoring LIR without delay.

Support can cover common Cisco, Juniper, Arista, MikroTik, Fortinet and Ubiquiti platforms, as well as software routing stacks such as BIRD, FRRouting and VyOS. Compatibility is confirmed against your exact software and hardware version.

BGP announcement services may be available for approved resources and use cases. We confirm prefix ownership or authorisation, origin ASN, LOA, routing records, communities and location before activation.

Yes, subject to service availability and design review. Anycast projects require consistent announcements, health checking, traffic engineering and operational planning across all participating locations.

RPKI lets a resource holder authorise which ASN may originate a prefix. A Route Origin Authorisation helps networks validate route origin and reject invalid announcements, reducing the risk of accidental leaks and some forms of hijacking.

ROV configuration can be included in an agreed implementation scope. We review validator connectivity, policy for Valid/NotFound/Invalid routes and fail-safe behaviour before applying changes.

We can help design Remote Triggered Black Hole and traffic-engineering community policies when supported by the upstream provider. The exact community values and operational procedure must be confirmed with that provider.

Common causes include incorrect neighbour addresses or ASNs, authentication mismatch, ACL/firewall blocks, wrong source interface, missing multihop configuration, MTU problems or an upstream session that has not been provisioned. A troubleshooting engagement can review both configuration and packet-level evidence.

Use the secure Jungle Labs client portal to submit eligible orders, review invoices, access service information and open support requests.

The payment methods, billing currency and any applicable tax are displayed during checkout or on the invoice. Availability can vary by customer location and service type.

Many sponsorship, maintenance and resource services renew for an agreed term. The invoice and service agreement state the billing period, renewal date and notice requirements. Review these before completing payment.

An overdue service may be suspended or terminated in accordance with the agreement and applicable RIPE policy. Because resource-related services can affect registration or routing, contact support before the due date if you need assistance.

Cancellation and refund eligibility depend on the service stage, work already performed, third-party costs, the applicable service agreement and mandatory law. Submit the request through the client portal so the specific order can be reviewed.

Use the password-reset option on the portal login page. If you no longer control the registered email address, contact support; additional verification will be required before account access or contact information can be changed.

Open a support request in the client portal and describe the change. Legal-entity, ownership, address or authorised-contact changes may require updated registration documents and additional verification.