bgpreport

Network · data from 2026-11-12

AS136166 ANGELONE-AS-AP - ANGEL ONE LIMITED

Registry name: ANGELONE-AS-AP - ANGEL ONE LIMITED, IN · not in PeeringDB

2IPv4 routes 100.0% RPKI valid · 100.0% with a route object
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
0Low visibility seen by under 10% of full-table peers
18Route objects not announced registered with origin AS136166, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136166, 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.82.176.0/23 Valid RIR databaseAPNIC 673 100% 66
103.82.178.0/23 Valid RIR databaseAPNIC, RADB 673 100% 66
2400:8740:1000::/48 Valid RIR databaseAPNIC, RADB 636 100% 70
2400:8740:2000::/40 Valid RIR databaseAPNIC 636 100% 69
2400:8740:2000::/48 Valid RIR databaseAPNIC 636 100% 70

AS-SET

AS136166 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 18 are in fix.csv.

  • Route object: not announced18

Route objects not announced

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

103.82.176.0/22APNICValid
103.82.176.0/24APNICValid
103.82.176.0/25APNICValid
103.82.176.128/25APNICValid
103.82.177.0/24APNICValid
103.82.177.0/25APNICValid
103.82.177.128/25APNICValid
103.82.178.0/24APNIC, RADBValid
103.82.178.0/25APNICValid
103.82.178.128/25APNICValid
103.82.179.0/24APNICValid
103.82.179.0/25APNICValid
103.82.179.128/25APNICValid
129.227.222.0/24APNIC, RADBValid
2400:8740::/32APNICNo ROA
2400:8740::/40APNICValid
2400:8740:1000::/40APNIC, RADBValid
2400:8740:3000::/40APNICValid

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.