bgpreport

Network · data from 2026-11-12

AS28652 Telecomunicações Nordeste Ltda.

Registry name: AS28652 - Telecomunicacoes Nordeste Ltda., BR · PeeringDB

39IPv4 routes 100.0% RPKI valid · 100.0% with a route object
4IPv6 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
19Route objects not announced registered with origin AS28652, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS28652, 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.

143.255.48.0/22 Valid Other IRR onlyRADB 671 100% 66
177.47.32.0/20 Valid Other IRR onlyRADB 671 100% 66
177.47.32.0/21 Valid Other IRR onlyRADB 671 100% 66
177.47.36.0/22 Valid Other IRR onlyRADB 671 100% 66
177.47.40.0/21 Valid Other IRR onlyRADB 671 100% 66
177.47.40.0/22 Valid Other IRR onlyRADB 671 100% 66
177.47.44.0/22 Valid Other IRR onlyRADB 671 100% 66
177.47.48.0/20 Valid Other IRR onlyRADB 671 100% 66
177.47.48.0/21 Valid Other IRR onlyRADB 671 100% 66
177.47.56.0/21 Valid Other IRR onlyRADB 671 100% 66
177.155.96.0/22 Valid Other IRR onlyRADB 671 100% 66
177.155.100.0/23 Valid Other IRR onlyRADB 671 100% 66
187.60.112.0/20 Valid Other IRR onlyRADB 671 100% 66
187.60.112.0/21 Valid Other IRR onlyRADB 671 100% 66
187.60.112.0/22 Valid Other IRR onlyRADB 671 100% 66
187.60.120.0/21 Valid Other IRR onlyRADB 671 100% 66
189.90.176.0/20 Valid Other IRR onlyRADB 671 100% 66
189.90.176.0/21 Valid Other IRR onlyRADB 671 100% 66
189.90.176.0/22 Valid Other IRR onlyRADB 671 100% 66
189.90.180.0/22 Valid Other IRR onlyRADB 671 100% 66
189.90.184.0/22 Valid Other IRR onlyRADB 671 100% 66
189.90.188.0/22 Valid Other IRR onlyRADB 671 100% 66
201.76.128.0/20 Valid Other IRR onlyRADB 671 100% 66
201.76.128.0/21 Valid Other IRR onlyRADB 671 100% 66
201.76.132.0/22 Valid Other IRR onlyRADB 671 100% 66
201.76.136.0/21 Valid Other IRR onlyRADB 671 100% 66
177.47.32.0/22 Valid Other IRR onlyRADB 669 99% 66
2804:45c::/32 Valid Other IRR onlyRADB 633 100% 67
2804:45c::/48 Valid Other IRR onlyRADB 633 100% 67
2804:45c:251::/48 Valid Other IRR onlyRADB 633 100% 67
2804:45c:c100::/41 Valid Other IRR onlyRADB 633 100% 67
177.155.108.0/23 Valid Other IRR onlyRADB 205 30% 56
177.155.110.0/23 Valid Other IRR onlyRADB 205 30% 56
143.255.48.0/23 Valid Other IRR onlyRADB 200 30% 54
143.255.50.0/23 Valid Other IRR onlyRADB 200 30% 54
177.47.44.0/23 Valid Other IRR onlyRADB 200 30% 54
177.47.62.0/23 Valid Other IRR onlyRADB 200 30% 54
177.155.96.0/23 Valid Other IRR onlyRADB 200 30% 54
177.155.98.0/23 Valid Other IRR onlyRADB 200 30% 54
187.60.118.0/23 Valid Other IRR onlyRADB 200 30% 54
187.60.122.0/23 Valid Other IRR onlyRADB 200 30% 54
189.90.190.0/23 Valid Other IRR onlyRADB 200 30% 54
201.76.130.0/23 Valid Other IRR onlyRADB 200 30% 54

AS-SET

AS28652'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 62 are in fix.csv.

  • Route object: RIR43
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: RIR143.255.48.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.32.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.32.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.36.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.40.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.40.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.44.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.48.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.48.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.56.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.155.96.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.155.100.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.60.112.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.60.112.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.60.112.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.60.120.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR189.90.176.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR189.90.176.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR189.90.176.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR189.90.180.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR189.90.184.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR189.90.188.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR201.76.128.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR201.76.128.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR201.76.132.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR201.76.136.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR177.47.32.0/22Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:45c::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:45c::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:45c:251::/48Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR2804:45c:c100::/41Route object only in RADB. Add it in the RIR database for the space.633 of 636
Route object: RIR177.155.108.0/23Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR177.155.110.0/23Route object only in RADB. Add it in the RIR database for the space.205 of 673
Route object: RIR143.255.48.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR143.255.50.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR177.47.44.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR177.47.62.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR177.155.96.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR177.155.98.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR187.60.118.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR187.60.122.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR189.90.190.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673
Route object: RIR201.76.130.0/23Route object only in RADB. Add it in the RIR database for the space.200 of 673

Route objects not announced

Route objects with origin AS28652 whose prefix no peer sees AS28652 announce. Many are kept on purpose (backup routes, space announced only in some places).

177.47.46.0/23RADBValid
177.47.48.0/22RADBValid
177.47.50.0/24RADBValid
177.47.52.0/22RADBValid
177.47.56.0/23RADBValid
177.47.58.0/23RADBValid
177.47.60.0/22RADBValid
177.47.62.0/24RADBValid
177.155.96.0/20RADBNo ROA
177.155.100.0/24RADBValid
177.155.101.0/24RADBValid
177.155.108.0/22RADBValid
187.60.113.0/24RADBValid
187.60.118.0/24RADBValid
187.60.121.0/24RADBValid
189.90.183.0/24RADBValid
201.76.128.0/24RADBValid
201.76.129.0/24RADBValid
201.76.134.0/23RADBValid

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.