bgpreport

Network · data from 2026-11-12

AS133975 CHEMPLASTSANMAR-AS-IN - Chemplast Sanmar Limited

Registry name: CHEMPLASTSANMAR-AS-IN - Chemplast Sanmar Limited, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133975, 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.54.64.0/24 Valid RIR databaseAPNIC 670 100% 67
103.54.65.0/24 Valid RIR databaseAPNIC 2 0%low visibility 2

AS-SET

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

  • Route object: not announced6

Route objects not announced

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

103.54.64.0/22APNICValid
103.54.64.0/23APNICValid
103.54.66.0/23APNICValid
103.54.66.0/24APNICValid
103.54.67.0/24APNICValid
2001:df3:6c00::/48APNICNo 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.