bgpreport

Network · data from 2026-11-12

AS28425 AS28425 - Convergencia Inalambrica, S.A. de C.V.

Registry name: AS28425 - Convergencia Inalambrica, S.A. de C.V., MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS28425, 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.231.108.0/24 No ROA Nonecovered by 45.231.108.0/22 672 100% 67
45.231.109.0/24 No ROA Nonecovered by 45.231.108.0/22 672 100% 67
45.231.110.0/24 No ROA Nonecovered by 45.231.108.0/22 672 100% 67
45.231.111.0/24 No ROA Nonecovered by 45.231.108.0/22 672 100% 67
200.23.144.0/24 No ROA Other origin only 672 100% 67

AS-SET

AS28425 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 11 are in fix.csv.

  • ROA: none5
  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none45.231.108.0/24No ROA covers it. Add a ROA for AS28425, maxLength 24.672 of 673
Route object: none45.231.108.0/24No route object for it. A route object for 45.231.108.0/22 with origin AS28425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28425 in the RIR database for the space.672 of 673
ROA: none45.231.109.0/24No ROA covers it. Add a ROA for AS28425, maxLength 24.672 of 673
Route object: none45.231.109.0/24No route object for it. A route object for 45.231.108.0/22 with origin AS28425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28425 in the RIR database for the space.672 of 673
ROA: none45.231.110.0/24No ROA covers it. Add a ROA for AS28425, maxLength 24.672 of 673
Route object: none45.231.110.0/24No route object for it. A route object for 45.231.108.0/22 with origin AS28425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28425 in the RIR database for the space.672 of 673
ROA: none45.231.111.0/24No ROA covers it. Add a ROA for AS28425, maxLength 24.672 of 673
Route object: none45.231.111.0/24No route object for it. A route object for 45.231.108.0/22 with origin AS28425 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28425 in the RIR database for the space.672 of 673
ROA: none200.23.144.0/24No ROA covers it. Add a ROA for AS28425, maxLength 24.672 of 673
Route object: none200.23.144.0/24Route objects for it name AS19332. Add a route object with origin AS28425 in the RIR database for the space.672 of 673

Route objects not announced

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

45.231.108.0/22RADBNo 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.