对等互联政策

最后更新:November 19, 2026

此页面目前仅提供英文版本。

In short: Pacswitch welcomes settlement-free peering with networks that operate responsibly, keep accurate routing records and run a 24×7 NOC.

1. Our networks

CompanyPacswitch Globe Telecom Limited
Autonomous systemsAS10136, AS55536
Regional registryAPNIC
Main exchangeHKIX (Hong Kong Internet Exchange)
Peering policySelective, settlement-free
Peering contact[email protected]

Please check our PeeringDB records for current exchange points, IP addresses and prefix counts.

2. Requirements

To peer with Pacswitch, a network should:

  • have a publicly routable ASN and a complete, up-to-date PeeringDB record;
  • run a 24×7 NOC that can respond to operational and security issues;
  • register all announced prefixes in an IRR (for example APNIC, RIPE or RADB) and publish valid RPKI ROAs;
  • follow the MANRS routing security actions;
  • support IPv4 and IPv6 where available;
  • have enough traffic exchange to justify the session, at our discretion.

3. Technical rules

  • Sessions use BGP-4 with MD5 or TCP-AO authentication where supported.
  • Announce only your own prefixes and those of your customers, consistent with your IRR and RPKI data.
  • Do not announce bogons, private addresses or prefixes longer than /24 (IPv4) or /48 (IPv6).
  • Do not point a default route or static routes at Pacswitch, and do not transit our network for third parties.
  • Set sensible maximum-prefix limits; we filter by IRR and drop RPKI-invalid routes.
  • Keep traffic ratios reasonable and upgrade capacity before ports become congested.
  • Private network interconnects (PNIs) are available in shared facilities for large traffic volumes.

4. Operations and security

Both parties should notify planned maintenance in advance and respond quickly to abuse, DDoS and route-leak reports. Routing incidents can be reported to [email protected] at any time.

5. Changes and termination

Pacswitch may update this policy, decline a request or end a peering session, for example after repeated breaches of these rules, with reasonable notice except in an urgent security situation.

6. Request peering

Email [email protected] with your ASN, PeeringDB link, exchange points or facilities, expected traffic and NOC contact details.