Release Notes
Getting started
DE-CIX Access
Overview and technical specifications
Create a new Access or LAG
Monitor your Access
Delete your Access
GlobePEER
Overview GlobePEER
Create your GlobePEER service
Manage your GlobePEER service
Upgrading / downgrading capacity
Change your MAC address
Monitor your traffic
DE-CIX Jakarta – IPv4 Peering LAN Renumbering FAQ
Delete your GlobePEER service
Blackholing Services
Route Service
Route Server Guides
DE-CIX ASEAN GlobePEER Route Server Guide
DE-CIX Barcelona GlobePEER Route Server Guide
DE-CIX Chicago GlobePEER Route Server Guide
DE-CIX Copenhagen GlobePEER Route Server Guide
DE-CIX Dallas GlobePEER Route Server Guide
DE-CIX Dusseldorf GlobePEER Route Server Guide
DE-CIX Esbjerg GlobePEER Route Server Guide
DE-CIX Frankfurt GlobePEER Route Server Guide
DE-CIX Hamburg GlobePEER Route Server Guide
DE-CIX Helsinki GlobePEER Route Server Guide
DE-CIX Houston GlobePEER Route Server Guide
DE-CIX Istanbul GlobePEER Route Server Guide
DE-CIX Jakarta GlobePEER Route Server Guide
DE-CIX Kuala Lumpur GlobePEER Route Server Guide
DE-CIX Kristiansand GlobePEER Route Server Guide
DE-CIX Leipzig GlobePEER Route Server Guide
DE-CIX Lisbon GlobePEER Route Server Guide
DE-CIX Madrid GlobePEER Route Server Guide
DE-CIX Malaysia GlobePEER Route Server Guide
DE-CIX Marseille GlobePEER Route Server Guide
DE-CIX Mexico GlobePEER Route Server Guide
DE-CIX Munich GlobePEER Route Server Guide
DE-CIX New York GlobePEER Route Server Guide
DE-CIX Oslo GlobePEER Route Server Guide
DE-CIX Palermo GlobePEER Route Server Guide
DE-CIX Phoenix GlobePEER Route Server Guide
DE-CIX Richmond GlobePEER Route Server Guide
ACIX GlobePEER Route Server Guide
AF-CIX GlobePEER Route Server Guide
AqabaIX GlobePEER Route Server Guide
Borneo-IX GlobePEER Route Server Guide
IRAQ-IXP Route Server Guide
PIE Karachi GlobePEER Route Server Guide
Penang IX Route Server Guide
Ruhr-CIX GlobePEER Route Server Guide
SEECIX GlobePEER Route Server Guide
UAE-IX GlobePEER Route Server Guide
DE-CIX Sao Paulo GlobePEER Route Server Guide
Doha IX Route Server Guide
DE-CIX Rio De Janeiro GlobePEER Route Server Guide
Action BGP Communities (Route Server Control)
DE-CIX GlobePEER Route Server Action BGP Communities
ACIX GlobePEER Route Server Action BGP Communities
AF-CIX GlobePEER Route Server Action BGP Communities
AqabaIX GlobePEER Route Server Action BGP Communities
Borneo-IX GlobePEER Route Server Action BGP Communities
IRAQ-IXP Route Server Action BGP Communities
PIE Karachi GlobePEER Route Server Action BGP Communities
Ruhr-CIX GlobePEER Route Server Action BGP Communities
SEECIX GlobePEER Route Server Action BGP Communities
UAE-IX GlobePEER Route Server Action BGP Communities
Doha IX Route Server Action BGP Communities
Informational BGP Communities (Route Details)
DE-CIX GlobePEER Route Server Informational BGP Communities
ACIX GlobePEER Route Server Informational BGP Communities
AF-CIX GlobePEER Route Server Informational BGP Communities
AqabaIX GlobePEEER Route Server Informational BGP Communities
Borneo-IX GlobePEER Route Server Informational BGP Communities
IRAQ-IXP Route Server Informational BGP Communities
PIE Karachi GlobePEER Route Server Informational BGP Communities
Ruhr-CIX GlobePEER Route Server Informational BGP Communities
SEECIX GlobePEER Route Server Informational BGP Communities
UAE-IX GlobePEER Route Server Informational BGP Communities
Doha IX Route Server Informational BGP Communities
Looking Glass Guides
DE-CIX GlobePEER Looking Glass Guide
ACIX GlobePEER Looking Glass Guide
AF-CIX GlobePEER Looking Glass Guide
AqabaIX GlobePEER Looking Glass Guide
Borneo-IX GlobePEER Looking Glass Guide
IRAQ-IXP Looking Glass Guide
PIE Karachi Looking Glass Guide
Ruhr-CIX GlobePEER Looking Glass Guide
SEECIX GlobePEER Looking Glass Guide
UAE-IX GlobePEER Looking Glass Guide
Doha IX Looking Glass Guide
Notes on additional Routes (incl. Google VPP) via GlobePEER Route Service
DirectCLOUD
Overview and Monitoring
Cloud Connections
DirectCLOUD for Microsoft Azure
Create DirectCLOUD Connection for Azure
How to order a DirectCLOUD connection for Azure
Create or upgrade Gateways for your Azure ExpressRoute
Manage your Azure Cloud Connection
Upgrade / downgrade a DirectCLOUD service for Azure
Change DirectCLOUD configurations for Azure
Delete DirectCLOUD configurations for Azure
Monitoring Azure ExpressRoute uptime
Monitor your connection
Updating the Cloud Key for Your Azure DirectCLOUD Service
Delete your Azure Cloud connection
FAQ DirectCLOUD for Microsoft Azure
DirectCLOUD for AWS
Create DirectCLOUD connection for AWS
Manage your DirectCLOUD connection for AWS
Upgrade / downgrade the connection
Change DirectCLOUD configurations for AWS
Delete DirectCLOUD configurations for AWS
Monitoring AWS DirectConnect uptime
Monitor your connection
Delete your AWS Cloud connection
DirectCLOUD for IBM
Create DirectCLOUD connection for IBM
Manage your DirectCLOUD connection for IBM
Upgrade / downgrade a DirectCLOUD service for IBM
Change DirectCLOUD configurations for IBM
Delete DirectCLOUD configurations for IBM
Monitor your connection
Delete your IBM Cloud connection
DirectCLOUD for GCloud
Cloud ROUTER
Overview Cloud ROUTER
Create / Manage your Cloud ROUTER
Create / Manage the configurations
Add a configuration
Upgrade / downgrade a configuration
Change your Cloud ROUTER configurations
Monitor your configurations
Delete a Cloud ROUTER configuration
Prefix Lists & Policies in Cloud ROUTER
VirtualPNI
Overview VirtualPNI
Create your VirtualPNI
Order and configure your VirtualPNI between two Accesses
Order and configure your VirtualPNI between Access and Cloud ROUTER
Manage your VirtualPNI
Upgrade / Downgrade your VirtualPNI service
Change VirtualPNI configurations
Delete VirtualPNI configurations
Monitor your VirtualPNI
Delete your VirtualPNI service
Colocation
Out-of-band access to your DE-CIX colocated equipment
Shipping Information
Colocation equipment management for Digital Realty data centers
API
Overview IX-API
Cloud ROUTER API
Cloud ROUTER Postman Collection
Monitor and Visibility of Learned Routes and Advertised Routes by API
BGP Ingress and Egress Filters Usage by API
Quick API Reference
Service Insights System
Service Insights System - Tutorial
Standard customer Service Insights Tutorial (for customers without reselling services or DaaS location)
Service Telemetry Insights Tutorial
GlobePEER Traffic Insights Tutorial
GlobePEER Threat Insights Tutorial
Cloud ROUTER Traffic Insights Tutorial
Reseller Service Insights Tutorial
Reseller GlobePEER Traffic Insights Tutorial
Reseller GlobePEER Threat Insights Tutorial
Reseller Service Telemetry Insights Tutorial
Partner (DaaS) Service Insights Tutorial
Partner GlobePEER Traffic Insights Tutorial
Partner Service Telemetry Insights Tutorial
Partner GlobePEER Threat Insights Tutorial
Service Insights Tutorial - General Informations
Service Insights System
Account administration
Add new users or subcustomers
Manage user roles and permissions
Multi-Factor-Authentification
Retrieving username and reset password
Delete a user
Customer service and ticket system
Table of Contents
- All Categories
- GlobePEER
- Manage your GlobePEER service
- DE-CIX Jakarta – IPv4 Peering LAN Renumbering FAQ
DE-CIX Jakarta – IPv4 Peering LAN Renumbering FAQ
Updated
by Peter Hahn
This article provides answers to frequently asked questions (FAQs) regarding the IPv4 peering LAN renumbering for Jakarta. English version
Artikel ini berisi jawaban atas pertanyaan yang sering diajukan (FAQ) seputar penomoran ulang LAN peering IPv4 di Jakarta. Versi bahasa Indonesia
Versi bahasa Indonesia
DE-CIX Jakarta terus berkembang! Sejak peluncuran kami, lebih dari 120 jaringan telah bergabung dengan peering LAN kami. Ruang IPv4 kami kini hampir penuh, sehingga kami harus memperluas jaringan untuk memastikan pertumbuhan berkelanjutan dan onboarding peer baru.
Kami akan pindah ke IPv4 peering LAN yang lebih besar. Ini berarti semua pelanggan perlu memperbarui konfigurasi IPv4 mereka di platform DE-CIX Jakarta.
FAQ ini menjelaskan mengapa kami melakukan perubahan, kapan perubahan akan terjadi, dan bagaimana cara mempersiapkannya.
Mengapa?
Mengapa kita harus melakukan penomoran ulang?
- IPv4 peering LAN saat ini adalah jaringan /25 (126 alamat IPv4 yang dapat digunakan).
- Setiap anggota DE-CIX Jakarta menerima satu alamat IPv4 untuk antarmuka router mereka.
- Saat ini hanya tersisa beberapa alamat IPv4.
- Memperluas jaringan memastikan kami dapat terus menghubungkan pelanggan baru tanpa penundaan.
Kapan?
Kapan perubahan akan dilakukan?
Jendela perubahan: 23–25 September 2025 (Selasa–Kamis). Waktu pemeliharaan yang tepat akan dikomunikasikan mendekati tanggal tersebut.
Apa yang terjadi jika saya melewati tenggat waktu?
Anda akan kehilangan peering IPv4 di DE-CIX Jakarta hingga Anda memperbarui konfigurasi dengan alamat IP dan netmask baru.
Bisakah tanggal diubah?
Tidak. Kami harus membebaskan ruang untuk pelanggan baru. Menunda akan menghambat koneksi baru dan membatasi potensi pertumbuhan semua pihak.
Bisakah saya melakukan perubahan sebelum jendela resmi?
Ya, tetapi Anda tidak dapat melakukan peering dengan pelanggan lain yang belum beralih. Perubahan lebih awal akan membuat Anda sementara tanpa peering IPv4.
Kapan route server akan berubah?
- 23 September 2025: Dua route server baru akan aktif dengan alamat IPv4 baru, dan satu alamat IPv4 route server lama akan dimatikan.
- 25 September 2025: Pada akhir periode perubahan, alamat IPv4 route server lama terakhir akan dihapus.
Bagaimana?
Apakah sesi BGP saya akan terputus?
Ya. Sesi BGP akan terputus selama perubahan. Sesi akan kembali setelah re-konfigurasi selesai.
Apa saja yang harus saya ubah?
- Perbarui alamat IPv4 antarmuka dan netmask.
- Perbarui semua alamat IPv4 BGP neighbor (termasuk route server dan direct peers).
- Perbarui access list, prefix filter, atau aturan firewall yang merujuk subnet lama.
- Verifikasi sistem monitoring, automasi, atau NMS yang menyimpan IP lama.
Apa alamat IP baru saya?
Anda akan menerimanya langsung dari tim dukungan DE-CIX sebelum jendela perubahan.
Jika saya memiliki dua router, apakah harus diubah bersamaan?
Tidak harus paralel, tetapi keduanya harus diubah dalam jendela perubahan.
Bagaimana cara menguji apakah perubahan berhasil?
Setelah re-konfigurasi, sesi BGP Anda dengan route server harus dapat kembali terbentuk dengan sukses.
Apakah saya perlu memberi tahu DE-CIX setelah selesai?
Tidak wajib, tetapi disarankan untuk konfirmasi agar tidak terjadi salah paham.
Saya sudah melakukan perubahan, tapi BGP tidak kembali. Apa yang harus dilakukan?
Periksa filter, ACL, dan route map Anda. Pastikan mereka mengizinkan peering LAN baru.
Apakah IPv6 juga perlu diubah?
Tidak. Alamat IPv6 tetap sama.
Bisakah saya tetap peering dengan pelanggan yang belum berubah?
Anda dapat sementara mempertahankan IPv4 lama sebagai secondary IP dan menjaga sesi BGP lama, tetapi tidak disarankan — sesi ini sering terlupakan dan dapat menimbulkan kebingungan.
Saya terkoneksi secara remote (GlobePEER Remote Service atau melalui reseller). Apakah saya juga perlu mengubah?
Ya. Jika Anda memiliki antarmuka di DE-CIX Jakarta IPv4 peering LAN, Anda harus memperbaruinya.
- Rencanakan jendela perubahan lebih awal – hindari perubahan mendadak di menit terakhir.
- Dokumentasikan konfigurasi lama agar bisa rollback jika diperlukan saat pengujian.
- Informasikan NOC Anda dan tim automasi lebih awal.
- Jadwalkan koordinasi dengan peers jika Anda memiliki sesi BGP langsung dengan pelanggan lain.
Dukungan
Jika pertanyaan Anda tidak terjawab di sini, jangan ragu untuk menghubungi layanan pelanggan kami. Kami senang membantu!
English Version
DE-CIX Jakarta is growing! Since our launch, over 120 networks have joined our peering LAN. Our IPv4 space is now nearly full, and we must expand the network to ensure continued growth and on-boarding of new peers.
We’re moving to a larger IPv4 peering LAN. This means all customers will need to update their IPv4 configuration on the DE-CIX Jakarta platform.
This FAQ explains why we’re making the change, when it will happen, and how to prepare.
Why?
Why do we have to renumber?
- The current IPv4 peering LAN is a /25 network (126 usable IPv4 addresses).
- Every DE-CIX Jakarta member receives one IPv4 address for their router interface.
- We have only a few IPv4 addresses left.
- Expanding the network ensures we can continue connecting new customers without delay.
When?
When will the change happen?
Change window: 23–25 (Tuesday–Thursday) September 2025. Exact maintenance times will be communicated closer to the date.
What happens if I miss the deadline?
You will lose IPv4 peering at DE-CIX Jakarta until you update your configuration to the new IP address and netmask.
Can we change the dates?
No. We must free up space for new customers. Postponing would block new connections and limit everyone’s growth potential.
Can I change before the official window?
Yes, but you won’t be able to peer with other customers who have not yet switched. Early changes will leave you temporarily without IPv4 peering.
When will route servers change?
- 23 September 2025: Two new route servers will become live with new IPv4 addresses configured, and one old route server IPv4 address will be switched off.
- 25 September 2025: At the end of the change period we will remove the last old IPv4 route server address.
How?
Will my BGP sessions drop?
Yes. BGP sessions will drop during the change. They will come back after you complete the reconfiguration.
What exactly do I need to change?
- Update your interface IPv4 address and netmask.
- Update all BGP neighbor IPv4 addresses (including route servers and direct peers).
- Update any access lists, prefix filters, or firewall rules referencing the old subnet.
- Verify any monitoring, automation, or NMS systems that store the old IP.
What will my new IP address be?
You will receive it directly from DE-CIX support before the change window.
If I have two routers, do I change both at once?
Not in parallel, but both must be changed during the change window.
How can I test if my change worked?
After reconfiguration, your BGP sessions with route servers should re-establish successfully.
Do I need to notify DE-CIX when I’m done?
Not required, but recommended to confirm and avoid misunderstandings.
I made the change, but BGP isn’t coming back. What now?
Check your filters, ACLs, and route maps. Ensure they allow the new peering LAN.
Do I need to change IPv6?
No. IPv6 addressing remains unchanged.
Can I still peer with customers who haven’t changed yet?
You may temporarily keep the old IPv4 as a secondary IP and maintain old BGP sessions, but we do not recommend this — these sessions are often forgotten and can cause confusion.
I connect remotely (GlobePEER Remote Service or via a reseller). Do I also need to change?
Yes. If you have an interface in the DE-CIX Jakarta IPv4 peering LAN, you must update it.
- Plan your change window early – avoid last-minute edits.
- Document your old config so you can revert if needed during testing.
- Inform your NOC and any automation systems teams ahead of time.
- Schedule peer coordination if you have direct BGP sessions with other customers.
Support
If your question is not covered here, do not hesitate to contact our customer service. We are happy to help!