Network · data from 2026-11-12
AS264637 Blue Consulting Group
Registry name: AS264637 - Blue Consulting Group, S. A., GT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS264637, 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.
| 170.80.21.0/24 | Valid | Nonecovered by 170.80.20.0/22 | 672 100% |
| 190.113.88.0/24 | Valid | Nonecovered by 190.113.88.0/22 | 670 100% |
| 190.113.90.0/24 | Valid | Nonecovered by 190.113.88.0/22 | 670 100% |
| 190.113.91.0/24 | Valid | Nonecovered by 190.113.88.0/22 | 670 100% |
| 170.80.22.0/24 | Valid | Nonecovered by 170.80.20.0/22 | 669 99% |
| 170.80.20.0/24 | Valid | Nonecovered by 170.80.20.0/22 | 662 98% |
| 190.113.89.0/24 | Valid | Nonecovered by 190.113.88.0/22 | 660 98% |
| 45.185.30.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.187.210.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.187.211.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 170.80.23.0/24 | Valid | Other IRR onlyRADB | 661 98% |
| 2803:5300::/32 | Valid | RIR databaseLACNIC, RADB | 634 100% |
AS-SET
AS264637'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 14 are in fix.csv.
- Route object: none7
- Route object: RIR4
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 170.80.21.0/24 | No route object for it. A route object for 170.80.20.0/22 with origin AS264637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264637 in the RIR database for the space. |
| Route object: none | 190.113.88.0/24 | No route object for it. A route object for 190.113.88.0/22 with origin AS264637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264637 in the RIR database for the space. |
| Route object: none | 190.113.90.0/24 | No route object for it. A route object for 190.113.88.0/22 with origin AS264637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264637 in the RIR database for the space. |
| Route object: none | 190.113.91.0/24 | No route object for it. A route object for 190.113.88.0/22 with origin AS264637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264637 in the RIR database for the space. |
| Route object: none | 170.80.22.0/24 | No route object for it. A route object for 170.80.20.0/22 with origin AS264637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264637 in the RIR database for the space. |
| Route object: none | 170.80.20.0/24 | No route object for it. A route object for 170.80.20.0/22 with origin AS264637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264637 in the RIR database for the space. |
| Route object: none | 190.113.89.0/24 | No route object for it. A route object for 190.113.88.0/22 with origin AS264637 covers it (filters allowing more-specifics accept it). Add a route object with origin AS264637 in the RIR database for the space. |
| Route object: RIR | 45.185.30.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.210.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.187.211.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 170.80.23.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS264637 whose prefix no peer sees AS264637 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 170.80.20.0/22 | LACNIC, RADB | Valid |
| 190.113.88.0/22 | LACNIC, RADB | Valid |
| 2803:af60::/32 | RADB | Valid |
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.