bgpreport

Network · data from 2026-11-12

AS266128 AS266128 - CENTRAL SAT INTERNET LTDA

Registry name: AS266128 - CENTRAL SAT INTERNET LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266128, 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:3b14::/33 No ROA Nonecovered by 2804:3b14::/32 635 100% 68
2804:3b14::/34 No ROA Nonecovered by 2804:3b14::/32 635 100% 68
45.6.56.0/23 No ROA Other IRR onlyALTDB 668 99% 67
45.6.58.0/23 No ROA Other IRR onlyALTDB, RADB 668 99% 67
45.6.56.0/22 No ROA Other IRR onlyALTDB, RADB 667 99% 67
45.6.56.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
45.6.57.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
45.6.58.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
45.6.59.0/24 No ROA Other IRR onlyALTDB, RADB 667 99% 67
2804:3b14::/32 No ROA Other IRR onlyALTDB, RADB 635 100% 68

AS-SET

AS266128 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 20 are in fix.csv.

  • ROA: none10
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none2804:3b14::/33No ROA covers it. Add a ROA for AS266128, maxLength 33.635 of 636
Route object: none2804:3b14::/33No route object for it. A route object for 2804:3b14::/32 with origin AS266128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266128 in the RIR database for the space.635 of 636
ROA: none2804:3b14::/34No ROA covers it. Add a ROA for AS266128, maxLength 34.635 of 636
Route object: none2804:3b14::/34No route object for it. A route object for 2804:3b14::/32 with origin AS266128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266128 in the RIR database for the space.635 of 636
ROA: none45.6.56.0/23No ROA covers it. Add a ROA for AS266128, maxLength 23.668 of 673
Route object: RIR45.6.56.0/23Route object only in ALTDB. Add it in the RIR database for the space.668 of 673
ROA: none45.6.58.0/23No ROA covers it. Add a ROA for AS266128, maxLength 23.668 of 673
Route object: RIR45.6.58.0/23Route object only in ALTDB, RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.6.56.0/22No ROA covers it. Add a ROA for AS266128, maxLength 22.667 of 673
Route object: RIR45.6.56.0/22Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.6.56.0/24No ROA covers it. Add a ROA for AS266128, maxLength 24.667 of 673
Route object: RIR45.6.56.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.6.57.0/24No ROA covers it. Add a ROA for AS266128, maxLength 24.667 of 673
Route object: RIR45.6.57.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.6.58.0/24No ROA covers it. Add a ROA for AS266128, maxLength 24.667 of 673
Route object: RIR45.6.58.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none45.6.59.0/24No ROA covers it. Add a ROA for AS266128, maxLength 24.667 of 673
Route object: RIR45.6.59.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:3b14::/32No ROA covers it. Add a ROA for AS266128, maxLength 32.635 of 636
Route object: RIR2804:3b14::/32Route object only in ALTDB, RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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