Network · data from 2026-11-12

AS135523 Multinet Broadband

Registry name: MULTINET-IE-AS-AP - Multinet Broadband, PK · PeeringDB

28IPv4 routes 92.9% RPKI valid · 96.4% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

2No ROA 1 with no route object for this origin

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

3Route objects not announced registered with origin AS135523, seen from no peer

Announced routes

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


202.55.128.0/22	No ROA	Other origin only	670 100%	67
103.152.255.0/24	No ROA	RIR databaseAPNIC, RADB	672 100%	67
115.167.72.0/24	Valid	RIR databaseAPNIC	672 100%	67
115.167.74.0/24	Valid	RIR databaseAPNIC	672 100%	67
115.167.75.0/24	Valid	RIR databaseAPNIC	672 100%	67
202.92.18.0/24	Valid	RIR databaseAPNIC	672 100%	67
202.92.19.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.151.27.0/24	Valid	RIR databaseAPNIC	671 100%	67
125.209.66.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.69.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.71.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.72.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.81.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.83.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.90.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.117.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.119.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.141.230.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.141.236.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.141.244.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.141.251.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.142.178.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.142.181.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.142.183.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.142.190.0/24	Valid	RIR databaseAPNIC	670 100%	66
202.142.191.0/24	Valid	RIR databaseAPNIC	670 100%	66
125.209.84.0/24	Valid	RIR databaseAPNIC	669 99%	67
111.92.157.0/24	Valid	RIR databaseAPNIC	4 1%low visibility	3

202.55.128.0/22

No ROA

Other origin only

670 100%

103.152.255.0/24

No ROA

RIR databaseAPNIC, RADB

672 100%

115.167.72.0/24

Valid

RIR databaseAPNIC

672 100%

115.167.74.0/24

Valid

RIR databaseAPNIC

672 100%

115.167.75.0/24

Valid

RIR databaseAPNIC

672 100%

202.92.18.0/24

Valid

RIR databaseAPNIC

672 100%

202.92.19.0/24

Valid

RIR databaseAPNIC

672 100%

103.151.27.0/24

Valid

RIR databaseAPNIC

671 100%

125.209.66.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.69.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.71.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.72.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.81.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.83.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.90.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.117.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.119.0/24

Valid

RIR databaseAPNIC

670 100%

202.141.230.0/24

Valid

RIR databaseAPNIC

670 100%

202.141.236.0/24

Valid

RIR databaseAPNIC

670 100%

202.141.244.0/24

Valid

RIR databaseAPNIC

670 100%

202.141.251.0/24

Valid

RIR databaseAPNIC

670 100%

202.142.178.0/24

Valid

RIR databaseAPNIC

670 100%

202.142.181.0/24

Valid

RIR databaseAPNIC

670 100%

202.142.183.0/24

Valid

RIR databaseAPNIC

670 100%

202.142.190.0/24

Valid

RIR databaseAPNIC

670 100%

202.142.191.0/24

Valid

RIR databaseAPNIC

670 100%

125.209.84.0/24

Valid

RIR databaseAPNIC

669 99%

111.92.157.0/24

Valid

RIR databaseAPNIC

4 1%low visibility

AS-SET

AS135523'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 6 are in fix.csv.

ROA: none2
Route object: none1
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
ROA: none	202.55.128.0/22	No ROA covers it. Add a ROA for AS135523, maxLength 22.	670 of 673
Route object: none	202.55.128.0/22	Route objects for it name AS9260, AS17557, AS23966, AS38193, AS45605, AS55714. Add a route object with origin AS135523 in the RIR database for the space.	670 of 673
ROA: none	103.152.255.0/24	No ROA covers it. Add a ROA for AS135523, maxLength 24.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

202.55.128.0/22

No ROA covers it. Add a ROA for AS135523, maxLength 22.

670 of 673

Route object: none

202.55.128.0/22

Route objects for it name AS9260, AS17557, AS23966, AS38193, AS45605, AS55714. Add a route object with origin AS135523 in the RIR database for the space.

670 of 673

ROA: none

103.152.255.0/24

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

672 of 673

Route objects not announced

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


103.70.251.0/24	APNIC	Valid
125.209.92.0/24	APNIC	Valid
125.209.93.0/24	APNIC	Valid

103.70.251.0/24

APNIC

Valid

125.209.92.0/24

APNIC

Valid

125.209.93.0/24

APNIC

Valid

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.