bgpreport

Network · data from 2026-11-12

AS45644 SBI-EMS-NET-IN - IT-Networking Department

Registry name: SBI-EMS-NET-IN - IT-Networking Department, IN · not in PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object
6IPv6 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
16Route objects not announced registered with origin AS45644, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45644, 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.61.133.0/24 Valid RIR databaseAPNIC 673 100% 66
202.58.102.0/24 Valid RIR databaseAPNIC 673 100% 66
202.58.103.0/24 Valid RIR databaseAPNIC 673 100% 67
45.121.46.0/24 Valid RIR databaseAPNIC 672 100% 66
103.61.132.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.68.220.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.68.221.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.209.96.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.209.97.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.12.109.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
45.121.44.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.121.45.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
223.31.160.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
2405:a700:21::/48 Valid RIR databaseAPNIC, RADB 635 100% 70
2405:a700:22::/48 Valid RIR databaseAPNIC, RADB 635 100% 69
2405:a700:14::/48 Valid RIR databaseAPNIC, RADB 633 100% 70
2405:a700:15::/48 Valid RIR databaseAPNIC, RADB 633 100% 70
2405:a700:1b::/48 Valid RIR databaseAPNIC, RADB 633 100% 70
2405:a700:1c::/48 Valid RIR databaseAPNIC, RADB 633 100% 70

AS-SET

AS45644 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 16 are in fix.csv.

  • Route object: not announced16

Route objects not announced

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

45.121.44.0/22APNICValid
45.121.44.0/23APNICValid
45.121.46.0/23APNICValid
45.121.47.0/24APNICValid
103.61.132.0/22APNICValid
103.61.132.0/23APNICValid
103.61.134.0/23APNICValid
103.61.134.0/24APNICValid
103.61.135.0/24APNICValid
103.68.220.0/23APNICValid
103.209.96.0/23APNICValid
202.58.102.0/23APNIC, RADBValid
2405:a700::/32APNICValid
2405:a700:20::/48APNICValid
2405:a700:23::/48APNICValid
2405:a700:24::/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.