bgpreport

Network · data from 2026-11-12

AS265113 Sales Telecom e Informatica

Registry name: AS265113 - SALES TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS265113, 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.
170.254.108.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
170.254.109.0/24 Valid Other IRR onlyALTDB 669 99% 67
170.254.110.0/24 Valid Other IRR onlyALTDB 669 99% 67
2804:330c::/32 Valid Other IRR onlyALTDB, RADB, TC 636 100% 67
2804:330c::/34 Valid Other IRR onlyALTDB 636 100% 67
2804:330c:4000::/34 Valid Other IRR onlyALTDB 636 100% 67
2804:330c:8000::/34 Valid Other IRR onlyALTDB 636 100% 67
2804:330c:c000::/34 Valid Other IRR onlyALTDB 636 100% 67
170.254.111.0/24 Valid Other IRR onlyALTDB 228 34% 56
170.254.108.0/23 Valid Other IRR onlyALTDB 200 30% 54
170.254.110.0/23 Valid Other IRR onlyALTDB 200 30% 54
170.254.108.0/24 Valid Other IRR onlyALTDB 197 29% 54

AS-SET

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

  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: RIR170.254.108.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR170.254.109.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR170.254.110.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:330c::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:330c::/34Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:330c:4000::/34Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:330c:8000::/34Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR2804:330c:c000::/34Route object only in ALTDB. Add it in the RIR database for the space.636 of 636
Route object: RIR170.254.111.0/24Route object only in ALTDB. Add it in the RIR database for the space.228 of 673
Route object: RIR170.254.108.0/23Route object only in ALTDB. Add it in the RIR database for the space.200 of 673
Route object: RIR170.254.110.0/23Route object only in ALTDB. Add it in the RIR database for the space.200 of 673
Route object: RIR170.254.108.0/24Route object only in ALTDB. Add it in the RIR database for the space.197 of 673

Route objects not announced

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