bgpreport

Network · data from 2026-11-12

AS268481 AS268481 - CENTERSAT TELECOMUNICACOES LTDA

Registry name: AS268481 - CENTERSAT TELECOMUNICACOES LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268481, 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.161.192.0/24 Valid Nonecovered by 45.161.192.0/22 671 100% 67
45.161.194.0/24 Valid Nonecovered by 45.161.192.0/22 671 100% 67
45.161.195.0/24 Valid Nonecovered by 45.161.192.0/22 671 100% 67
45.161.193.0/24 Valid Nonecovered by 45.161.192.0/22 670 100% 67
2804:51dc:1080::/43 Valid Nonecovered by 2804:51dc::/32 635 100% 67
2804:51dc:10a0::/43 Valid Nonecovered by 2804:51dc::/32 635 100% 67
2804:51dc:10c0::/43 Valid Nonecovered by 2804:51dc::/32 635 100% 67
2804:51dc:10e0::/43 Valid Nonecovered by 2804:51dc::/32 635 100% 67
45.161.192.0/22 Valid Other IRR onlyRADB 671 100% 67
2804:51dc::/32 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS268481 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 10 are in fix.csv.

  • Route object: none8
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
Route object: none45.161.192.0/24No route object for it. A route object for 45.161.192.0/22 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.671 of 673
Route object: none45.161.194.0/24No route object for it. A route object for 45.161.192.0/22 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.671 of 673
Route object: none45.161.195.0/24No route object for it. A route object for 45.161.192.0/22 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.671 of 673
Route object: none45.161.193.0/24No route object for it. A route object for 45.161.192.0/22 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.670 of 673
Route object: none2804:51dc:1080::/43No route object for it. A route object for 2804:51dc::/32 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.635 of 636
Route object: none2804:51dc:10a0::/43No route object for it. A route object for 2804:51dc::/32 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.635 of 636
Route object: none2804:51dc:10c0::/43No route object for it. A route object for 2804:51dc::/32 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.635 of 636
Route object: none2804:51dc:10e0::/43No route object for it. A route object for 2804:51dc::/32 with origin AS268481 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268481 in the RIR database for the space.635 of 636
Route object: RIR45.161.192.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:51dc::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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