bgpreport

Network · data from 2026-11-12

AS52856 NETWAY PROVEDOR DE INTERNET LTDA

Registry name: AS52856 - NETWAY PROVEDOR DE INTERNET LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52856, 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.11.160.0/21 No ROA Other IRR onlyRADB, TC 672 100% 67
2804:4dcc::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
177.11.160.0/24 No ROA Other IRR onlyTC 202 30% 56
177.11.161.0/24 No ROA Other IRR onlyTC 202 30% 56
177.11.162.0/24 No ROA Other IRR onlyRADB, TC 202 30% 56
177.11.163.0/24 No ROA Other IRR onlyTC 202 30% 56
177.11.164.0/24 No ROA Other IRR onlyRADB, TC 202 30% 56
177.11.165.0/24 No ROA Other IRR onlyRADB, TC 202 30% 56
177.11.166.0/24 No ROA Other IRR onlyTC 202 30% 56
177.11.167.0/24 No ROA Other IRR onlyTC 202 30% 56

AS-SET

AS52856'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 29 are in fix.csv.

  • ROA: none10
  • Route object: RIR10
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: none177.11.160.0/21No ROA covers it. Add a ROA for AS52856, maxLength 21.672 of 673
Route object: RIR177.11.160.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:4dcc::/32No ROA covers it. Add a ROA for AS52856, maxLength 32.635 of 636
Route object: RIR2804:4dcc::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none177.11.160.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.160.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
ROA: none177.11.161.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.161.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
ROA: none177.11.162.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.162.0/24Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
ROA: none177.11.163.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.163.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
ROA: none177.11.164.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.164.0/24Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
ROA: none177.11.165.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.165.0/24Route object only in RADB, TC. Add it in the RIR database for the space.202 of 673
ROA: none177.11.166.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.166.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673
ROA: none177.11.167.0/24No ROA covers it. Add a ROA for AS52856, maxLength 24.202 of 673
Route object: RIR177.11.167.0/24Route object only in TC. Add it in the RIR database for the space.202 of 673

Route objects not announced

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

177.11.160.0/22TCNo ROA
177.11.160.0/23TCNo ROA
177.11.162.0/23TCNo ROA
177.11.164.0/22TCNo ROA
177.11.164.0/23RADB, TCNo ROA
177.11.166.0/23TCNo ROA
2804:4dcc:7000::/36RADBNo ROA
2804:4dcc:8000::/36RADBNo ROA
2804:4dcc:9000::/36RADBNo 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.