1. Scope
This policy applies to the IP address assignments, ASN (autonomous system number) sponsorship and BGP session services provided by the service provider whose details appear below ("Smart Host", "we"). It forms part of the Terms of Service and of the relevant service contract.
For a description of the services, see the IP addresses, ASN and BGP pages.
Smart Host. For company details see the contact page.
2. Definitions
The following terms are used in this policy:
- RIPE NCC: the regional internet registry that manages internet number resources for Europe, the Middle East and parts of Central Asia.
- LIR: a local internet registry, that is a member of RIPE NCC. Smart Host is a LIR.
- Sponsorship: the registration of an organisation’s resource, such as an ASN, with RIPE NCC through a LIR and under that LIR’s responsibility.
- Resource: an IP address block (prefix) or an ASN.
- RIPE Database: the public registry database in which resources and their responsible contacts are published.
3. RIPE NCC rules
Resources are subject to the RIPE NCC policies in force and to the contract terms that bind us as a LIR. These rules are published on the RIPE NCC website. The customer agrees to comply with them.
If this policy conflicts with the RIPE NCC rules, the RIPE NCC rules prevail. When the RIPE NCC rules change, we may make the changes needed to keep the service compliant; we will tell you about them.
The registration or transfer of a resource depends on a decision of RIPE NCC; we do not guarantee that decision.
4. Eligibility and identity verification
Identity verification (KYC) is required for IP address and ASN services. We usually ask for: a company incorporation document or equivalent and a tax certificate, the ID or passport of the authorised signatory, a recent proof of address, and a summary of the routing policy. The final list is given when you apply and may change with RIPE NCC requirements.
Payment is by bank transfer only. The service is not provided until verification is complete. We reserve the right to refuse a request or ask for further documents. For individual requests, contact us through the Contact page.
5. IPv6 assignments
IPv6 prefixes are assigned from our block, which is registered to our company at RIPE NCC. The prefix size is agreed when you request it. The assignment is registered in the RIPE Database in the customer’s name, and management of the reverse DNS (PTR) records is delegated to the customer. [network team to confirm the assignment model (registration in the customer’s name, size range)]
Assignments from our block are tied to the service and cannot be moved to another provider. When the service ends the prefix is returned to us.
6. IPv4 leasing
IPv4 address leasing is not offered at present. This section will be updated when the service opens. Leasing IPv4 addresses gives no ownership right over them; no guarantee is given about the reputation (blocklist status) of an address. [confirm the source of the IPv4 space and the right to re-lease it]
7. ASN sponsorship
As the sponsoring LIR, we file the ASN request with RIPE NCC on your behalf and follow the process with you. The ASN is registered in the RIPE Database in the customer’s name. Sponsorship is annual and renews each year; we send a reminder before renewal.
Timelines are approximate and depend on how RIPE NCC works. If sponsorship ends or is not renewed, then within the RIPE NCC rules the ASN may be transferred to another sponsoring LIR or returned. [the period and transfer/return procedure that applies when sponsorship ends]
8. BGP sessions
To open a BGP session you need: your own ASN, your own prefixes (at least a /24 for IPv4 or a /48 for IPv6), a valid RPKI ROA, and route/route6 objects in an IRR database. The minimum prefix sizes follow the common rule on the public internet and may change.
We validate the prefixes you announce; we do not accept, or we withdraw, announcements that appear invalid, unowned or unauthorised. Session types and the details of the routing policy are announced before the service opens. [network team to confirm the routing policy and session types]
9. Registry data and accuracy
The RIPE Database is public. The customer agrees to keep the name, address, email address and phone number that appear in the records accurate and up to date, and to maintain a working abuse contact. The customer accepts that this information will be published in the RIPE Database; for details see the Privacy and KVKK Notice (Aydınlatma Metni).
The customer is responsible for the consequences of inaccurate or outdated information.
10. Use of resources
The use of resources is subject to the Acceptable Use Policy. In particular it is prohibited to announce prefixes that are not yours (BGP hijacking), to spoof IP addresses, or to send unsolicited bulk messages or attack traffic from these resources.
If the security of the network or of third parties requires it, we may withdraw an announcement, block traffic or close a session. The customer is responsible for responding to abuse reports about the resources in good time.
11. Fees, term and renewal
Current fees are shown on the service pages and at order time; this text contains no prices. Sponsorship is billed annually. If payment is not made, the service may be suspended and sponsorship may not be renewed; an additional grace period of 7 days applies after the due date, after which the service is suspended, and if payment is not made within 30 days of the suspension date, the service is terminated.
Refund after the request has been filed with RIPE NCC: [refund rule after filing]. For consumer rights see the Cancellation and Refund Policy.
12. End of service
When the service ends, the customer stops announcing and using the prefixes assigned from our block; these prefixes are returned to us. For the customer’s own resources (for example its own ASN), a move to another sponsoring LIR can be requested to the extent the RIPE NCC rules allow. Notice period and fee for the move: [notice period and fee for a move].
13. Liability
We are not responsible for decisions, delays or rule changes of RIPE NCC, or for the network policies of third parties (for example other networks’ filtering or blocklist decisions). The limit of our liability is set out in the Terms of Service: [limitation of liability (lawyer)]. Mandatory provisions of law are reserved.
14. Changes and contact
We may update this policy; we announce material changes before they take effect. Notice period: at least 30 days. For questions, use the Contact page.