Network · data from 2026-11-12

AS198154 parsabr Pars Abr Toseeh Ertebatat LTD

Registry name: parsabr Pars Abr Toseeh Ertebatat LTD, IR · not in PeeringDB

23IPv4 routes 100.0% RPKI valid · 100.0% with a route object

3IPv6 routes 0.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

3No ROA 0 with no route object for this origin

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

7Route objects not announced registered with origin AS198154, seen from no peer

Announced routes

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


2a05:9080::/48	No ROA	RIR databaseRIPE	632 99%	68
2a05:9080:7::/48	No ROA	RIR databaseRIPE	632 99%	68
2a05:9080:10::/48	No ROA	RIR databaseRIPE	632 99%	68
5.57.38.0/24	Valid	RIR databaseRIPE	671 100%	66
5.160.110.0/24	Valid	RIR databaseRIPE	671 100%	66
5.160.144.0/24	Valid	RIR databaseRIPE	671 100%	66
5.160.198.0/24	Valid	RIR databaseRIPE	671 100%	66
81.12.32.0/24	Valid	RIR databaseRIPE	671 100%	66
81.12.33.0/24	Valid	RIR databaseRIPE	671 100%	66
81.12.34.0/24	Valid	RIR databaseRIPE	671 100%	66
81.12.35.0/24	Valid	RIR databaseRIPE	671 100%	66
81.12.46.0/24	Valid	RIR databaseRIPE	671 100%	66
81.12.83.0/24	Valid	RIR databaseRIPE	671 100%	66
85.133.195.0/24	Valid	RIR databaseRIPE	671 100%	66
85.133.230.0/24	Valid	RIR databaseRIPE	671 100%	66
87.236.38.0/24	Valid	RIR databaseRIPE	671 100%	66
185.215.231.0/24	Valid	RIR databaseRIPE	671 100%	66
37.32.47.0/24	Valid	RIR databaseRIPE	669 99%	67
81.12.80.0/24	Valid	RIR databaseRIPE	669 99%	67
85.133.221.0/24	Valid	RIR databaseRIPE	669 99%	66
85.133.225.0/24	Valid	RIR databaseRIPE	669 99%	66
85.133.248.0/24	Valid	RIR databaseRIPE	669 99%	66
85.133.250.0/24	Valid	RIR databaseRIPE	669 99%	66
89.44.242.0/24	Valid	RIR databaseRIPE	669 99%	66
91.239.192.0/24	Valid	RIR databaseRIPE	669 99%	66
178.239.145.0/24	Valid	RIR databaseRIPE	669 99%	66

AS-SET

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

ROA: none3
Route object: not announced7

Change	Prefix or set	Detail	Full-table peers
ROA: none	2a05:9080::/48	No ROA covers it. Add a ROA for AS198154, maxLength 48.	632 of 636
ROA: none	2a05:9080:7::/48	No ROA covers it. Add a ROA for AS198154, maxLength 48.	632 of 636
ROA: none	2a05:9080:10::/48	No ROA covers it. Add a ROA for AS198154, maxLength 48.	632 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

2a05:9080::/48

No ROA covers it. Add a ROA for AS198154, maxLength 48.

632 of 636

ROA: none

2a05:9080:7::/48

No ROA covers it. Add a ROA for AS198154, maxLength 48.

632 of 636

ROA: none

2a05:9080:10::/48

No ROA covers it. Add a ROA for AS198154, maxLength 48.

632 of 636

Route objects not announced

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


5.160.144.0/23	RIPE	Invalid: origin
45.135.195.0/24	RIPE	Valid
185.42.214.0/24	RIPE	Invalid: origin
185.42.215.0/24	RIPE	Valid
2a05:9080:4::/48	RIPE	No ROA
2a14:2340::/48	RIPE	No ROA
2a14:23c0::/48	RIPE	No ROA

5.160.144.0/23

RIPE

Invalid: origin

45.135.195.0/24

RIPE

Valid

185.42.214.0/24

RIPE

Invalid: origin

185.42.215.0/24

RIPE

Valid

2a05:9080:4::/48

RIPE

No ROA

2a14:2340::/48

RIPE

No ROA

2a14:23c0::/48

RIPE

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.