Network · data from 2026-11-12
AS28506 AS28506 - Sistemas de Communicacion GM S.A. de C.V.
Registry name: AS28506 - Sistemas de Communicacion GM S.A. de C.V., MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28506, 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.
| 200.78.138.0/24 | Invalid: origin | None | 2 0%low visibility |
| 200.78.168.0/24 | Invalid: origin | None | 2 0%low visibility |
| 187.176.185.0/24 | Invalid: origin | Other IRR onlyRADB | 4 1%low visibility |
| 200.34.66.0/24 | Invalid: origin | Other IRR onlyRADB | 4 1%low visibility |
| 200.34.141.0/24 | No ROA | Other IRR onlyRADB | 669 99% |
| 148.243.37.0/24 | Valid | RIR databaseLACNIC | 672 100% |
| 148.245.248.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.139.252.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.139.253.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.139.255.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.180.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.181.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.182.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.183.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.184.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.185.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.186.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.187.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.188.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.189.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.140.190.0/24 | Valid | RIR databaseLACNIC, RADB | 672 100% |
| 201.139.254.0/24 | Valid | RIR databaseLACNIC | 670 100% |
AS-SET
AS28506 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: origin4
- ROA: none1
- Route object: none2
- Route object: RIR3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 200.78.138.0/24 | ROAs covering it name AS6503, not AS28506. If AS28506 should announce it, add a ROA for AS28506. |
| Route object: none | 200.78.138.0/24 | No route object for it. Add a route object with origin AS28506 in the RIR database for the space. |
| ROA: origin | 200.78.168.0/24 | ROAs covering it name AS6503, not AS28506. If AS28506 should announce it, add a ROA for AS28506. |
| Route object: none | 200.78.168.0/24 | No route object for it. Add a route object with origin AS28506 in the RIR database for the space. |
| ROA: origin | 187.176.185.0/24 | ROAs covering it name AS6503, not AS28506. If AS28506 should announce it, add a ROA for AS28506. |
| Route object: RIR | 187.176.185.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: origin | 200.34.66.0/24 | ROAs covering it name AS6503, not AS28506. If AS28506 should announce it, add a ROA for AS28506. |
| Route object: RIR | 200.34.66.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 200.34.141.0/24 | No ROA covers it. Add a ROA for AS28506, maxLength 24. |
| Route object: RIR | 200.34.141.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28506 whose prefix no peer sees AS28506 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 201.140.0.0/14 | RADB | No 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.