bgpreport

Network · data from 2026-11-12

AS271952 AS271952 - UNICABLE H.D. SAS

Registry name: AS271952 - UNICABLE H.D. SAS, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271952, 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.
2803:5790::/48 No ROA None 636 100% 67
2803:5790:1::/48 No ROA None 636 100% 67
2803:5790:2::/48 No ROA None 636 100% 67
2803:5790:3::/48 No ROA None 636 100% 67
204.199.96.64/26 No ROA None 2 0%low visibility 2
204.199.126.160/27 No ROA None 2 0%low visibility 2
209.61.57.0/24 Valid RIR databaseARIN 672 100% 67
190.109.49.0/24 Valid RIR databaseLACNIC, RADB 671 100% 67

AS-SET

AS271952 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 12 are in fix.csv.

  • ROA: none6
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none2803:5790::/48No ROA covers it. Add a ROA for AS271952, maxLength 48.636 of 636
Route object: none2803:5790::/48No route object for it. Add a route object with origin AS271952 in the RIR database for the space.636 of 636
ROA: none2803:5790:1::/48No ROA covers it. Add a ROA for AS271952, maxLength 48.636 of 636
Route object: none2803:5790:1::/48No route object for it. Add a route object with origin AS271952 in the RIR database for the space.636 of 636
ROA: none2803:5790:2::/48No ROA covers it. Add a ROA for AS271952, maxLength 48.636 of 636
Route object: none2803:5790:2::/48No route object for it. Add a route object with origin AS271952 in the RIR database for the space.636 of 636
ROA: none2803:5790:3::/48No ROA covers it. Add a ROA for AS271952, maxLength 48.636 of 636
Route object: none2803:5790:3::/48No route object for it. Add a route object with origin AS271952 in the RIR database for the space.636 of 636
ROA: none204.199.96.64/26No ROA covers it. Add a ROA for AS271952, maxLength 26.2 of 673
Route object: none204.199.96.64/26No route object for it. Add a route object with origin AS271952 in the RIR database for the space.2 of 673
ROA: none204.199.126.160/27No ROA covers it. Add a ROA for AS271952, maxLength 27.2 of 673
Route object: none204.199.126.160/27No route object for it. Add a route object with origin AS271952 in the RIR database for the space.2 of 673

Route objects not announced

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