bgpreport

Network · data from 2026-11-12

AS42742 INTERKAMSERVICE-AS InterkamService LLC

Registry name: INTERKAMSERVICE-AS InterkamService LLC, RU · not in PeeringDB

13IPv4 routes 84.6% RPKI valid · 84.6% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS42742, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS42742, 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.206.12.0/24 No ROA Other origin only 1 0%low visibility 2
91.203.44.0/22 No ROA RIR databaseRIPE 673 100% 67
78.157.254.0/23 Valid Nonecovered by 78.157.224.0/19 3 0%low visibility 4
78.157.253.0/24 Valid RIR databaseRIPE 673 100% 67
194.79.4.0/22 Valid RIR databaseRIPE 673 100% 67
195.211.64.0/22 Valid RIR databaseRIPE 673 100% 67
78.157.224.0/19 Valid RIR databaseRIPE 672 100% 67
91.189.232.0/21 Valid RIR databaseRIPE 672 100% 67
92.118.140.0/24 Valid RIR databaseRIPE 672 100% 67
92.118.141.0/24 Valid RIR databaseRIPE 672 100% 67
92.118.142.0/24 Valid RIR databaseRIPE 672 100% 67
185.211.164.0/22 Valid RIR databaseRIPE 672 100% 67
188.191.0.0/20 Valid RIR databaseRIPE 672 100% 67
2a09:ad40::/29 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

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

  • ROA: none2
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none91.206.12.0/24No ROA covers it. Add a ROA for AS42742, maxLength 24.1 of 673
Route object: none91.206.12.0/24Route objects for it name AS47375. Add a route object with origin AS42742 in the RIR database for the space.1 of 673
ROA: none91.203.44.0/22No ROA covers it. Add a ROA for AS42742, maxLength 22.673 of 673
Route object: none78.157.254.0/23No route object for it. A route object for 78.157.224.0/19 with origin AS42742 covers it (filters allowing more-specifics accept it). Add a route object with origin AS42742 in the RIR database for the space.3 of 673

Route objects not announced

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