bgpreport

Network · data from 2026-11-12

AS274535 CONEXT TELECOMUNICAÇOES

Registry name: AS274535 - CONEXT TELECOMUNICACOES LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274535, 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.227.43.0/24 No ROA Other origin only 670 100% 67
2804:95a4::/32 No ROA Other IRR onlyTC 635 100% 67

AS-SET

AS274535'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 4 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none45.227.43.0/24No ROA covers it. Add a ROA for AS274535, maxLength 24.670 of 673
Route object: none45.227.43.0/24Route objects for it name AS267042. Add a route object with origin AS274535 in the RIR database for the space.670 of 673
ROA: none2804:95a4::/32No ROA covers it. Add a ROA for AS274535, maxLength 32.635 of 636
Route object: RIR2804:95a4::/32Route object only in TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS274535 is announced.

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.