bgpreport

Network · data from 2026-11-12

AS269339 CONEXAO WEB TELECOM LTDA

Registry name: AS269339 - CONEXAO WEB TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS269339, 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.
45.182.96.0/22 Valid Other IRR onlyALTDB, RADB, TC 671 100% 67
2804:631c::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 67
45.182.96.0/23 Valid Other IRR onlyALTDB 64 10%low visibility 21
45.182.98.0/23 Valid Other IRR onlyALTDB 64 10%low visibility 21
2804:631c::/33 Valid Other IRR onlyALTDB 53 8%low visibility 20
2804:631c:8000::/33 Valid Other IRR onlyALTDB 53 8%low visibility 20

AS-SET

AS269339'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 14 are in fix.csv.

  • Route object: RIR6
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
Route object: RIR45.182.96.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:631c::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR45.182.96.0/23Route object only in ALTDB. Add it in the RIR database for the space.64 of 673
Route object: RIR45.182.98.0/23Route object only in ALTDB. Add it in the RIR database for the space.64 of 673
Route object: RIR2804:631c::/33Route object only in ALTDB. Add it in the RIR database for the space.53 of 636
Route object: RIR2804:631c:8000::/33Route object only in ALTDB. Add it in the RIR database for the space.53 of 636

Route objects not announced

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

45.182.96.0/24ALTDBValid
45.182.97.0/24ALTDBValid
45.182.98.0/24ALTDBValid
45.182.99.0/24ALTDBValid
2804:631c::/34ALTDBValid
2804:631c:4000::/34ALTDBValid
2804:631c:8000::/34ALTDBValid
2804:631c:c000::/34ALTDBValid

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.