bgpreport

Network · data from 2026-11-12

AS47139 INDIGO TAJIKISTAN

Registry name: INDIGO-TAJIKISTAN-AS CJSC INDIGO TAJIKISTAN, TJ · PeeringDB

23IPv4 routes 91.3% RPKI valid · 95.7% with a route object
1IPv6 routes 100.0% RPKI valid · 100.0% with a route object
1RPKI invalid 0 origin · 1 maxLength
1No ROA 1 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS47139, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS47139, 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.54.0/24 Invalid: maxLength RIR databaseRIPE 2 0%low visibility 2
185.42.96.0/22 No ROA RIR databaseRIPE 2 0%low visibility 2
109.75.61.0/24 Valid Other origin onlycovered by 109.75.48.0/20 671 100% 67
109.75.48.0/24 Valid RIR databaseRIPE 673 100% 66
109.75.49.0/24 Valid RIR databaseRIPE 673 100% 66
109.75.50.0/24 Valid RIR databaseRIPE 673 100% 66
109.75.52.0/24 Valid RIR databaseRIPE 673 100% 66
109.75.55.0/24 Valid RIR databaseRIPE 673 100% 66
109.75.56.0/24 Valid RIR databaseRIPE 673 100% 66
185.42.96.0/24 Valid RIR databaseRIPE 673 100% 66
185.42.98.0/24 Valid RIR databaseRIPE 673 100% 66
109.75.48.0/20 Valid RIR databaseRIPE 672 100% 66
109.75.51.0/24 Valid RIR databaseRIPE 672 100% 66
109.75.53.0/24 Valid RIR databaseRIPE 672 100% 67
109.75.57.0/24 Valid RIR databaseRIPE 672 100% 67
109.75.59.0/24 Valid RIR databaseRIPE 672 100% 67
109.75.60.0/24 Valid RIR databaseRIPE 672 100% 67
109.75.63.0/24 Valid RIR databaseRIPE 672 100% 67
185.42.97.0/24 Valid RIR databaseRIPE 672 100% 67
185.42.99.0/24 Valid RIR databaseRIPE 672 100% 67
195.246.102.0/23 Valid RIR databaseRIPE 672 100% 66
195.246.102.0/24 Valid RIR databaseRIPE 672 100% 66
2a01:5d60::/30 Valid RIR databaseRIPE 633 100% 68
195.246.103.0/24 Valid RIR databaseRIPE 2 0%low visibility 3

AS-SET

AS47139's PeeringDB record names no 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 5 are in fix.csv.

  • ROA: maxLength1
  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength109.75.54.0/24ROA 109.75.48.0/20 AS47139 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 109.75.54.0/24.2 of 673
ROA: none185.42.96.0/22No ROA covers it. Add a ROA for AS47139, maxLength 22.2 of 673
Route object: none109.75.61.0/24Route objects for it name AS48887. A route object for 109.75.48.0/20 with origin AS47139 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47139 in the RIR database for the space.671 of 673

Route objects not announced

Route objects with origin AS47139 whose prefix no peer sees AS47139 announce. Many are kept on purpose (backup routes, space announced only in some places).

185.42.96.0/23RIPENo ROA
185.42.98.0/23RIPENo 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.