Network · data from 2026-11-12
AS139118 RuguInfo - Shanghai Rugu Info&Tech Co.,Ltd.
Registry name: RuguInfo - Shanghai Rugu Info&Tech Co.,Ltd., CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS139118, 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.
| 43.242.98.0/23 | Valid | None | 672 100% |
| 43.242.96.0/23 | Valid | None | 606 90% |
| 103.156.68.0/23 | Valid | Other origin only | 132 20% |
AS-SET
AS139118 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 3 are in fix.csv.
- Route object: none3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 43.242.98.0/23 | No route object for it. Add a route object with origin AS139118 in the RIR database for the space. |
| Route object: none | 43.242.96.0/23 | No route object for it. Add a route object with origin AS139118 in the RIR database for the space. |
| Route object: none | 103.156.68.0/23 | Route objects for it name AS4812. Add a route object with origin AS139118 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS139118 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.