Network · data from 2026-11-12
AS140362 DIGISIGMAPTELTD-AS-AP - DIGISIGMA PTE. LTD.
Registry name: DIGISIGMAPTELTD-AS-AP - DIGISIGMA PTE. LTD., SG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS140362, 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.
| 2602:feda:adb::/48 | No ROA | Nonecovered by 2602:feda:ad0::/44 | 633 100% |
| 2602:feda:adc::/48 | No ROA | Nonecovered by 2602:feda:ad0::/44 | 633 100% |
| 2602:feda:adf::/48 | No ROA | Nonecovered by 2602:feda:ad0::/44 | 633 100% |
| 103.196.26.0/24 | No ROA | Other IRR onlyRADB | 673 100% |
| 2400:a260::/48 | No ROA | Other IRR onlyRADB | 634 100% |
| 157.10.250.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 157.10.251.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 160.30.120.0/24 | Valid | RIR databaseAPNIC | 673 100% |
| 160.30.121.0/24 | Valid | RIR databaseAPNIC | 673 100% |
AS-SET
AS140362 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 13 are in fix.csv.
- ROA: none5
- Route object: none3
- Route object: RIR3
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:feda:adb::/48 | No ROA covers it. Add a ROA for AS140362, maxLength 48. |
| Route object: none | 2602:feda:adb::/48 | No route object for it. A route object for 2602:feda:ad0::/44 with origin AS140362 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140362 in the RIR database for the space. |
| ROA: none | 2602:feda:adc::/48 | No ROA covers it. Add a ROA for AS140362, maxLength 48. |
| Route object: none | 2602:feda:adc::/48 | No route object for it. A route object for 2602:feda:ad0::/44 with origin AS140362 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140362 in the RIR database for the space. |
| ROA: none | 2602:feda:adf::/48 | No ROA covers it. Add a ROA for AS140362, maxLength 48. |
| Route object: none | 2602:feda:adf::/48 | No route object for it. A route object for 2602:feda:ad0::/44 with origin AS140362 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140362 in the RIR database for the space. |
| ROA: none | 103.196.26.0/24 | No ROA covers it. Add a ROA for AS140362, maxLength 24. |
| Route object: RIR | 103.196.26.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2400:a260::/48 | No ROA covers it. Add a ROA for AS140362, maxLength 48. |
| Route object: RIR | 2400:a260::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 157.10.250.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS140362 whose prefix no peer sees AS140362 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 160.30.120.0/23 | APNIC | Valid |
| 2602:feda:ad0::/44 | ARIN | 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.