bgpreport

Network · data from 2026-11-12

AS197398 ASTESMEDiA TES Media s.r.o.

Registry name: ASTESMEDiA TES Media s.r.o., SK · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS197398, 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.
46.151.56.0/23 No ROA Nonecovered by 46.151.56.0/22 1 0%low visibility 1
46.151.58.0/23 No ROA Nonecovered by 46.151.56.0/22 1 0%low visibility 1
46.151.60.0/23 No ROA Nonecovered by 46.151.60.0/22 1 0%low visibility 1
46.151.62.0/23 No ROA Nonecovered by 46.151.60.0/22 1 0%low visibility 1
46.151.56.0/22 No ROA RIR databaseRIPE 671 100% 66
46.151.60.0/22 No ROA RIR databaseRIPE 671 100% 66
46.151.61.0/24 No ROA RIR databaseRIPE 671 100% 66

AS-SET

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

  • ROA: none7
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: none46.151.56.0/23No ROA covers it. Add a ROA for AS197398, maxLength 23.1 of 673
Route object: none46.151.56.0/23No route object for it. A route object for 46.151.56.0/22 with origin AS197398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197398 in the RIR database for the space.1 of 673
ROA: none46.151.58.0/23No ROA covers it. Add a ROA for AS197398, maxLength 23.1 of 673
Route object: none46.151.58.0/23No route object for it. A route object for 46.151.56.0/22 with origin AS197398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197398 in the RIR database for the space.1 of 673
ROA: none46.151.60.0/23No ROA covers it. Add a ROA for AS197398, maxLength 23.1 of 673
Route object: none46.151.60.0/23No route object for it. A route object for 46.151.60.0/22 with origin AS197398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197398 in the RIR database for the space.1 of 673
ROA: none46.151.62.0/23No ROA covers it. Add a ROA for AS197398, maxLength 23.1 of 673
Route object: none46.151.62.0/23No route object for it. A route object for 46.151.60.0/22 with origin AS197398 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197398 in the RIR database for the space.1 of 673
ROA: none46.151.56.0/22No ROA covers it. Add a ROA for AS197398, maxLength 22.671 of 673
ROA: none46.151.60.0/22No ROA covers it. Add a ROA for AS197398, maxLength 22.671 of 673
ROA: none46.151.61.0/24No ROA covers it. Add a ROA for AS197398, maxLength 24.671 of 673

Route objects not announced

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