bgpreport

Network · data from 2026-11-12

AS3905 AS3905 - CONSORCIO REDUNO S.A. de C.V

Registry name: AS3905 - CONSORCIO REDUNO S.A. de C.V, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS3905, 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.
2806:1070:401::/48 Invalid: origin None 205 32% 60
189.240.32.0/24 Invalid: origin None 19 3%low visibility 16
204.124.104.0/24 No ROA Other origin only 673 100% 67
204.124.106.0/24 No ROA Other origin only 673 100% 67
204.124.107.0/24 No ROA Other origin only 673 100% 67
200.4.144.0/24 No ROA None 672 100% 67
200.4.145.0/24 No ROA None 672 100% 67
200.4.158.0/23 No ROA None 672 100% 67
189.247.131.0/24 Valid RIR databaseLACNIC 673 100% 67
189.254.64.0/24 Valid RIR databaseLACNIC 673 100% 67

AS-SET

AS3905 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 16 are in fix.csv.

  • ROA: origin2
  • ROA: none6
  • Route object: none8
ChangePrefix or setDetailFull-table peers
ROA: origin2806:1070:401::/48ROAs covering it name AS8151, not AS3905. If AS3905 should announce it, add a ROA for AS3905.205 of 636
Route object: none2806:1070:401::/48No route object for it. Add a route object with origin AS3905 in the RIR database for the space.205 of 636
ROA: origin189.240.32.0/24ROAs covering it name AS8151, not AS3905. If AS3905 should announce it, add a ROA for AS3905.19 of 673
Route object: none189.240.32.0/24No route object for it. Add a route object with origin AS3905 in the RIR database for the space.19 of 673
ROA: none204.124.104.0/24No ROA covers it. Add a ROA for AS3905, maxLength 24.673 of 673
Route object: none204.124.104.0/24Route objects for it name AS8151. Add a route object with origin AS3905 in the RIR database for the space.673 of 673
ROA: none204.124.106.0/24No ROA covers it. Add a ROA for AS3905, maxLength 24.673 of 673
Route object: none204.124.106.0/24Route objects for it name AS8151. Add a route object with origin AS3905 in the RIR database for the space.673 of 673
ROA: none204.124.107.0/24No ROA covers it. Add a ROA for AS3905, maxLength 24.673 of 673
Route object: none204.124.107.0/24Route objects for it name AS8151, AS19905. Add a route object with origin AS3905 in the RIR database for the space.673 of 673
ROA: none200.4.144.0/24No ROA covers it. Add a ROA for AS3905, maxLength 24.672 of 673
Route object: none200.4.144.0/24No route object for it. Add a route object with origin AS3905 in the RIR database for the space.672 of 673
ROA: none200.4.145.0/24No ROA covers it. Add a ROA for AS3905, maxLength 24.672 of 673
Route object: none200.4.145.0/24No route object for it. Add a route object with origin AS3905 in the RIR database for the space.672 of 673
ROA: none200.4.158.0/23No ROA covers it. Add a ROA for AS3905, maxLength 23.672 of 673
Route object: none200.4.158.0/23No route object for it. Add a route object with origin AS3905 in the RIR database for the space.672 of 673

Route objects not announced

Every route object with origin AS3905 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.