bgpreport

Network · data from 2026-11-12

AS63760 AZDIGI Corporation

Registry name: AZDIGI-AS-VN - AZDIGI Corporation, VN · PeeringDB

5IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
14Route objects not announced registered with origin AS63760, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63760, 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.
45.252.248.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 670 100% 67
103.110.84.0/22 Valid RIR databaseAPNIC, NTTCOM 669 99% 67
103.221.220.0/22 Valid RIR databaseAPNIC, NTTCOM 669 99% 67
116.118.48.0/22 Valid RIR databaseAPNIC 669 99% 67
157.10.200.0/23 Valid RIR databaseAPNIC 669 99% 67

AS-SET

AS63760'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 14 are in fix.csv.

  • Route object: not announced14

Route objects not announced

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

45.252.248.0/23APNIC, NTTCOM, RADBValid
45.252.248.0/24APNIC, NTTCOM, RADBValid
45.252.249.0/24APNIC, NTTCOM, RADBValid
45.252.250.0/23APNIC, NTTCOM, RADBValid
45.252.250.0/24APNIC, NTTCOM, RADBValid
45.252.251.0/24APNIC, NTTCOM, RADBValid
116.118.48.0/23APNICValid
116.118.48.0/24APNICValid
116.118.49.0/24APNICValid
116.118.50.0/23APNICValid
116.118.50.0/24APNICValid
116.118.51.0/24APNICValid
2401:75e0::/48APNICValid
2401:f2c0::/32NTTCOM, RADBNo ROA

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.