Network · data from 2026-11-12

AS198675 Intersvyaz-M-net Gelicon-Apple Limited liability company

Registry name: Intersvyaz-M-net Gelicon-Apple Limited liability company, RU · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 75.0% with a route object

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

0RPKI invalid 0 origin · 0 maxLength

6No ROA 1 with no route object for this origin

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

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

Announced routes

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


91.238.48.0/24	No ROA	Nonecovered by 91.238.48.0/23	673 100%	66
37.139.87.0/24	No ROA	RIR databaseRIPE	671 100%	68
91.238.48.0/23	No ROA	RIR databaseRIPE	671 100%	68
91.238.49.0/24	No ROA	RIR databaseRIPE	671 100%	68
2a03:cf40:100::/40	No ROA	RIR databaseRIPE	636 100%	69
2a03:cf40:100::/48	No ROA	RIR databaseRIPE	636 100%	69

AS-SET

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

ROA: none6
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: none	91.238.48.0/24	No ROA covers it. Add a ROA for AS198675, maxLength 24.	673 of 673
Route object: none	91.238.48.0/24	No route object for it. A route object for 91.238.48.0/23 with origin AS198675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198675 in the RIR database for the space.	673 of 673
ROA: none	37.139.87.0/24	No ROA covers it. Add a ROA for AS198675, maxLength 24.	671 of 673
ROA: none	91.238.48.0/23	No ROA covers it. Add a ROA for AS198675, maxLength 23.	671 of 673
ROA: none	91.238.49.0/24	No ROA covers it. Add a ROA for AS198675, maxLength 24.	671 of 673
ROA: none	2a03:cf40:100::/40	No ROA covers it. Add a ROA for AS198675, maxLength 40.	636 of 636
ROA: none	2a03:cf40:100::/48	No ROA covers it. Add a ROA for AS198675, maxLength 48.	636 of 636

Change

Prefix or set

Detail

Full-table peers

ROA: none

91.238.48.0/24

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

673 of 673

Route object: none

91.238.48.0/24

No route object for it. A route object for 91.238.48.0/23 with origin AS198675 covers it (filters allowing more-specifics accept it). Add a route object with origin AS198675 in the RIR database for the space.

673 of 673

ROA: none

37.139.87.0/24

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

671 of 673

ROA: none

91.238.48.0/23

No ROA covers it. Add a ROA for AS198675, maxLength 23.

671 of 673

ROA: none

91.238.49.0/24

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

671 of 673

ROA: none

2a03:cf40:100::/40

No ROA covers it. Add a ROA for AS198675, maxLength 40.

636 of 636

ROA: none

2a03:cf40:100::/48

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

636 of 636

Route objects not announced

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