Network · data from 2026-11-12
AS63708 LTIDC - Guangdong LITONG Network Technology Limited
Registry name: LTIDC - Guangdong LITONG Network Technology Limited, CN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS63708, 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.
| 139.159.104.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 139.159.96.0/24 | Valid | None | 5 1%low visibility |
| 139.159.97.0/24 | Valid | None | 5 1%low visibility |
| 139.159.98.0/24 | Valid | None | 5 1%low visibility |
| 139.159.99.0/24 | Valid | None | 5 1%low visibility |
| 139.159.100.0/24 | Valid | None | 5 1%low visibility |
| 139.159.101.0/24 | Valid | None | 5 1%low visibility |
| 139.159.102.0/24 | Valid | None | 5 1%low visibility |
| 139.159.103.0/24 | Valid | None | 5 1%low visibility |
| 139.159.105.0/24 | Valid | Other origin only | 5 1%low visibility |
| 139.159.106.0/24 | Valid | Other origin only | 5 1%low visibility |
AS-SET
AS63708 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 12 are in fix.csv.
- ROA: origin1
- Route object: none11
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 139.159.104.0/24 | ROAs covering it name AS63199, not AS63708. If AS63708 should announce it, add a ROA for AS63708. |
| Route object: none | 139.159.104.0/24 | Route objects for it name AS63199. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.96.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.97.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.98.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.99.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.100.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.101.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.102.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.103.0/24 | No route object for it. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.105.0/24 | Route objects for it name AS63199. Add a route object with origin AS63708 in the RIR database for the space. |
| Route object: none | 139.159.106.0/24 | Route objects for it name AS63199. Add a route object with origin AS63708 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS63708 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.