Network · data from 2026-11-12
AS270110 AS270110 - FIBRA 360 SA de CV
Registry name: AS270110 - FIBRA 360 SA de CV, MX · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270110, 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:3b1::/36 | Valid | Nonecovered by 2806:3b1::/32 | 634 100% |
| 189.85.100.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 189.85.101.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 189.85.102.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 189.85.103.0/24 | Valid | Other IRR onlyRADB | 671 100% |
AS-SET
AS270110 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 7 are in fix.csv.
- Route object: none1
- Route object: RIR4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2806:3b1::/36 | No route object for it. A route object for 2806:3b1::/32 with origin AS270110 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270110 in the RIR database for the space. |
| Route object: RIR | 189.85.100.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.85.101.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.85.102.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 189.85.103.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270110 whose prefix no peer sees AS270110 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 189.85.100.0/22 | LACNIC, RADB | Valid |
| 2806:3b1::/32 | LACNIC, 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.