bgpreport

Network · data from 2026-11-12

AS142461 ATC INFOCOM SOLUTIONS PVT LTD

Registry name: ATCINFO-AS-IN - ATC INFOCOM SOLUTIONS PVT LTD, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS142461, 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.
160.19.41.0/24 Valid Other origin only 672 100% 67
103.168.210.0/23 Valid RIR databaseAPNIC 672 100% 67
103.168.210.0/24 Valid RIR databaseAPNIC 672 100% 67
103.168.211.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS142461'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 2 are in fix.csv.

  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none160.19.41.0/24Route objects for it name AS142462. Add a route object with origin AS142461 in the RIR database for the space.672 of 673

Route objects not announced

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

2001:df2:2940::/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.