Network · data from 2026-11-12

AS17911 Brain Telecommunication

Registry name: BRAINPK-AS-AP - Brain Telecommunication Ltd., PK · PeeringDB

51IPv4 routes 96.1% RPKI valid · 98.0% with a route object

1IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

2No ROA 1 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

2Route objects not announced registered with origin AS17911, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS17911, 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.


103.100.188.0/24	No ROA	Other origin only	672 100%	67
203.128.24.0/24	No ROA	RIR databaseAPNIC, RADB	670 100%	68
122.129.82.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.128.3.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.128.4.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.128.8.0/24	Valid	RIR databaseAPNIC	673 100%	68
203.128.15.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.128.16.0/24	Valid	RIR databaseAPNIC	673 100%	68
203.128.17.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.128.19.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
203.128.23.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
122.129.64.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.66.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.69.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.72.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.73.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.74.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.75.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.76.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.77.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.78.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.79.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.80.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.81.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.84.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.85.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.89.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.90.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.91.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.92.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.93.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
122.129.94.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.5.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.6.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.7.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.9.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.11.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.12.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.13.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.14.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.18.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.20.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	68
203.128.21.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.22.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.25.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.26.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.27.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.28.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.31.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.128.0.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
203.128.1.0/24	Valid	RIR databaseAPNIC, RADB	671 100%	68
2400:4f00::/36	Valid	RIR databaseAPNIC, RADB	630 99%	67

AS-SET

AS17911's PeeringDB record names no 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 5 are in fix.csv.

ROA: none2
Route object: none1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: none	103.100.188.0/24	No ROA covers it. Add a ROA for AS17911, maxLength 24.	672 of 673
Route object: none	103.100.188.0/24	Route objects for it name AS38193. Add a route object with origin AS17911 in the RIR database for the space.	672 of 673
ROA: none	203.128.24.0/24	No ROA covers it. Add a ROA for AS17911, maxLength 24.	670 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

103.100.188.0/24

No ROA covers it. Add a ROA for AS17911, maxLength 24.

672 of 673

Route object: none

103.100.188.0/24

Route objects for it name AS38193. Add a route object with origin AS17911 in the RIR database for the space.

672 of 673

ROA: none

203.128.24.0/24

No ROA covers it. Add a ROA for AS17911, maxLength 24.

670 of 673

Route objects not announced

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


103.224.12.0/22	RADB	No ROA
203.128.0.0/19	APNIC, RADB	No ROA

103.224.12.0/22

RADB

No ROA

203.128.0.0/19

APNIC, RADB

No 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.