bgpreport

Network · data from 2026-11-12

AS272244 AS272244 - Pi Telecom

Registry name: AS272244 - Pi Telecom, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272244, 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.
186.216.28.0/24 Invalid: origin Other origin only 7 1%low visibility 5
2804:842c::/34 No ROA Nonecovered by 2804:842c::/32 635 100% 67
2804:842c:4000::/34 No ROA Nonecovered by 2804:842c::/32 635 100% 67
2804:842c:8000::/34 No ROA Nonecovered by 2804:842c::/32 635 100% 67
2804:842c:c000::/34 No ROA Nonecovered by 2804:842c::/32 635 100% 67
2804:842c::/32 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

AS272244 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: origin1
  • ROA: none5
  • Route object: none5
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: origin186.216.28.0/24ROAs covering it name AS262663, not AS272244. If AS272244 should announce it, add a ROA for AS272244.7 of 673
Route object: none186.216.28.0/24Route objects for it name AS262663. Add a route object with origin AS272244 in the RIR database for the space.7 of 673
ROA: none2804:842c::/34No ROA covers it. Add a ROA for AS272244, maxLength 34.635 of 636
Route object: none2804:842c::/34No route object for it. A route object for 2804:842c::/32 with origin AS272244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272244 in the RIR database for the space.635 of 636
ROA: none2804:842c:4000::/34No ROA covers it. Add a ROA for AS272244, maxLength 34.635 of 636
Route object: none2804:842c:4000::/34No route object for it. A route object for 2804:842c::/32 with origin AS272244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272244 in the RIR database for the space.635 of 636
ROA: none2804:842c:8000::/34No ROA covers it. Add a ROA for AS272244, maxLength 34.635 of 636
Route object: none2804:842c:8000::/34No route object for it. A route object for 2804:842c::/32 with origin AS272244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272244 in the RIR database for the space.635 of 636
ROA: none2804:842c:c000::/34No ROA covers it. Add a ROA for AS272244, maxLength 34.635 of 636
Route object: none2804:842c:c000::/34No route object for it. A route object for 2804:842c::/32 with origin AS272244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272244 in the RIR database for the space.635 of 636
ROA: none2804:842c::/32No ROA covers it. Add a ROA for AS272244, maxLength 32.635 of 636
Route object: RIR2804:842c::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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