bgpreport

Network · data from 2026-11-12

AS268145 IPV7 SERVICOS DE TELECOMUNICACOES BRASIL

Registry name: AS268145 - IPV7 SERVICOS DE TELECOMUNICACOES BRASIL LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268145, 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.
45.170.16.0/23 No ROA Nonecovered by 45.170.16.0/22 669 99% 67
45.170.18.0/23 No ROA Nonecovered by 45.170.16.0/22 668 99% 67
2804:58b4:8000::/33 No ROA Nonecovered by 2804:58b4::/32 635 100% 67
2804:58b4::/33 No ROA Nonecovered by 2804:58b4::/32 634 100% 67
45.170.16.0/22 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:58b4::/32 No ROA Other IRR onlyRADB, TC 634 100% 67

AS-SET

AS268145'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.

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none45.170.16.0/23No ROA covers it. Add a ROA for AS268145, maxLength 23.669 of 673
Route object: none45.170.16.0/23No route object for it. A route object for 45.170.16.0/22 with origin AS268145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268145 in the RIR database for the space.669 of 673
ROA: none45.170.18.0/23No ROA covers it. Add a ROA for AS268145, maxLength 23.668 of 673
Route object: none45.170.18.0/23No route object for it. A route object for 45.170.16.0/22 with origin AS268145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268145 in the RIR database for the space.668 of 673
ROA: none2804:58b4:8000::/33No ROA covers it. Add a ROA for AS268145, maxLength 33.635 of 636
Route object: none2804:58b4:8000::/33No route object for it. A route object for 2804:58b4::/32 with origin AS268145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268145 in the RIR database for the space.635 of 636
ROA: none2804:58b4::/33No ROA covers it. Add a ROA for AS268145, maxLength 33.634 of 636
Route object: none2804:58b4::/33No route object for it. A route object for 2804:58b4::/32 with origin AS268145 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268145 in the RIR database for the space.634 of 636
ROA: none45.170.16.0/22No ROA covers it. Add a ROA for AS268145, maxLength 22.669 of 673
Route object: RIR45.170.16.0/22Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:58b4::/32No ROA covers it. Add a ROA for AS268145, maxLength 32.634 of 636
Route object: RIR2804:58b4::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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