bgpreport

Network · data from 2026-11-12

AS150650 Nexotel

Registry name: NEXOTEL-AS-IN - Nexotel Pvt Ltd, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS150650, 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.
2001:df1:f1c0::/48 Invalid: origin Other origin only 65 10% 32
103.84.106.0/24 Valid RIR databaseAPNIC 672 100% 67
103.84.107.0/24 Valid RIR databaseAPNIC 672 100% 66
138.252.194.0/24 Valid RIR databaseAPNIC 672 100% 67
138.252.195.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS150650'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 3 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2001:df1:f1c0::/48ROAs covering it name AS137633, not AS150650. If AS150650 should announce it, add a ROA for AS150650.65 of 636
Route object: none2001:df1:f1c0::/48Route objects for it name AS137633. Add a route object with origin AS150650 in the RIR database for the space.65 of 636

Route objects not announced

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

103.84.106.0/23APNICValid

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.