bgpreport

Network · data from 2026-11-12

AS267476 AS267476 - TT Peixoto Provedor de Internet LTDA ME

Registry name: AS267476 - TT Peixoto Provedor de Internet LTDA ME, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS267476, 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.
192.141.204.0/23 No ROA Nonecovered by 192.141.204.0/22 136 20% 45
192.141.206.0/23 No ROA Nonecovered by 192.141.204.0/22 136 20% 45
192.141.204.0/24 No ROA Nonecovered by 192.141.204.0/22 5 1%low visibility 2
192.141.205.0/24 No ROA Nonecovered by 192.141.204.0/22 5 1%low visibility 2
192.141.206.0/24 No ROA Nonecovered by 192.141.204.0/22 5 1%low visibility 2
192.141.207.0/24 No ROA Nonecovered by 192.141.204.0/22 5 1%low visibility 2
192.141.204.0/22 No ROA Other IRR onlyNTTCOM, RADB 671 100% 67
2804:4214::/32 No ROA Other IRR onlyNTTCOM, RADB 5 1%low visibility 3

AS-SET

AS267476 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 16 are in fix.csv.

  • ROA: none8
  • Route object: none6
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none192.141.204.0/23No ROA covers it. Add a ROA for AS267476, maxLength 23.136 of 673
Route object: none192.141.204.0/23No route object for it. A route object for 192.141.204.0/22 with origin AS267476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267476 in the RIR database for the space.136 of 673
ROA: none192.141.206.0/23No ROA covers it. Add a ROA for AS267476, maxLength 23.136 of 673
Route object: none192.141.206.0/23No route object for it. A route object for 192.141.204.0/22 with origin AS267476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267476 in the RIR database for the space.136 of 673
ROA: none192.141.204.0/24No ROA covers it. Add a ROA for AS267476, maxLength 24.5 of 673
Route object: none192.141.204.0/24No route object for it. A route object for 192.141.204.0/22 with origin AS267476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267476 in the RIR database for the space.5 of 673
ROA: none192.141.205.0/24No ROA covers it. Add a ROA for AS267476, maxLength 24.5 of 673
Route object: none192.141.205.0/24No route object for it. A route object for 192.141.204.0/22 with origin AS267476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267476 in the RIR database for the space.5 of 673
ROA: none192.141.206.0/24No ROA covers it. Add a ROA for AS267476, maxLength 24.5 of 673
Route object: none192.141.206.0/24No route object for it. A route object for 192.141.204.0/22 with origin AS267476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267476 in the RIR database for the space.5 of 673
ROA: none192.141.207.0/24No ROA covers it. Add a ROA for AS267476, maxLength 24.5 of 673
Route object: none192.141.207.0/24No route object for it. A route object for 192.141.204.0/22 with origin AS267476 covers it (filters allowing more-specifics accept it). Add a route object with origin AS267476 in the RIR database for the space.5 of 673
ROA: none192.141.204.0/22No ROA covers it. Add a ROA for AS267476, maxLength 22.671 of 673
Route object: RIR192.141.204.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
ROA: none2804:4214::/32No ROA covers it. Add a ROA for AS267476, maxLength 32.5 of 636
Route object: RIR2804:4214::/32Route object only in NTTCOM, RADB. Add it in the RIR database for the space.5 of 636

Route objects not announced

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