bgpreport

Network · data from 2026-11-12

AS141825 EXTREMEC1-AS-IN - EXTREME COMPUTE TECHNOLOGIES PRIVATE LIMITED

Registry name: EXTREMEC1-AS-IN - EXTREME COMPUTE TECHNOLOGIES PRIVATE LIMITED, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141825, 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.

38.226.63.0/24 Invalid: origin Other origin only 137 20% 49
103.192.72.0/22 Invalid: origin Other origin only 129 19% 50
130.117.119.0/24 No ROA Other IRR onlyRADB 673 100% 66
103.167.180.0/24 Valid RIR databaseAPNIC 672 100% 67
103.177.31.0/24 Valid RIR databaseAPNIC 671 100% 66
38.146.201.0/24 Valid RIR databaseARIN 632 94% 66

AS-SET

AS141825 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 7 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin38.226.63.0/24ROAs covering it name AS9498, AS136625, not AS141825. If AS141825 should announce it, add a ROA for AS141825.137 of 673
Route object: none38.226.63.0/24Route objects for it name AS9498, AS136625. Add a route object with origin AS141825 in the RIR database for the space.137 of 673
ROA: origin103.192.72.0/22ROAs covering it name AS136625, not AS141825. If AS141825 should announce it, add a ROA for AS141825.129 of 673
Route object: none103.192.72.0/22Route objects for it name AS136625. Add a route object with origin AS141825 in the RIR database for the space.129 of 673
ROA: none130.117.119.0/24No ROA covers it. Add a ROA for AS141825, maxLength 24.673 of 673
Route object: RIR130.117.119.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

2001:df6:ba80::/48APNICValid

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.