bgpreport

Network · data from 2026-11-12

AS53160 UNIDASNET COMUNICAÇÕES

Registry name: AS53160 - UNIDASNET COMUNICACOES LTDA, BR · PeeringDB

37IPv4 routes 100.0% RPKI valid · 100.0% with a route object
7IPv6 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
3Low visibility seen by under 10% of full-table peers
25Route objects not announced registered with origin AS53160, seen from no peer

Announced routes

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

138.186.132.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
138.186.132.0/23 Valid Other IRR onlyTC 671 100% 66
138.186.132.0/24 Valid Other IRR onlyTC 671 100% 67
138.186.134.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.112.0/20 Valid Other IRR onlyRADB, TC 671 100% 66
187.19.112.0/21 Valid Other IRR onlyTC 671 100% 66
187.19.112.0/22 Valid Other IRR onlyTC 671 100% 66
187.19.112.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.112.0/24 Valid Other IRR onlyTC 671 100% 67
187.19.114.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.116.0/22 Valid Other IRR onlyTC 671 100% 66
187.19.116.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.118.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.120.0/21 Valid Other IRR onlyTC 671 100% 66
187.19.120.0/22 Valid Other IRR onlyTC 671 100% 66
187.19.120.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.121.0/24 Valid Other IRR onlyTC 671 100% 67
187.19.122.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.124.0/22 Valid Other IRR onlyTC 671 100% 66
187.19.124.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.126.0/23 Valid Other IRR onlyTC 671 100% 66
187.19.127.0/24 Valid Other IRR onlyTC 669 99% 67
2804:26d8::/32 Valid Other IRR onlyRADB, TC 634 100% 67
2804:26d8::/33 Valid Other IRR onlyTC 634 100% 67
2804:26d8:8000::/33 Valid Other IRR onlyTC 634 100% 67
187.19.114.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.115.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.116.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.117.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.118.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.119.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.124.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.125.0/24 Valid Other IRR onlyTC 128 19% 45
187.19.126.0/24 Valid Other IRR onlyTC 128 19% 45
138.186.133.0/24 Valid Other IRR onlyTC 126 19% 44
187.19.113.0/24 Valid Other IRR onlyTC 126 19% 44
138.186.135.0/24 Valid Other IRR onlyTC 124 18% 44
2804:26d8::/34 Valid Other IRR onlyTC 68 11% 34
2804:26d8:4000::/34 Valid Other IRR onlyTC 68 11% 34
2804:26d8:8000::/34 Valid Other IRR onlyTC 68 11% 34
2804:26d8:c000::/34 Valid Other IRR onlyTC 68 11% 34
187.19.120.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
187.19.122.0/24 Valid Other IRR onlyTC 2 0%low visibility 2
187.19.123.0/24 Valid Other IRR onlyTC 2 0%low visibility 2

AS-SET

AS53160'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 69 are in fix.csv.

  • Route object: RIR44
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
Route object: RIR138.186.132.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.186.132.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.186.132.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR138.186.134.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.112.0/20Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.112.0/21Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.112.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.112.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.112.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.114.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.116.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.116.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.118.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.120.0/21Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.120.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.120.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.121.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.122.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.124.0/22Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.124.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.126.0/23Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.19.127.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:26d8::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:26d8::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:26d8:8000::/33Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR187.19.114.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.115.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.116.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.117.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.118.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.119.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.124.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.125.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR187.19.126.0/24Route object only in TC. Add it in the RIR database for the space.128 of 673
Route object: RIR138.186.133.0/24Route object only in TC. Add it in the RIR database for the space.126 of 673
Route object: RIR187.19.113.0/24Route object only in TC. Add it in the RIR database for the space.126 of 673
Route object: RIR138.186.135.0/24Route object only in TC. Add it in the RIR database for the space.124 of 673
Route object: RIR2804:26d8::/34Route object only in TC. Add it in the RIR database for the space.68 of 636
Route object: RIR2804:26d8:4000::/34Route object only in TC. Add it in the RIR database for the space.68 of 636
Route object: RIR2804:26d8:8000::/34Route object only in TC. Add it in the RIR database for the space.68 of 636
Route object: RIR2804:26d8:c000::/34Route object only in TC. Add it in the RIR database for the space.68 of 636
Route object: RIR187.19.120.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR187.19.122.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
Route object: RIR187.19.123.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

138.186.134.0/24TCValid
2804:26d8::/35TCValid
2804:26d8::/36TCValid
2804:26d8:1000::/36TCValid
2804:26d8:2000::/35TCValid
2804:26d8:2000::/36TCValid
2804:26d8:3000::/36TCValid
2804:26d8:4000::/35TCValid
2804:26d8:4000::/36TCValid
2804:26d8:5000::/36TCValid
2804:26d8:6000::/35TCValid
2804:26d8:6000::/36TCValid
2804:26d8:7000::/36TCValid
2804:26d8:8000::/35TCValid
2804:26d8:8000::/36TCValid
2804:26d8:9000::/36TCValid
2804:26d8:a000::/35TCValid
2804:26d8:a000::/36TCValid
2804:26d8:b000::/36TCValid
2804:26d8:c000::/35TCValid
2804:26d8:c000::/36TCValid
2804:26d8:d000::/36TCValid
2804:26d8:e000::/35TCValid
2804:26d8:e000::/36TCValid
2804:26d8:f000::/36TCValid

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.