Lombok-IX

Become Member

Ready to Peer? A Guide to Connecting with LOMBOK-IX

  • Membership Costs and Levels

    LOMBOK-IX provides scalable, high-performance interconnection services with port capacities ranging from 1G to 100G. Our flexible port options allow members to start with the capacity they need today and scale effortlessly for future demands. To ensure maximum resilience and throughput, we offer full support for Link Aggregation (LAG).

  • Become Member LOMBOK-IX

    To ensure a stable, secure, and professional peering environment, all prospective members are required to meet the following criteria:

    • Autonomous System Number (ASN) You must have a public and officially registered Autonomous System Number (ASN).

    • IP Prefixes You are required to have at least one public IPv4 prefix and one public IPv6 prefix.

    • 24×7 Network Operations Center (NOC) You must operate a Network Operations Center (NOC) that is reachable 24/7 to handle technical and operational issues.

    • BGP Knowledge You must have a clear routing policy and the technical expertise to manage Border Gateway Protocol (BGP) peering sessions.

    • Physical Connectivity You must have the capability to establish a physical connection (cross-connect) to the LOMBOK-IX fabric at one of our points of presence.

    • Acceptable Use Policy All members must agree to our terms of service and use the LOMBOK-IX infrastructure responsibly, respecting all other members and partners.

  • Steps for Connecting

    Connecting to the LOMBOK-IX peering fabric is a straightforward process. Here are the steps to get started:

    1. Review Our Requirements Ensure you have reviewed and can meet all the technical and logistical prerequisites outlined in our Peering Requirements page.

    2. Submit Your Application Complete and submit the official application form available on our Join Us page. Our team will review your submission and contact you to coordinate the next steps.

    3. Establish Physical Connection & IP Allocation Once your application is approved, you will establish the physical cross-connect to our switch. LOMBOK-IX will then allocate your IPv4 and IPv6 peering addresses. Please note: new connections may be placed in a temporary quarantine VLAN for initial testing.

    4. Configure BGP Sessions With the connection live, you can configure your BGP sessions with our route servers and establish any required direct peering sessions with other members.

    5. Begin Exchanging Traffic Once your BGP sessions are active and stable, you can start exchanging traffic with the LOMBOK-IX community. Welcome and happy peering!

Lombok-IX

Server Room Access Policy

Regulations Inside the Data Center

  • Purpose

    The purpose of this policy is to establish standard operating procedures and access controls for the data center facility to ensure the comprehensive security of its physical assets, data, and overall infrastructure.

  • Scope

    This policy applies to all individuals requiring access to the data center facility, including but not limited to:

    1. All Employees (Permanent and Contract)

    2. Vendors

    3. Partners

    4. Any other third party with authorized technical purposes.

  • Definitions

    1. Data Center: A centralized facility housing network infrastructure, including servers, storage systems, networking equipment, and other supporting hardware.

    2. Restricted Access: An area that may only be entered by specifically authorized personnel.

    3. Access Log Book: A physical or digital record used to document the entry and exit of all personnel to and from a restricted area.

  • Supporting Resources

    To support a secure and documented access process, the following resources and equipment will be utilized:

    1. Access Cards (RFID)

    2. Data Center Access Request Forms

    3. Visitor IDs or Temporary Badges

    4. CCTV Surveillance and Automated Door Control Systems

    5. Access Log Books (Physical or Electronic)

Access Request Procedure

No Prosedure Keterangan
1

Submitting an Access Request

Access requests must be submitted by the user (both internal and external) through one of the following channels:

  • Official Form: By filling out the provided Data Center Access Request Form.

  • Internal Ticketing System: By creating a request ticket through the designated system.

Submission Deadlines:

  • Routine/Internal Access: A minimum of D-1 (one business day) prior to the visit.

  • Vendor/Third-Party Access: A minimum of D-3 (three business days) prior to the visit.
2

Required Account Information

Each request must include the following contact information for the responsible party:

  1. ID Card of the Owner/Customer

  2. Contact Phone Number of the Owner/Customer

  3. Name of the Technical Lead

  4. Phone Number of the Technical Lead

  5. Name of the Finance Lead

  6. Phone Number of the Finance Lead

Note: If the contact details are the same as the owner’s, the fields can be filled with the customer’s name and contact information accordingly.
3 Details of Attending Personnel

The personnel who will be entering the Data Center must provide the following details:

  1. Full Name

  2. ID Number (KTP/NIP) and Company of Origin

  3. Purpose of the Visit

  4. Planned Date and Time of Access

  5. Estimated Duration of Access

  6. List of Equipment Being Brought In (using a separate form that includes Device Name, Serial Number, and Quantity).
4 Authorization and Approval

All requests will be reviewed and approved by authorized personnel. Approval will be granted in the form of:

  • An Access Code (for internal personnel).

  • Official confirmation via email, WhatsApp, or a signature on the request form (for external parties).

Data Center Entry Procedure

No Prosedure Keterangan
1

Check-in Process at Reception / Security Post

As part of the initial procedure, all personnel must undergo a verification process at the reception or security area, which includes:

  1. Verification of official identification (ID Card/Driver’s License/Company ID).

  2. Recording personal details in the Access Log Book.

  3. Submission of the approved access permit.

  4. An inspection of all carried items to be checked against the approved list, such as:

    • Laptops

    • USB Drives

    • Cameras

    • Toolbox
2 Escort and Supervision

  1. Vendors or any external parties are required to be escorted and supervised at all times by a designated internal staff member (PIC).

  2. External personnel are not permitted to enter the Data Center unaccompanied.

Regulations Inside the Data Center

No Prosedure Keterangan
1 No Food or Drinks Allowed

To prevent equipment damage and maintain the cleanliness of the data center, food and beverages are strictly prohibited.
2 Footwear Must Be Removed

To prevent dirt, dust, and other particles from entering the highly sensitive environment and to minimize the risk of static electricity.
3 All Activities Must Be Logged

All actions performed must be recorded in the operational log, including the name of the personnel, time, and a description of the activity.
4

Accessing Other Racks/Servers is Prohibited

Personnel are restricted to accessing only their designated racks. Accessing racks belonging to other parties is forbidden without prior authorization or an official work order from the equipment owner.
5 No Equipment May Be Left Behind

All items brought into the data center must be brought out upon exit, unless the equipment has been granted prior approval for permanent installation in a rack.
6 Maintain Cleanliness and Order

All cabling and connection panels must be left in a tidy and organized manner without disrupting or damaging the access or equipment of other tenants in the facility.

Data Center Exit Procedure

No Prosedure Keterangan
1 Data Center Exit Procedure

Upon completing all activities, personnel must follow the check-out process, which includes:

  1. Security personnel will log the official exit time.

  2. An inspection of all equipment will be conducted to ensure all items are accounted for.

  3. All access cards or temporary badges must be returned to security personnel.
2 Activity Reporting

Following a visit, the designated internal escort (PIC) is required to complete a brief report.

  1. The report must include daily access data: company name, personnel names, activities performed, and timestamps.

  2. The final status of the activity (e.g., completed or pending) must be clearly noted.
3 Monitoring and Auditing

  1. The facility is monitored by 24/7 CCTV surveillance.

  2. All surveillance recordings are securely stored for a minimum period of 90 days.

  3. Periodic access audits will be conducted by the designated security team.

Violations and Sanctions

No Prosedure Keterangan
1 Minor

Failure to properly sign the access log.

  • A formal verbal warning will be issued. 
2 Moderate

Entering the facility without a valid or authorized access permit. 

  • A written warning will be issued, and the individual may be blacklisted from future access. 
3 Severe

Theft, property damage, or any act of sabotage within the Data Center. 

  • Immediate termination of contract/employment and/or legal action will be pursued.
Lombok-IX

Route Server

Route Server Platform

To simplify the peering process, LOMBOK-IX operates a sophisticated and redundant route server platform, compliant with RFC7947 standards.

How It Works

The route server acts as a central BGP route exchange. Instead of establishing separate BGP sessions with every member, you only need to configure a single session with our route servers. Once connected, you will automatically receive the BGP announcements from all other members who are also peered with the platform.

Key Benefits

  • Efficiency: Drastically reduce the number of BGP sessions you need to manage, simplifying your configuration and saving router resources.

  • Redundancy: We operate two identical, redundant route servers at each of our locations to ensure maximum uptime and reliability.

  • Full Control: You retain complete control over your routing policy. Use BGP communities to manage which peers your prefixes are announced (or not announced) to via the route servers. On your end, you can also apply filter lists to decide which prefixes to accept from the route servers.

Utilizing our route server platform makes peering at LOMBOK-IX easier, faster, and more efficient.

  • Route Server Guides for the exchanges

    This document provides the technical guides and parameters required to connect to the LOMBOK-IX route server platform.

    Blackholing Route Server

    In addition to our conventional route servers for prefix exchange, LOMBOK-IX also operates a dedicated Blackholing Route Server. This platform is designed specifically to distribute BGP announcements that are tagged for Blackholing, an effective method for mitigating large-scale DDoS attacks.

    For more details on its operation and implementation, please refer to our Blackholing Guide.

    BGP Session Parameters

    Below is a summary of the BGP session parameters you will need to connect to our route server platforms, for both conventional and Blackholing route servers.

    (You can then continue with a table or list of technical parameters such as ASN, IP Address, etc.)

  • How and what the route servers filters

    Important: IRR Filtering Policy

    To maintain network integrity, LOMBOK-IX automatically updates its filters from IRR databases every hour. All members are required to register their IP prefixes in a valid IRR database at least 24 hours prior to announcing them on our platform to avoid rejection.

  • Bogon and Martian filtering

    To maintain the integrity and stability of our peering fabric, LOMBOK-IX implements a strict route filtering policy. All members are required to ensure their BGP announcements adhere to the following rules. Prefixes that violate these policies will be rejected by our route servers.

    Members must not announce routes that:

    1. Violate Prefix Length Restrictions (RFC7454)

    • IPv4: Prefixes must be between /8 and /24 in length. Announcements for prefixes more specific than /24 or less specific than /8 will be dropped.

    • IPv6: Prefixes must be between /19 and /48 in length. Announcements for prefixes more specific than /48 or less specific than /19 will be dropped.

    2. Contain Bogon or Martian Addresses

    • Announcements must not include private or reserved IP prefixes as defined by IETF standards (RFC 1918, RFC 5735, RFC 6598, etc.).

    3. Contain Bogon ASNs

    • The BGP AS_PATH must not contain private or reserved Autonomous System Numbers as defined by IETF standards (RFC 6996, RFC 7300, etc.).

Download Server Room Access Policy