bgpreport

Network · data from 2026-11-12

AS42186 AS-ITE_NET Kancelarija za informacione tehnologije i elektronsku upravu

Registry name: AS-ITE_NET Kancelarija za informacione tehnologije i elektronsku upravu, RS · not in PeeringDB

6IPv4 routes 0.0% RPKI valid · 33.3% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
6No ROA 4 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS42186, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42186, 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.
185.168.16.0/23 No ROA Other origin onlycovered by 185.168.16.0/22 673 100% 66
185.168.18.0/23 No ROA Other origin onlycovered by 185.168.16.0/22 673 100% 66
195.222.96.0/23 No ROA Other origin onlycovered by 195.222.96.0/22 673 100% 66
195.222.98.0/23 No ROA Other origin onlycovered by 195.222.96.0/22 670 100% 66
185.168.16.0/22 No ROA RIR databaseRIPE 673 100% 66
195.222.96.0/22 No ROA RIR databaseRIPE 673 100% 66

AS-SET

AS42186 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: none6
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none185.168.16.0/23No ROA covers it. Add a ROA for AS42186, maxLength 23.673 of 673
Route object: none185.168.16.0/23Route objects for it name AS198949. A route object for 185.168.16.0/22 with origin AS42186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42186 in the RIR database for the space.673 of 673
ROA: none185.168.18.0/23No ROA covers it. Add a ROA for AS42186, maxLength 23.673 of 673
Route object: none185.168.18.0/23Route objects for it name AS198949. A route object for 185.168.16.0/22 with origin AS42186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42186 in the RIR database for the space.673 of 673
ROA: none195.222.96.0/23No ROA covers it. Add a ROA for AS42186, maxLength 23.673 of 673
Route object: none195.222.96.0/23Route objects for it name AS198949. A route object for 195.222.96.0/22 with origin AS42186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42186 in the RIR database for the space.673 of 673
ROA: none195.222.98.0/23No ROA covers it. Add a ROA for AS42186, maxLength 23.670 of 673
Route object: none195.222.98.0/23Route objects for it name AS198949. A route object for 195.222.96.0/22 with origin AS42186 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42186 in the RIR database for the space.670 of 673
ROA: none185.168.16.0/22No ROA covers it. Add a ROA for AS42186, maxLength 22.673 of 673
ROA: none195.222.96.0/22No ROA covers it. Add a ROA for AS42186, maxLength 22.673 of 673

Route objects not announced

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