bgpreport

Network · data from 2026-11-12

AS270724 CLIENT.CO SERVIÇOS E TELECOMUNICAÇÕES LTDA

Registry name: AS270724 - CLIENT.CO SERVICOS E TELECOMUNICACOES LTDA, BR · PeeringDB

14IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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 AS270724, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS270724, 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.160.228.0/22 Valid Other IRR onlyTC 672 100% 67
45.160.228.0/23 Valid Other IRR onlyTC 672 100% 67
45.160.229.0/24 Valid Other IRR onlyTC 672 100% 67
45.160.230.0/23 Valid Other IRR onlyTC 672 100% 67
45.160.230.0/24 Valid Other IRR onlyTC 672 100% 67
189.51.32.0/22 Valid Other IRR onlyRADB, TC 672 100% 67
189.51.32.0/23 Valid Other IRR onlyTC 672 100% 67
189.51.32.0/24 Valid Other IRR onlyTC 672 100% 67
189.51.33.0/24 Valid Other IRR onlyTC 672 100% 67
189.51.34.0/23 Valid Other IRR onlyTC 672 100% 67
189.51.34.0/24 Valid Other IRR onlyTC 672 100% 67
189.51.35.0/24 Valid Other IRR onlyTC 672 100% 67
45.160.228.0/24 Valid Other IRR onlyTC 671 100% 67
45.160.231.0/24 Valid Other IRR onlyTC 671 100% 67
2804:7064::/32 Valid Other IRR onlyRADB, TC 633 100% 67

AS-SET

AS270724'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 15 are in fix.csv.

  • Route object: RIR15
ChangePrefix or setDetailFull-table peers
Route object: RIR45.160.228.0/22Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.160.228.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.160.229.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.160.230.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.160.230.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.51.32.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.51.32.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.51.32.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.51.33.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.51.34.0/23Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.51.34.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR189.51.35.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR45.160.228.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.160.231.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:7064::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636

Route objects not announced

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