bgpreport

Network · data from 2026-11-12

AS271835 Fiber Pro

Registry name: AS271835 - P Y D TELECOM S.R.L., PE · PeeringDB

10IPv4 routes 80.0% RPKI valid · 40.0% with a route object
6IPv6 routes 100.0% RPKI valid · 16.7% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No ROA 11 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS271835, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271835, 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.

8.243.115.160/27 No ROA None 2 0%low visibility 2
204.199.170.32/27 No ROA None 2 0%low visibility 2
181.233.27.0/24 Valid Nonecovered by 181.233.24.0/22 672 100% 67
181.233.25.0/24 Valid Nonecovered by 181.233.24.0/22 671 100% 67
181.233.26.0/24 Valid Nonecovered by 181.233.24.0/22 671 100% 67
181.233.24.0/24 Valid Nonecovered by 181.233.24.0/22 670 100% 67
2803:1810:3000::/44 Valid Nonecovered by 2803:1810::/32 636 100% 67
2803:1810:f010::/44 Valid Nonecovered by 2803:1810::/32 636 100% 67
2803:1810:f020::/44 Valid Nonecovered by 2803:1810::/32 636 100% 67
2803:1810:c010::/44 Valid Nonecovered by 2803:1810::/32 635 100% 67
2803:1810::/48 Valid Nonecovered by 2803:1810::/32 20 3%low visibility 10
2803:1810::/32 Valid Other IRR onlyRADB 636 100% 69
201.218.157.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
201.218.159.0/24 Valid RIR databaseLACNIC, RADB 672 100% 67
38.137.207.0/24 Valid RIR databaseARIN, RADB 671 100% 67
38.137.194.0/24 Valid RIR databaseARIN, RADB 670 100% 67

AS-SET

AS271835'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 17 are in fix.csv.

  • ROA: none2
  • Route object: none11
  • Route object: RIR1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none8.243.115.160/27No ROA covers it. Add a ROA for AS271835, maxLength 27.2 of 673
Route object: none8.243.115.160/27No route object for it. Add a route object with origin AS271835 in the RIR database for the space.2 of 673
ROA: none204.199.170.32/27No ROA covers it. Add a ROA for AS271835, maxLength 27.2 of 673
Route object: none204.199.170.32/27No route object for it. Add a route object with origin AS271835 in the RIR database for the space.2 of 673
Route object: none181.233.27.0/24No route object for it. A route object for 181.233.24.0/22 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.672 of 673
Route object: none181.233.25.0/24No route object for it. A route object for 181.233.24.0/22 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.671 of 673
Route object: none181.233.26.0/24No route object for it. A route object for 181.233.24.0/22 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.671 of 673
Route object: none181.233.24.0/24No route object for it. A route object for 181.233.24.0/22 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.670 of 673
Route object: none2803:1810:3000::/44No route object for it. A route object for 2803:1810::/32 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.636 of 636
Route object: none2803:1810:f010::/44No route object for it. A route object for 2803:1810::/32 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.636 of 636
Route object: none2803:1810:f020::/44No route object for it. A route object for 2803:1810::/32 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.636 of 636
Route object: none2803:1810:c010::/44No route object for it. A route object for 2803:1810::/32 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.635 of 636
Route object: none2803:1810::/48No route object for it. A route object for 2803:1810::/32 with origin AS271835 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271835 in the RIR database for the space.20 of 636
Route object: RIR2803:1810::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

38.137.203.0/24RADBNo ROA
38.137.208.0/24RADBNo ROA
181.233.24.0/22RADBValid

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.