01 / BGP
Bilateral & multilateral
Peering can be bilateral or through the route server according to participant requirements and policies.
SDCT / PANDA-IX
Connect locally.
Route efficiently.
Panda Internet Exchange (PANDA-IX) provides a local interconnection point in Semarang for networks to exchange traffic directly through peering.
LOCAL PEERING · SEMARANG
Bring networks closer.
Exchange traffic locally.
PANDA-IX brings networks together in a local interconnection ecosystem in Semarang. Local peering can provide more direct traffic paths depending on destination networks, routing policies and traffic patterns.
Network ANetwork BNetwork C
PANDA-IXSEMARANG
Local traffic exchange
Interconnection illustration, not an actual topologyNETWORK INFORMATION
Core information for
your network team.
The details below are public PANDA-IX network details. Port, VLAN, session addresses and activation details are confirmed during onboarding.
- Route Server ASN
- AS154034
- IPv4 Allocation
- 165.101.31.0/24
- IPv6 Allocation
- 2001:df5:c140::/48
02 / DUAL STACK
IPv4 & IPv6
PANDA-IX supports peering for IPv4 and IPv6. Session parameters are confirmed at activation.
03 / ROUTE SERVER
Simplified peering
The route server helps participants establish multilateral peering without creating a bilateral session with every member.
04 / PUBLIC TOOLS
Visibility & troubleshooting
Looking Glass and public traffic statistics support routing observation and exchange visibility.
PUBLIC NETWORK TOOLS
Explore PANDA-IX
from the network side.
Use these public sources to review PANDA-IX information and prepare for peering.
HOW TO CONNECT
From your ASN
to an active BGP session.
The PANDA-IX team coordinates administrative and technical steps before activation. Keep your network information ready and up to date.
Start a peering request ↗Prepare network information
ASN, technical contacts, prefixes to announce and required device information.
Update PeeringDB
Keep your network profile and peering information current for smoother validation and configuration.
Coordinate connectivity
Choose the connection method to PANDA-IX and confirm interconnection availability with SDCT/PANDA-IX.
Activate & test BGP
Session parameters are provided during onboarding, and routing is tested before activation is completed.
PEERING POLICY
Clear rules
for interconnection.
PANDA-IX public policy covers bilateral and multilateral peering, prefix announcement through the route server and maintaining current network information in PeeringDB.
Bilateral & multilateral peering
Participants may use bilateral BGP sessions or multilateral peering. Session suitability and technical parameters are confirmed during activation.
Prefix announcement
Prefixes to be announced should be communicated to PANDA-IX. Selective advertisement or special routing requirements are coordinated with the peering team.
PeeringDB
PANDA-IX uses PeeringDB information in peering operations. Participants should keep ASN and network profile information accurate before activation.
Advanced route control
Advanced route-server policies, including BGP Large Communities, are published through PANDA-IX technical channels or PeeringDB and should be confirmed before use.
FAQ
Before you connect.
Do I need my own ASN?
BGP peering requires an appropriate network identity. Contact PANDA-IX to confirm technical requirements before onboarding.
Does PANDA-IX support IPv6?
Yes. Public PANDA-IX information includes IPv4 and IPv6 support. Session details are provided at activation.
Do all networks automatically exchange traffic?
No. Traffic exchange depends on BGP sessions, each network's peering policy, route-server participation and bilateral agreements where used.
How can I review routes before peering?
Use the public PANDA-IX Looking Glass to review available routing information, then coordinate further technical requirements with the peering team.
PANDA-IX · SEMARANG