Network · data from 2026-11-12

AS212042 as-istqservers Stability for Integrated Server Hosting Ltd

Registry name: as-istqservers Stability for Integrated Server Hosting Ltd, JO · not in PeeringDB

8IPv4 routes 75.0% RPKI valid · 75.0% with a route object

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

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

Announced routes

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


203.32.25.0/24	Invalid: origin	Other origin only	5 1%low visibility	3
185.237.95.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
154.83.136.0/24	Valid	Other IRR onlyRADB	672 100%	67
31.58.140.0/24	Valid	RIR databaseRADB, RIPE	673 100%	67
217.74.17.0/24	Valid	RIR databaseRIPE	673 100%	66
45.87.29.0/24	Valid	RIR databaseRIPE	672 100%	66
45.150.95.0/24	Valid	RIR databaseRIPE	672 100%	66
31.57.130.0/24	Valid	RIR databaseRADB, RIPE	671 100%	68

203.32.25.0/24

Invalid: origin

Other origin only

5 1%low visibility

185.237.95.0/24

Invalid: origin

Other origin only

2 0%low visibility

154.83.136.0/24

Valid

Other IRR onlyRADB

672 100%

31.58.140.0/24

Valid

RIR databaseRADB, RIPE

673 100%

217.74.17.0/24

Valid

RIR databaseRIPE

673 100%

45.87.29.0/24

Valid

RIR databaseRIPE

672 100%

45.150.95.0/24

Valid

RIR databaseRIPE

672 100%

31.57.130.0/24

Valid

RIR databaseRADB, RIPE

671 100%

AS-SET

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

ROA: origin2
Route object: none2
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: origin	203.32.25.0/24	ROAs covering it name AS153393, not AS212042. If AS212042 should announce it, add a ROA for AS212042.	5 of 673
Route object: none	203.32.25.0/24	Route objects for it name AS153393. Add a route object with origin AS212042 in the RIR database for the space.	5 of 673
ROA: origin	185.237.95.0/24	ROAs covering it name AS57043, not AS212042. If AS212042 should announce it, add a ROA for AS212042.	2 of 673
Route object: none	185.237.95.0/24	Route objects for it name AS57043. Add a route object with origin AS212042 in the RIR database for the space.	2 of 673
Route object: RIR	154.83.136.0/24	Route object only in RADB. Add it in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

203.32.25.0/24

ROAs covering it name AS153393, not AS212042. If AS212042 should announce it, add a ROA for AS212042.

5 of 673

Route object: none

203.32.25.0/24

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

5 of 673

ROA: origin

185.237.95.0/24

ROAs covering it name AS57043, not AS212042. If AS212042 should announce it, add a ROA for AS212042.

2 of 673

Route object: none

185.237.95.0/24

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

2 of 673

Route object: RIR

154.83.136.0/24

Route object only in RADB. Add it in the RIR database for the space.

672 of 673

Route objects not announced

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