bgpreport

Network · data from 2026-11-12

AS264429 V1 Telecomunicacoes e Informatica LTDA - ME

Registry name: AS264429 - V1 Telecomunicacoes e Informatica LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS264429, 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:1e70:100::/40 Valid Nonecovered by 2804:1e70::/34 633 100% 67
131.221.132.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
170.245.116.0/24 Valid Other IRR onlyALTDB, RADB 671 100% 67
170.245.117.0/24 Valid Other IRR onlyALTDB, RADB 669 99% 67
170.245.118.0/23 Valid Other IRR onlyALTDB, RADB 669 99% 67
131.221.134.0/23 Valid Other IRR onlyALTDB, RADB 668 99% 67
170.245.118.0/24 Valid Other IRR onlyALTDB, RADB 668 99% 67
170.245.119.0/24 Valid Other IRR onlyALTDB, RADB 668 99% 67
131.221.132.0/23 Valid Other IRR onlyALTDB, RADB 667 99% 67
2804:1e70::/34 Valid Other IRR onlyTC 632 99% 67
2804:1e70:4000::/34 Valid Other IRR onlyTC 632 99% 67

AS-SET

AS264429'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 19 are in fix.csv.

  • Route object: none1
  • Route object: RIR10
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: none2804:1e70:100::/40No route object for it. A route object for 2804:1e70::/34 with origin AS264429 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264429 in the RIR database for the space.633 of 636
Route object: RIR131.221.132.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.245.116.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR170.245.117.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.245.118.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR131.221.134.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR170.245.118.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR170.245.119.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR131.221.132.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:1e70::/34Route object only in TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:1e70:4000::/34Route object only in TC. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

131.221.132.0/24ALTDB, RADBValid
131.221.133.0/24ALTDB, RADBValid
131.221.134.0/24ALTDB, RADBValid
131.221.135.0/24ALTDB, RADBValid
170.245.116.0/22ALTDB, RADB, TCValid
170.245.116.0/23ALTDB, RADBValid
2804:1e70::/32RADB, TCValid
2804:1e70:8000::/34RADBValid

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.