bgpreport

Network · data from 2026-11-12

AS142511 SPEEDNET AS NETWORK

Registry name: ASNETWORK-AS-IN - SPEEDNET AS NETWORK PRIVATE LIMITED, IN · PeeringDB

4IPv4 routes 75.0% RPKI valid · 75.0% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
0No 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 AS142511, seen from no peer

Announced routes

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

103.157.150.0/23 Invalid: origin Other origin only 1 0%low visibility 1
103.171.24.0/23 Valid RIR databaseAPNIC 672 100% 67
103.171.24.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1
103.171.25.0/24 Valid RIR databaseAPNIC 1 0%low visibility 1

AS-SET

AS142511'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 4 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin103.157.150.0/23ROAs covering it name AS135799, not AS142511. If AS142511 should announce it, add a ROA for AS142511.1 of 673
Route object: none103.157.150.0/23Route objects for it name AS135799. Add a route object with origin AS142511 in the RIR database for the space.1 of 673

Route objects not announced

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

2001:df0:2840::/48APNICValid
2001:df7:3280::/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.