bgpreport

Network · data from 2026-11-12

AS17886 MATRIXNETWORKS-AS-SG-AP - Matrix Networks Pte Ltd

Registry name: MATRIXNETWORKS-AS-SG-AP - Matrix Networks Pte Ltd, SG · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 50.0% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
6No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS17886, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17886, 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.114.0/24 No ROA Nonecovered by 115.146.114.0/23 673 100% 66
115.146.115.0/24 No ROA Nonecovered by 115.146.114.0/23 673 100% 66
2401:8400:9009::/48 No ROA Nonecovered by 2401:8400::/32 635 100% 69
2401:8400::/32 No ROA Other IRR onlyRADB 635 100% 69
115.146.112.0/24 No ROA RIR databaseAPNIC 673 100% 68
115.146.113.0/24 No ROA RIR databaseAPNIC 673 100% 68

AS-SET

AS17886 isn't in PeeringDB, where networks name their AS-SET.

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 12 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none115.146.114.0/24No ROA covers it. Add a ROA for AS17886, maxLength 24.673 of 673
Route object: none115.146.114.0/24No route object for it. A route object for 115.146.114.0/23 with origin AS17886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17886 in the RIR database for the space.673 of 673
ROA: none115.146.115.0/24No ROA covers it. Add a ROA for AS17886, maxLength 24.673 of 673
Route object: none115.146.115.0/24No route object for it. A route object for 115.146.114.0/23 with origin AS17886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17886 in the RIR database for the space.673 of 673
ROA: none2401:8400:9009::/48No ROA covers it. Add a ROA for AS17886, maxLength 48.635 of 636
Route object: none2401:8400:9009::/48No route object for it. A route object for 2401:8400::/32 with origin AS17886 covers it (filters allowing more-specifics accept it). Add a route object with origin AS17886 in the RIR database for the space.635 of 636
ROA: none2401:8400::/32No ROA covers it. Add a ROA for AS17886, maxLength 32.635 of 636
Route object: RIR2401:8400::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none115.146.112.0/24No ROA covers it. Add a ROA for AS17886, maxLength 24.673 of 673
ROA: none115.146.113.0/24No ROA covers it. Add a ROA for AS17886, maxLength 24.673 of 673

Route objects not announced

Route objects with origin AS17886 whose prefix no peer sees AS17886 announce. Many are kept on purpose (backup routes, space announced only in some places).

115.146.114.0/23APNICNo ROA
115.146.116.0/22APNICNo ROA

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.