bgpreport

Network · data from 2026-11-12

AS263628 ADWAVE INFORMATICA LTDA

Registry name: AS263628 - ADWAVE TELECOM LTDA, BR · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
1IPv6 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
28Route objects not announced registered with origin AS263628, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS263628, 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.200.16.0/20 Valid Other IRR onlyRADB, TC 672 100% 67
2804:1048::/32 Valid Other IRR onlyRADB, TC 635 100% 69
177.200.16.0/21 Valid Other IRR onlyRADB 87 13% 30
177.200.24.0/21 Valid Other IRR onlyRADB 87 13% 30

AS-SET

AS263628'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 32 are in fix.csv.

  • Route object: RIR4
  • Route object: not announced28
ChangePrefix or setDetailFull-table peers
Route object: RIR177.200.16.0/20Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR2804:1048::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR177.200.16.0/21Route object only in RADB. Add it in the RIR database for the space.87 of 673
Route object: RIR177.200.24.0/21Route object only in RADB. Add it in the RIR database for the space.87 of 673

Route objects not announced

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

177.200.16.0/22RADBValid
177.200.16.0/23RADBValid
177.200.16.0/24RADBValid
177.200.17.0/24RADBValid
177.200.18.0/23RADBValid
177.200.18.0/24RADBValid
177.200.19.0/24RADBValid
177.200.20.0/22RADBValid
177.200.20.0/23RADBValid
177.200.20.0/24RADBValid
177.200.21.0/24RADBValid
177.200.22.0/23RADBValid
177.200.22.0/24RADBValid
177.200.23.0/24RADBValid
177.200.24.0/22RADBValid
177.200.24.0/23RADBValid
177.200.24.0/24RADBValid
177.200.25.0/24RADBValid
177.200.26.0/23RADBValid
177.200.26.0/24RADBValid
177.200.27.0/24RADBValid
177.200.28.0/22RADBValid
177.200.28.0/23RADBValid
177.200.28.0/24RADBValid
177.200.29.0/24RADBValid
177.200.30.0/23RADBValid
177.200.30.0/24RADBValid
177.200.31.0/24RADBValid

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.