Network · data from 2026-11-12
AS151231 GC-INFOTECH - GOOGLE CHINA INFOTECH OU
Registry name: GC-INFOTECH - GOOGLE CHINA INFOTECH OU, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS151231, 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.
| 103.104.155.0/24 | Valid | Other IRR onlyRADB | 8 1%low visibility |
| 2402:2e60::/39 | Valid | Other IRR onlyRADB | 5 1%low visibility |
AS-SET
AS151231 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.
- Route object: RIR2
- Route object: not announced9
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 103.104.155.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2402:2e60::/39 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS151231 whose prefix no peer sees AS151231 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.104.152.0/22 | RADB | Valid |
| 103.104.152.0/23 | RADB | Valid |
| 103.104.152.0/24 | RADB | Valid |
| 103.104.153.0/24 | RADB | Valid |
| 103.104.154.0/23 | RADB | Valid |
| 103.104.154.0/24 | RADB | Valid |
| 2402:2e60::/32 | RADB | Valid |
| 2402:2e60:200::/39 | RADB | Valid |
| 2402:2e60:400::/39 | 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.