bgpreport

Network · data from 2026-11-12

AS45417 CFLINDIA-NET-IN - 1-2-10, S P ROAD

Registry name: CFLINDIA-NET-IN - 1-2-10, S P ROAD, IN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45417, 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.
2001:df3:4a40::/48 Invalid: origin RIR databaseAPNIC 106 17% 42
202.129.239.0/24 No ROA RIR databaseAPNIC, RADB 673 100% 66
165.99.25.0/24 No ROA RIR databaseAPNIC 672 100% 66

AS-SET

AS45417 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 3 are in fix.csv.

  • ROA: origin1
  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: origin2001:df3:4a40::/48ROAs covering it name AS9498, not AS45417. If AS45417 should announce it, add a ROA for AS45417.106 of 636
ROA: none202.129.239.0/24No ROA covers it. Add a ROA for AS45417, maxLength 24.673 of 673
ROA: none165.99.25.0/24No ROA covers it. Add a ROA for AS45417, maxLength 24.672 of 673

Route objects not announced

Every route object with origin AS45417 is announced.

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.