bgpreport

Network · data from 2026-11-12

AS263264 AS263264 - GRUPO CONECTA TELECOM SCM LTDA EPP

Registry name: AS263264 - GRUPO CONECTA TELECOM SCM LTDA EPP, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS263264, 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.
2804:160c:4000::/34 No ROA Nonecovered by 2804:160c::/32 635 100% 67
2804:160c:4000::/36 No ROA Nonecovered by 2804:160c::/32 635 100% 67
2804:160c::/36 No ROA Nonecovered by 2804:160c::/34 634 100% 67
186.209.220.0/24 No ROA Other IRR onlyRADB 669 99% 67
186.209.221.0/24 No ROA Other IRR onlyRADB 669 99% 67
2804:160c::/34 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

AS263264 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 20 are in fix.csv.

  • ROA: none6
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none2804:160c:4000::/34No ROA covers it. Add a ROA for AS263264, maxLength 34.635 of 636
Route object: none2804:160c:4000::/34No route object for it. A route object for 2804:160c::/32 with origin AS263264 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263264 in the RIR database for the space.635 of 636
ROA: none2804:160c:4000::/36No ROA covers it. Add a ROA for AS263264, maxLength 36.635 of 636
Route object: none2804:160c:4000::/36No route object for it. A route object for 2804:160c::/32 with origin AS263264 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263264 in the RIR database for the space.635 of 636
ROA: none2804:160c::/36No ROA covers it. Add a ROA for AS263264, maxLength 36.634 of 636
Route object: none2804:160c::/36No route object for it. A route object for 2804:160c::/34 with origin AS263264 covers it (filters allowing more-specifics accept it). Add a route object with origin AS263264 in the RIR database for the space.634 of 636
ROA: none186.209.220.0/24No ROA covers it. Add a ROA for AS263264, maxLength 24.669 of 673
Route object: RIR186.209.220.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none186.209.221.0/24No ROA covers it. Add a ROA for AS263264, maxLength 24.669 of 673
Route object: RIR186.209.221.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:160c::/34No ROA covers it. Add a ROA for AS263264, maxLength 34.634 of 636
Route object: RIR2804:160c::/34Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

138.0.244.0/22RADBNo ROA
138.0.246.0/24RADBNo ROA
138.0.247.0/24RADBNo ROA
186.209.32.0/19RADBNo ROA
186.209.220.0/22RADBNo ROA
186.209.220.0/23RADBNo ROA
2804:160c::/32RADBNo ROA
2804:160c:e000::/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.