Network · data from 2026-11-12
AS48887 SOMONCOM-AS CJSC INDIGO TAJIKISTAN
Registry name: SOMONCOM-AS CJSC INDIGO TAJIKISTAN, TJ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48887, 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.
| 109.75.61.0/24 | Invalid: origin | RIR databaseRIPE | 1 0%low visibility |
| 217.8.32.0/23 | Valid | Nonecovered by 217.8.32.0/21 | 673 100% |
| 217.8.34.0/23 | Valid | Nonecovered by 217.8.32.0/21 | 673 100% |
| 217.8.36.0/23 | Valid | Nonecovered by 217.8.32.0/21 | 673 100% |
| 217.8.46.0/23 | Valid | Nonecovered by 217.8.40.0/21 | 673 100% |
| 217.8.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.8.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.8.44.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.8.45.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 109.75.58.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 109.75.62.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.8.32.0/20 | Valid | RIR databaseRIPE | 671 100% |
| 217.8.32.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.8.33.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.8.37.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 217.8.34.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.8.35.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.8.36.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.8.40.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.8.41.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.8.42.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.8.43.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 217.8.46.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 2a01:5d64::/30 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS48887 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: none4
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 109.75.61.0/24 | ROAs covering it name AS47139, not AS48887. If AS48887 should announce it, add a ROA for AS48887. |
| Route object: none | 217.8.32.0/23 | No route object for it. A route object for 217.8.32.0/21 with origin AS48887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48887 in the RIR database for the space. |
| Route object: none | 217.8.34.0/23 | No route object for it. A route object for 217.8.32.0/21 with origin AS48887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48887 in the RIR database for the space. |
| Route object: none | 217.8.36.0/23 | No route object for it. A route object for 217.8.32.0/21 with origin AS48887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48887 in the RIR database for the space. |
| Route object: none | 217.8.46.0/23 | No route object for it. A route object for 217.8.40.0/21 with origin AS48887 covers it (filters allowing more-specifics accept it). Add a route object with origin AS48887 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48887 whose prefix no peer sees AS48887 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 217.8.32.0/21 | RIPE | Invalid: maxLength |
| 217.8.40.0/21 | RIPE | Invalid: maxLength |
| 217.8.47.0/24 | RIPE | Invalid: maxLength |
| 2a01:5d60::/29 | RIPE | No ROA |
| 2a01:5d60::/48 | RIPE | Invalid: origin |
| 2a01:5d60:1::/48 | RIPE | Invalid: origin |
| 2a01:5d64::/48 | RIPE | Invalid: maxLength |
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.