bgpreport

Exchanges · data from 2026-11-12

Equinix Kuala Lumpur

Kuala Lumpur, MY · IX Report finds no sign this exchange is running · members from IX Report (2026-11-12)

2Members 1 originate routes
2,455Their routes 34.2% RPKI valid · 38.1% with a route object
653RPKI invalid from 1 members
963No ROA 1,519 with no route object for their origin
1AS-SET includes own ASN 0 missing it · 0 not found · 0 none
1Route-server members 1,457 of their 2,455 routes left out by an RPKI + IRR filter

Route servers: RPKI + IRR filtering

For each member on the route servers: of the routes it originates, how many a route server would leave out if it dropped RPKI-invalid routes and filtered on the IRR the way IXP route servers commonly build their prefix lists: the member's AS-SETs from PeeringDB (with none, its own AS number), expanded as bgpq4 does against whois.radb.net, with more-specifics of a route object accepted down to /24 and /48 (bgpq4 -A -R 24 / -R 48). 653 routes are RPKI invalid and 1,447 fail the IRR filter. Only each member's own routes are counted: the collectors show a route's origin, not which network it came through, so customers' routes aren't in these numbers. Route objects only in LEVEL3 or IDNIC (no public dump) count as missing.
AS15830Equinix as15830 RIPE::AS15830:AS-EQUINIX 2,455 653 1,447 1,457 59%

0 other route-server members would have every route they originate accepted.

Members

Every member on IX Report's lists for Equinix Kuala Lumpur, with the routes it originates. Also as members.csv.
AS15830Equinix as15830 Yes 2,4551,547 v4 · 908 v6 34% 653 38% includes own ASN
AS24115Equinix Internet Exchange - MLPE Route Servers No none seen