bgpreport

Network · data from 2026-11-12

AS48473 TOWERCOM-SK-AS Towercom a.s.

Registry name: TOWERCOM-SK-AS Towercom a.s., SK · not in PeeringDB

6IPv4 routes 16.7% RPKI valid · 33.3% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
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
1Route objects not announced registered with origin AS48473, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48473, 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.14.116.0/24 No ROA Nonecovered by 185.14.116.0/22 671 100% 66
185.14.117.0/24 No ROA Nonecovered by 185.14.116.0/22 671 100% 66
185.14.118.0/24 No ROA Nonecovered by 185.14.116.0/22 671 100% 66
185.14.119.0/24 No ROA Nonecovered by 185.14.116.0/22 671 100% 66
91.209.247.0/24 No ROA RIR databaseRIPE 668 99% 68
2a03:aac0::/32 No ROA RIR databaseRIPE 635 100% 67
85.248.152.0/22 Valid RIR databaseRIPE 671 100% 66

AS-SET

AS48473 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: none6
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.14.116.0/24No ROA covers it. Add a ROA for AS48473, maxLength 24.671 of 673
Route object: none185.14.116.0/24No route object for it. A route object for 185.14.116.0/22 with origin AS48473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48473 in the RIR database for the space.671 of 673
ROA: none185.14.117.0/24No ROA covers it. Add a ROA for AS48473, maxLength 24.671 of 673
Route object: none185.14.117.0/24No route object for it. A route object for 185.14.116.0/22 with origin AS48473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48473 in the RIR database for the space.671 of 673
ROA: none185.14.118.0/24No ROA covers it. Add a ROA for AS48473, maxLength 24.671 of 673
Route object: none185.14.118.0/24No route object for it. A route object for 185.14.116.0/22 with origin AS48473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48473 in the RIR database for the space.671 of 673
ROA: none185.14.119.0/24No ROA covers it. Add a ROA for AS48473, maxLength 24.671 of 673
Route object: none185.14.119.0/24No route object for it. A route object for 185.14.116.0/22 with origin AS48473 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48473 in the RIR database for the space.671 of 673
ROA: none91.209.247.0/24No ROA covers it. Add a ROA for AS48473, maxLength 24.668 of 673
ROA: none2a03:aac0::/32No ROA covers it. Add a ROA for AS48473, maxLength 32.635 of 636

Route objects not announced

Route objects with origin AS48473 whose prefix no peer sees AS48473 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.14.116.0/22RIPENo ROA

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.