bgpreport

Network · data from 2026-11-12

AS263590 AS263590 - LOCAWEB SERVICOS DE INTERNET S.A.

Registry name: AS263590 - LOCAWEB SERVICOS DE INTERNET S.A., BR · not in PeeringDB

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

Announced routes

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

177.70.224.0/20 No ROA Other IRR onlyRADB 672 100% 67
177.136.16.0/20 No ROA Other IRR onlyRADB 672 100% 67
177.136.48.0/20 No ROA Other IRR onlyRADB 672 100% 67
179.109.208.0/20 No ROA Other IRR onlyRADB 672 100% 67
179.109.224.0/19 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

AS263590 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 102 are in fix.csv.

  • ROA: none5
  • Route object: RIR5
  • Route object: not announced92
ChangePrefix or setDetailFull-table peers
ROA: none177.70.224.0/20No ROA covers it. Add a ROA for AS263590, maxLength 20.672 of 673
Route object: RIR177.70.224.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.136.16.0/20No ROA covers it. Add a ROA for AS263590, maxLength 20.672 of 673
Route object: RIR177.136.16.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none177.136.48.0/20No ROA covers it. Add a ROA for AS263590, maxLength 20.672 of 673
Route object: RIR177.136.48.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none179.109.208.0/20No ROA covers it. Add a ROA for AS263590, maxLength 20.672 of 673
Route object: RIR179.109.208.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none179.109.224.0/19No ROA covers it. Add a ROA for AS263590, maxLength 19.672 of 673
Route object: RIR179.109.224.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

177.70.224.0/21RADBNo ROA
177.70.224.0/22RADBNo ROA
177.70.224.0/23RADBNo ROA
177.70.224.0/24RADBNo ROA
177.70.225.0/24RADBNo ROA
177.70.226.0/23RADBNo ROA
177.70.226.0/24RADBNo ROA
177.70.227.0/24RADBNo ROA
177.70.228.0/22RADBNo ROA
177.70.228.0/23RADBNo ROA
177.70.228.0/24RADBNo ROA
177.70.229.0/24RADBNo ROA
177.70.230.0/23RADBNo ROA
177.70.230.0/24RADBNo ROA
177.70.231.0/24RADBNo ROA
177.70.232.0/21RADBNo ROA
177.70.232.0/22RADBNo ROA
177.70.232.0/23RADBNo ROA
177.70.232.0/24RADBNo ROA
177.70.233.0/24RADBNo ROA
177.70.234.0/23RADBNo ROA
177.70.234.0/24RADBNo ROA
177.70.235.0/24RADBNo ROA
177.70.236.0/22RADBNo ROA
177.70.236.0/23RADBNo ROA
177.70.236.0/24RADBNo ROA
177.70.237.0/24RADBNo ROA
177.70.238.0/23RADBNo ROA
177.70.238.0/24RADBNo ROA
177.70.239.0/24RADBNo ROA
177.136.16.0/21RADBNo ROA
177.136.16.0/22RADBNo ROA
177.136.16.0/23RADBNo ROA
177.136.16.0/24RADBNo ROA
177.136.17.0/24RADBNo ROA
177.136.18.0/23RADBNo ROA
177.136.18.0/24RADBNo ROA
177.136.19.0/24RADBNo ROA
177.136.20.0/22RADBNo ROA
177.136.20.0/23RADBNo ROA
177.136.20.0/24RADBNo ROA
177.136.21.0/24RADBNo ROA
177.136.22.0/23RADBNo ROA
177.136.22.0/24RADBNo ROA
177.136.23.0/24RADBNo ROA
177.136.24.0/21RADBNo ROA
177.136.24.0/22RADBNo ROA
177.136.24.0/23RADBNo ROA
177.136.24.0/24RADBNo ROA
177.136.25.0/24RADBNo ROA
177.136.26.0/23RADBNo ROA
177.136.26.0/24RADBNo ROA
177.136.27.0/24RADBNo ROA
177.136.28.0/22RADBNo ROA
177.136.28.0/23RADBNo ROA
177.136.28.0/24RADBNo ROA
177.136.29.0/24RADBNo ROA
177.136.30.0/23RADBNo ROA
177.136.30.0/24RADBNo ROA
177.136.31.0/24RADBNo ROA
177.136.48.0/21RADBNo ROA
177.136.48.0/22RADBNo ROA
177.136.48.0/23RADBNo ROA
177.136.48.0/24RADBNo ROA
177.136.49.0/24RADBNo ROA
177.136.50.0/23RADBNo ROA
177.136.50.0/24RADBNo ROA
177.136.51.0/24RADBNo ROA
177.136.52.0/22RADBNo ROA
177.136.52.0/23RADBNo ROA
177.136.52.0/24RADBNo ROA
177.136.53.0/24RADBNo ROA
177.136.54.0/23RADBNo ROA
177.136.54.0/24RADBNo ROA
177.136.55.0/24RADBNo ROA
177.136.56.0/21RADBNo ROA
177.136.56.0/22RADBNo ROA
177.136.56.0/23RADBNo ROA
177.136.56.0/24RADBNo ROA
177.136.57.0/24RADBNo ROA
177.136.58.0/23RADBNo ROA
177.136.58.0/24RADBNo ROA
177.136.59.0/24RADBNo ROA
177.136.60.0/22RADBNo ROA
177.136.60.0/23RADBNo ROA
177.136.60.0/24RADBNo ROA
177.136.61.0/24RADBNo ROA
177.136.62.0/23RADBNo ROA
177.136.62.0/24RADBNo ROA
177.136.63.0/24RADBNo ROA
179.109.208.0/24RADBNo ROA
2801:80:790::/48RADBNo ROA

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.