bgpreport

Network · data from 2026-11-12

AS203765 PRONETEUS Sp. z o.o.

Registry name: ASN-PRONETEUS PRONETEUS Sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS203765, 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.124.118.75/32 No ROA Nonecovered by 185.124.118.0/23 7 1%low visibility 11
185.124.118.194/32 No ROA Nonecovered by 185.124.118.0/23 7 1%low visibility 11
91.210.238.0/24 No ROA RIR databaseRIPE 671 100% 68
185.124.116.0/22 No ROA RIR databaseRIPE 671 100% 68
2a06:b1c0::/29 No ROA RIR databaseRIPE 635 100% 67
185.124.116.0/23 No ROA RIR databaseRIPE 22 3%low visibility 23
185.124.118.0/23 No ROA RIR databaseRIPE 22 3%low visibility 23

AS-SET

AS203765'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 10 are in fix.csv.

  • ROA: none7
  • Route object: none2
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none185.124.118.75/32No ROA covers it. Add a ROA for AS203765, maxLength 32.7 of 673
Route object: none185.124.118.75/32No route object for it. A route object for 185.124.118.0/23 with origin AS203765 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203765 in the RIR database for the space.7 of 673
ROA: none185.124.118.194/32No ROA covers it. Add a ROA for AS203765, maxLength 32.7 of 673
Route object: none185.124.118.194/32No route object for it. A route object for 185.124.118.0/23 with origin AS203765 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS203765 in the RIR database for the space.7 of 673
ROA: none91.210.238.0/24No ROA covers it. Add a ROA for AS203765, maxLength 24.671 of 673
ROA: none185.124.116.0/22No ROA covers it. Add a ROA for AS203765, maxLength 22.671 of 673
ROA: none2a06:b1c0::/29No ROA covers it. Add a ROA for AS203765, maxLength 29.635 of 636
ROA: none185.124.116.0/23No ROA covers it. Add a ROA for AS203765, maxLength 23.22 of 673
ROA: none185.124.118.0/23No ROA covers it. Add a ROA for AS203765, maxLength 23.22 of 673

Route objects not announced

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

2a10:f781:10:3af::/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.