Network · data from 2026-11-12
AS15107 AS15107 - Grupo Financiero Bancomer
Registry name: AS15107 - Grupo Financiero Bancomer, MX · not in PeeringDB
21IPv4 routes
100.0% RPKI valid · 57.1% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
9 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS15107, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS15107, 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.
| 148.244.56.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 673 100% |
| 148.244.30.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 672 100% |
| 148.244.42.0/24 | Valid | Other origin onlycovered by 148.244.0.0/18 | 672 100% |
| 148.244.43.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 672 100% |
| 148.244.48.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 672 100% |
| 148.244.54.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 672 100% |
| 148.244.55.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 672 100% |
| 148.244.58.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 672 100% |
| 148.244.62.0/24 | Valid | Nonecovered by 148.244.0.0/18 | 671 100% |
| 148.244.38.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 148.244.40.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 148.244.45.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 148.244.47.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 148.244.49.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 148.244.53.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 148.244.57.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 148.244.61.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 148.244.50.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 148.244.51.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 148.244.63.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 148.244.0.0/18 | Valid | RIR databaseLACNIC, RADB | 672 100% |
AS-SET
AS15107 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.
- Route object: none9
- Route object: RIR11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 148.244.56.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.30.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.42.0/24 | Route objects for it name AS11172. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.43.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.48.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.54.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.55.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.58.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: none | 148.244.62.0/24 | No route object for it. A route object for 148.244.0.0/18 with origin AS15107 covers it (filters allowing more-specifics accept it). Add a route object with origin AS15107 in the RIR database for the space. |
| Route object: RIR | 148.244.38.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.40.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.45.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.47.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.49.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.53.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.57.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.61.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.50.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.51.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 148.244.63.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS15107 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.