bgpreport

Network · data from 2026-11-12

AS271326 P3 SERVIÇOS DE TELECOMUNICAÇÃO LTDA

Registry name: AS271326 - P3 SERVICOS DE TELECOMUNICACAO LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271326, 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.
2804:79c4:8020::/45 Valid Nonecovered by 2804:79c4:8020::/44 636 100% 67
2804:79c4:8028::/45 Valid Nonecovered by 2804:79c4:8020::/44 636 100% 67
190.123.72.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
190.123.73.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
190.123.74.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
190.123.75.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
2804:79c4:8020::/44 Valid Other IRR onlyRADB, TC 635 100% 69

AS-SET

AS271326'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 15 are in fix.csv.

  • Route object: none2
  • Route object: RIR5
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2804:79c4:8020::/45No route object for it. A route object for 2804:79c4:8020::/44 with origin AS271326 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271326 in the RIR database for the space.636 of 636
Route object: none2804:79c4:8028::/45No route object for it. A route object for 2804:79c4:8020::/44 with origin AS271326 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271326 in the RIR database for the space.636 of 636
Route object: RIR190.123.72.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR190.123.73.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR190.123.74.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR190.123.75.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:79c4:8020::/44Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

190.123.72.0/22TCNo ROA
190.123.72.0/23RADB, TCNo ROA
190.123.74.0/23RADB, TCNo ROA
2804:79c4::/32RADB, TCNo ROA
2804:79c4::/33RADBNo ROA
2804:79c4:8000::/44TCNo ROA
2804:79c4:8010::/44RADB, TCNo ROA
2804:79c4:8030::/44TCNo 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.