bgpreport

Network · data from 2026-11-12

AS55818 Matrix Cable International Exchange (MCIX)

Registry name: MCIX-AS-AP - MC-IX Matrix Internet Exchange RS-1, ID · PeeringDB

5IPv4 routes 80.0% RPKI valid · 80.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS55818, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55818, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
115.146.116.0/22 No ROA Other origin only 673 100% 69
2404:c000:4004::/47 Valid Other IRR onlyRADB 634 100% 69
2404:c000:4004::/48 Valid Other IRR onlyRADB 634 100% 69
119.110.115.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
119.110.116.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
119.110.118.0/24 Valid RIR databaseAPNIC, RADB 671 100% 68
119.110.116.0/23 Valid RIR databaseAPNIC, RADB 495 74% 64

AS-SET

PeeringDB's irr_as_set for AS55818: RADB::AS55818:AS-NAPINFO-MCIX. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS55818 isn't in the set, or no route object for AS55818 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS55818 in itNot covered
RADB::AS55818:AS-NAPINFO-MCIX RADBlists itself further down5 member sets in no database: AS-NTTNETID, AS-RAPDODGE, AS-RAPDODGE:AS-TABISNET, AS141126:AS-CUBIESPOT, AS150242:AS-KDN 532876,952 Yes 1

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 9 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: RIR2
  • AS-SET: missing member5
ChangePrefix or setDetailFull-table peers
ROA: none115.146.116.0/22No ROA covers it. Add a ROA for AS55818, maxLength 22.673 of 673
Route object: none115.146.116.0/22Route objects for it name AS17886. Add a route object with origin AS55818 in the RIR database for the space.673 of 673
Route object: RIR2404:c000:4004::/47Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2404:c000:4004::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
AS-SET: missing memberRADB::AS55818:AS-NAPINFO-MCIXAS55818:AS-NAPINFO-MCIX (RADB) lists AS-NTTNETID; no IRR database read has it.
AS-SET: missing memberRADB::AS55818:AS-NAPINFO-MCIXAS55818:AS-NAPINFO-MCIX (RADB) lists AS-RAPDODGE; no IRR database read has it.
AS-SET: missing memberRADB::AS55818:AS-NAPINFO-MCIXAS55818:AS-NAPINFO-MCIX (RADB) lists AS-RAPDODGE:AS-TABISNET; no IRR database read has it.
AS-SET: missing memberRADB::AS55818:AS-NAPINFO-MCIXAS55818:AS-NAPINFO-MCIX (RADB) lists AS141126:AS-CUBIESPOT; no IRR database read has it.
AS-SET: missing memberRADB::AS55818:AS-NAPINFO-MCIXAS55818:AS-NAPINFO-MCIX (RADB) lists AS150242:AS-KDN; no IRR database read has it.

Route objects not announced

Every route object with origin AS55818 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.