bgpreport

Network · data from 2026-11-12

AS57256 Pros-Services

Registry name: Pros Pros-Services S.A.R.L., LB · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57256, 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.176.146.0/24 Valid Other origin only 671 100% 67
89.187.216.0/24 Valid RIR databaseRIPE 671 100% 67
89.187.217.0/24 Valid RIR databaseRIPE 671 100% 67
89.187.218.0/24 Valid RIR databaseRIPE 671 100% 67
89.187.219.0/24 Valid RIR databaseRIPE 671 100% 67
89.187.220.0/24 Valid RIR databaseRIPE 671 100% 67
89.187.221.0/24 Valid RIR databaseRIPE 671 100% 67
89.187.222.0/24 Valid RIR databaseRIPE 671 100% 67
89.187.223.0/24 Valid RIR databaseRIPE 671 100% 67
185.176.145.0/24 Valid RIR databaseRIPE 671 100% 67
185.176.147.0/24 Valid RIR databaseRIPE 671 100% 67
185.176.144.0/24 Valid RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS57256'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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none185.176.146.0/24Route objects for it name AS56902. Add a route object with origin AS57256 in the RIR database for the space.671 of 673

Route objects not announced

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