IP Address Tariffs are offered only for services hosted in Netinternet data center (single server hosting and cabinet rental). These tariffs are not valid for servers/infrastructures used outside the data center.

No. IP allocation is made in line with service type, usage scenario and fair management of address resources. The maximum number of IPs applicable for each package/service is specified in the service details.

Different subnet options are offered in the /29 to /22 range on the IPv4 side. The applicable subnet size is clarified based on the hosting model (single server/cabinet), topology and technical suitability.

IPv6 allocation is made according to the required addressing plan. Different prefix options can be evaluated for in-datacenter use. The minimum /48 prefix model applies to the portable IPv6 service and is tariffed separately.

The delivery and integration model is determined based on service type and topology. VLAN-based delivery, static routing or BGP integration options may be offered. When using BGP, IP block size, security filters and operational model are evaluated together.

Activation/announcement steps after IP allocation and basic operation processes are carried out with automation within the standard operating flow. The scope may vary according to the selected service model, routing method and requested topology.

Portable IP is a model that enables customers meeting certain conditions to announce their rented IP blocks (for IPv6 /48, for IPv4 /24) in different locations/operators. This product is tariffed separately from in-datacenter IP allocation tariffs.

The Portable IP service is evaluated for customers who have been receiving IP rental service from Netinternet for at least 12 months. Additionally, the location/operator to be announced, routing plan and relevant policy/technical eligibility conditions are taken into account.

Our ASN service is ASN allocation on behalf of your organization within RIPE NCC processes with Netinternet's LIR sponsorship. The operation of application, documentation, process tracking and preparation of required records/objects is carried out by Netinternet. The ASN is allocated on behalf of the institution.

In case your institution becomes a LIR in the future, the transfer of the ASN to your own LIR account can be evaluated within the framework of RIPE NCC policy and eligibility conditions. The process is planned according to the requested transfer model.

Depending on request; management of RIPE database objects (e.g. inetnum/inet6num, route/route6, aut-num, mntner), contact/role records, operational updates and process coordination can be provided. The scope is clarified according to your institution's current structure and operating model.

Information such as the required number of IPs/subnet, hosting model (single server/cabinet), routing preference (VLAN/static/BGP), devices to be used and security policies (ACL/filtering) is requested. With this information, the appropriate subnet plan and delivery model is determined.

The process consists of needs analysis, clarification of the IP plan, determination of the delivery/routing method and activation steps. If there are additional components such as BGP/ASN, documentation and process management steps are also added. Net timing may vary depending on topology and process scope.

Yes. You can request rDNS (PTR) record for your allocated IPv4/IPv6 addresses. The rDNS record can be critical for email delivery (mail reputation), reverse DNS verification and some security checks. In the request; the relevant IP/prefix, target PTR name (FQDN) and domain ownership information for verification may be requested.

Abuse notifications are handled as a priority for the reputation of IP blocks and network security. In complaints originating from spam, DDoS, botnet, port scanning, phishing or malicious content; the notification is recorded, traffic/flow/log checks are performed and the customer is quickly informed. In critical situations, temporary restrictions may be applied to the relevant IP to protect network security. The permanent solution is planned together according to the source of the incident (server security, application, email configuration, outbound filtering, etc.).

Yes. In the L2 delivery model over VLAN, a VLAN can deliver maximum 256 IPv4 addresses (in practice /24) or 1 IPv6 /64 per VLAN. For larger IPv4 blocks (/23, /22 etc.) or wider IPv6 prefix needs; according to topology static routing (L3) or BGP routing should be preferred. The appropriate method is determined considering your current router architecture, security filters and operation model.