Network · data from 2026-11-12

AS200173 AGMail AdGuard Software Limited

Registry name: AGMail AdGuard Software Limited, CY · not in PeeringDB

7IPv4 routes 42.9% RPKI valid · 42.9% with a route object

0IPv6 routes

1RPKI invalid 1 origin · 0 maxLength

3No ROA 4 with no route object for this origin

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

0Route objects not announced registered with origin AS200173, seen from no peer

Announced routes

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


136.175.81.0/24	Invalid: origin	None	3 0%low visibility	3
23.26.10.0/24	No ROA	None	3 0%low visibility	3
134.195.11.0/24	No ROA	None	3 0%low visibility	3
172.111.57.0/24	No ROA	Other origin only	3 0%low visibility	3
179.254.99.0/24	Valid	RIR databaseRIPE	672 100%	66
216.238.38.0/24	Valid	RIR databaseARIN	670 100%	66
216.211.195.0/24	Valid	RIR databaseARIN	2 0%low visibility	2

136.175.81.0/24

Invalid: origin

None

3 0%low visibility

23.26.10.0/24

No ROA

None

3 0%low visibility

134.195.11.0/24

No ROA

None

3 0%low visibility

172.111.57.0/24

No ROA

Other origin only

3 0%low visibility

179.254.99.0/24

Valid

RIR databaseRIPE

672 100%

216.238.38.0/24

Valid

RIR databaseARIN

670 100%

216.211.195.0/24

Valid

RIR databaseARIN

2 0%low visibility

AS-SET

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

ROA: origin1
ROA: none3
Route object: none4

Change	Prefix or set	Detail	Full-table peers
ROA: origin	136.175.81.0/24	An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS200173 should announce it, add a ROA for AS200173.	3 of 673
Route object: none	136.175.81.0/24	No route object for it. Add a route object with origin AS200173 in the RIR database for the space.	3 of 673
ROA: none	23.26.10.0/24	No ROA covers it. Add a ROA for AS200173, maxLength 24.	3 of 673
Route object: none	23.26.10.0/24	No route object for it. Add a route object with origin AS200173 in the RIR database for the space.	3 of 673
ROA: none	134.195.11.0/24	No ROA covers it. Add a ROA for AS200173, maxLength 24.	3 of 673
Route object: none	134.195.11.0/24	No route object for it. Add a route object with origin AS200173 in the RIR database for the space.	3 of 673
ROA: none	172.111.57.0/24	No ROA covers it. Add a ROA for AS200173, maxLength 24.	3 of 673
Route object: none	172.111.57.0/24	Route objects for it name AS35916. Add a route object with origin AS200173 in the RIR database for the space.	3 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

136.175.81.0/24

An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS200173 should announce it, add a ROA for AS200173.

3 of 673

Route object: none

136.175.81.0/24

No route object for it. Add a route object with origin AS200173 in the RIR database for the space.

3 of 673

ROA: none

23.26.10.0/24

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

3 of 673

Route object: none

23.26.10.0/24

No route object for it. Add a route object with origin AS200173 in the RIR database for the space.

3 of 673

ROA: none

134.195.11.0/24

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

3 of 673

Route object: none

134.195.11.0/24

No route object for it. Add a route object with origin AS200173 in the RIR database for the space.

3 of 673

ROA: none

172.111.57.0/24

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

3 of 673

Route object: none

172.111.57.0/24

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

3 of 673

Route objects not announced

Every route object with origin AS200173 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.