bgpreport

Network · data from 2026-11-12

AS153293 HOSTYCARE-AS-IN - Srmak Technological System Private Limited

Registry name: HOSTYCARE-AS-IN - Srmak Technological System Private Limited, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS153293, 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.
2402:7a0:216::/48 Valid RIR databaseAPNIC 12 2%low visibility 13
2402:7a0:217::/48 Valid RIR databaseAPNIC 12 2%low visibility 13
2402:7a0:218::/48 Valid RIR databaseAPNIC 12 2%low visibility 13

AS-SET

AS153293 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.

  • Route object: not announced7

Route objects not announced

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

103.184.162.0/23APNICNo ROA
2402:7a0:210::/48APNICValid
2402:7a0:211::/48APNICValid
2402:7a0:212::/48APNICValid
2402:7a0:213::/48APNICValid
2402:7a0:214::/48APNICValid
2402:7a0:215::/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.