bgpreport

Exchanges · data from 2026-11-12

BY-IX Belarusian Internet Exchange

Minsk, BY · members from IX Report (2026-11-12)

7Members 7 originate routes
33Their routes 97.0% RPKI valid · 97.0% with a route object
0RPKI invalid from 0 members
1No ROA 1 with no route object for their origin
2AS-SET includes own ASN 0 missing it · 2 not found · 1 none
4Route-server members 1 of their 23 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). 0 routes are RPKI invalid and 1 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.

AS50438Qline AS50438 no AS-SET in PeeringDB 3 0 1 1 33%

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

Members

Every member on IX Report's lists for BY-IX, with the routes it originates. Also as members.csv.

AS49711Flynet (AS49711) Yes 1110 v4 · 1 v6 100% 0 100% includes own ASN
AS57184KT MAZ LLC No 65 v4 · 1 v6 100% 0 100% not found
AS50929Advanced Technology Yes 55 v4 · 0 v6 100% 0 100% AS number only
AS60337MEDIATEK Yes 43 v4 · 1 v6 100% 0 100% AS number only
AS50438Qline Yes 33 v4 · 0 v6 67% 0 67% none in PeeringDB
AS43232TELEVID-AS16 No 21 v4 · 1 v6 100% 0 100% includes own ASN
AS59770KT MAZ No 21 v4 · 1 v6 100% 0 100% not found