bgpreport

Network · data from 2026-11-12

AS52657 Norte Telecomunicações

Registry name: AS52657 - NORTE TELECOMUNICACOES SERVICOS DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52657, 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:5bcc:6e00::/40 Valid Nonecovered by 2804:5bcc:6000::/36 631 99% 67
2804:5bcc:6f00::/40 Valid Nonecovered by 2804:5bcc:6000::/36 631 99% 67
2804:5bcc:7100::/40 Valid Nonecovered by 2804:5bcc:7000::/36 631 99% 67
177.104.240.0/20 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
177.104.240.0/24 Valid Other IRR onlyALTDB, RADB, TC 672 100% 66
177.104.241.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
177.104.242.0/24 Valid Other IRR onlyRADB, TC 672 100% 66
177.104.243.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
177.104.245.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
177.104.247.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
177.104.248.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
177.104.251.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
177.104.253.0/24 Valid Other IRR onlyRADB, TC 671 100% 67
177.104.254.0/24 Valid Other IRR onlyRADB, TC 671 100% 66
177.104.255.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
177.104.244.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
177.104.250.0/24 Valid Other IRR onlyRADB, TC 668 99% 67
177.104.252.0/24 Valid Other IRR onlyRADB, TC 668 99% 66
177.104.246.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
177.104.249.0/24 Valid Other IRR onlyRADB, TC 667 99% 67
2804:5bcc::/32 Valid Other IRR onlyRADB, TC 631 99% 67
2804:5bcc::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:1000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:2000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:3000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:4000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:5000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:6000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:7000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:8000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:9000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:a000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:b000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:c000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:d000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:e000::/36 Valid Other IRR onlyTC 631 99% 67
2804:5bcc:f000::/36 Valid Other IRR onlyTC 631 99% 67

AS-SET

AS52657'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 65 are in fix.csv.

  • Route object: none3
  • Route object: RIR34
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
Route object: none2804:5bcc:6e00::/40No route object for it. A route object for 2804:5bcc:6000::/36 with origin AS52657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52657 in the RIR database for the space.631 of 636
Route object: none2804:5bcc:6f00::/40No route object for it. A route object for 2804:5bcc:6000::/36 with origin AS52657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52657 in the RIR database for the space.631 of 636
Route object: none2804:5bcc:7100::/40No route object for it. A route object for 2804:5bcc:7000::/36 with origin AS52657 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52657 in the RIR database for the space.631 of 636
Route object: RIR177.104.240.0/20Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.104.240.0/24Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.104.241.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.104.242.0/24Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.104.243.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.104.245.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.104.247.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.104.248.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.104.251.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.104.253.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.104.254.0/24Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.104.255.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.104.244.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.104.250.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.104.252.0/24Route object only in RADB, TC. Add it in the RIR database for the space.668 of 673
Route object: RIR177.104.246.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR177.104.249.0/24Route object only in RADB, TC. Add it in the RIR database for the space.667 of 673
Route object: RIR2804:5bcc::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:1000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:2000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:3000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:4000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:5000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:6000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:7000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:8000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:9000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:a000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:b000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:c000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:d000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:e000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636
Route object: RIR2804:5bcc:f000::/36Route object only in TC. Add it in the RIR database for the space.631 of 636

Route objects not announced

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

177.104.240.0/21TCValid
177.104.240.0/22TCValid
177.104.240.0/23TCValid
177.104.242.0/23TCValid
177.104.244.0/22TCValid
177.104.244.0/23TCValid
177.104.246.0/23TCValid
177.104.248.0/21TCValid
177.104.248.0/22TCValid
177.104.248.0/23TCValid
177.104.250.0/23TCValid
177.104.252.0/22TCValid
177.104.252.0/23TCValid
177.104.254.0/23TCValid
2804:5bcc::/33TCValid
2804:5bcc::/34TCValid
2804:5bcc::/35TCValid
2804:5bcc:2000::/35TCValid
2804:5bcc:4000::/34TCValid
2804:5bcc:4000::/35TCValid
2804:5bcc:6000::/35TCValid
2804:5bcc:8000::/33TCValid
2804:5bcc:8000::/34TCValid
2804:5bcc:8000::/35TCValid
2804:5bcc:a000::/35TCValid
2804:5bcc:c000::/34TCValid
2804:5bcc:c000::/35TCValid
2804:5bcc:e000::/35TCValid

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.