bgpreport

Network · data from 2026-11-12

AS132568 Infinet Communictions

Registry name: INFINET-AS - INFINET, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132568, 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:df1:6dc0::/48 No ROA RIR databaseAPNIC 610 96% 68
103.24.108.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.24.109.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.24.110.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.24.111.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
45.120.16.0/24 Valid RIR databaseAPNIC 671 100% 66
45.120.17.0/24 Valid RIR databaseAPNIC 671 100% 67
45.120.18.0/24 Valid RIR databaseAPNIC 671 100% 67
45.120.19.0/24 Valid RIR databaseAPNIC 671 100% 66

AS-SET

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

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2001:df1:6dc0::/48No ROA covers it. Add a ROA for AS132568, maxLength 48.610 of 636

Route objects not announced

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

45.120.16.0/22APNICValid
103.24.108.0/22APNICValid

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.