bgpreport

Network · data from 2026-11-12

AS154239 Neosoft Technologies And Software Pvt Ltd

Registry name: IRINN-NEOSOFT-AS-IN - Neosoft Technologies And Software Pvt Ltd, IN · PeeringDB

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

Announced routes

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

101.0.40.0/24 No ROA Other origin only 673 100% 67
203.115.86.0/24 No ROA Other origin only 673 100% 67
101.0.36.0/24 Valid RIR databaseAPNIC 673 100% 66
101.0.48.0/24 Valid RIR databaseAPNIC 673 100% 67
103.149.199.0/24 Valid RIR databaseAPNIC 673 100% 66

AS-SET

AS154239'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 6 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none101.0.40.0/24No ROA covers it. Add a ROA for AS154239, maxLength 24.673 of 673
Route object: none101.0.40.0/24Route objects for it name AS23682. Add a route object with origin AS154239 in the RIR database for the space.673 of 673
ROA: none203.115.86.0/24No ROA covers it. Add a ROA for AS154239, maxLength 24.673 of 673
Route object: none203.115.86.0/24Route objects for it name AS23682. Add a route object with origin AS154239 in the RIR database for the space.673 of 673

Route objects not announced

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

103.149.198.0/23APNICValid
103.149.198.0/24APNICValid

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.