bgpreport

Network · data from 2026-11-12

AS197667 FEROMEDIA

Registry name: FEROMEDIA-AS Telekom System sp.z o.o., PL · PeeringDB

7IPv4 routes 85.7% RPKI valid · 42.9% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
3No 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 AS197667, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS197667, 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.
194.5.244.0/22 No ROA RIR databaseRIPE 671 100% 68
2a07:13c0::/29 No ROA RIR databaseRIPE 633 100% 67
2a0c:e940::/29 No ROA RIR databaseRIPE 633 100% 67
31.41.82.0/24 Valid Nonecovered by 31.41.80.0/21 156 23% 46
185.139.41.0/24 Valid Nonecovered by 185.139.40.0/22 156 23% 46
185.139.42.0/24 Valid Nonecovered by 185.139.40.0/22 156 23% 46
185.139.43.0/24 Valid Nonecovered by 185.139.40.0/22 156 23% 46
31.41.80.0/21 Valid RIR databaseRIPE 671 100% 68
185.139.40.0/22 Valid RIR databaseRIPE 671 100% 68

AS-SET

AS197667's PeeringDB record names no 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 8 are in fix.csv.

  • ROA: none3
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none194.5.244.0/22No ROA covers it. Add a ROA for AS197667, maxLength 22.671 of 673
ROA: none2a07:13c0::/29No ROA covers it. Add a ROA for AS197667, maxLength 29.633 of 636
ROA: none2a0c:e940::/29No ROA covers it. Add a ROA for AS197667, maxLength 29.633 of 636
Route object: none31.41.82.0/24No route object for it. A route object for 31.41.80.0/21 with origin AS197667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197667 in the RIR database for the space.156 of 673
Route object: none185.139.41.0/24No route object for it. A route object for 185.139.40.0/22 with origin AS197667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197667 in the RIR database for the space.156 of 673
Route object: none185.139.42.0/24No route object for it. A route object for 185.139.40.0/22 with origin AS197667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197667 in the RIR database for the space.156 of 673
Route object: none185.139.43.0/24No route object for it. A route object for 185.139.40.0/22 with origin AS197667 covers it (filters allowing more-specifics accept it). Add a route object with origin AS197667 in the RIR database for the space.156 of 673

Route objects not announced

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

2a10:f781:10:ef0b::/64RIPENo 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.