bgpreport

Network · data from 2026-11-12

AS199925 Phan Nhat Nghi

Registry name: AZCOM-AS Phan Nhat Nghi, VG · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199925, 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.128.13.0/24 Invalid: origin Other origin only 2 0%low visibility 2
202.134.233.0/24 Invalid: origin Other origin only 2 0%low visibility 2
184.174.51.0/24 Invalid: origin Other origin only 1 0%low visibility 1
2a05:dfc1:5c00::/40 Valid RIR databaseRIPE 636 100% 68
2a05:dfc1:100::/40 Valid RIR databaseRIPE 635 100% 67
2a05:dfc1:3d00::/40 Valid RIR databaseRIPE 635 100% 67
2a05:dfc1:5100::/40 Valid RIR databaseRIPE 635 100% 67
2a05:dfc1:5200::/40 Valid RIR databaseRIPE 635 100% 67
2a05:dfc1:9900::/40 Valid RIR databaseRADB, RIPE 635 100% 69
2a0a:6040:8f00::/40 Valid RIR databaseRADB, RIPE 635 100% 67
2a05:dfc1:3700::/40 Valid RIR databaseRIPE 634 100% 67
2a12:d5c0::/29 Valid RIR databaseRIPE 633 100% 68
2a13:9b00::/29 Valid RIR databaseRIPE 632 99% 68

AS-SET

AS199925'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 15 are in fix.csv.

  • ROA: origin3
  • Route object: none3
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin45.128.13.0/24ROAs covering it name AS834, not AS199925. If AS199925 should announce it, add a ROA for AS199925.2 of 673
Route object: none45.128.13.0/24Route objects for it name AS834. Add a route object with origin AS199925 in the RIR database for the space.2 of 673
ROA: origin202.134.233.0/24ROAs covering it name AS13335, AS59117, AS135074, AS211392, not AS199925. If AS199925 should announce it, add a ROA for AS199925.2 of 673
Route object: none202.134.233.0/24Route objects for it name AS13335, AS59117, AS135074, AS211392. Add a route object with origin AS199925 in the RIR database for the space.2 of 673
ROA: origin184.174.51.0/24ROAs covering it name AS136809, AS402306, not AS199925. If AS199925 should announce it, add a ROA for AS199925.1 of 673
Route object: none184.174.51.0/24Route objects for it name AS136809, AS402306. Add a route object with origin AS199925 in the RIR database for the space.1 of 673

Route objects not announced

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

64.72.207.0/24RADBValid
2a13:2b40::/32RIPEInvalid: origin
2a13:2b41::/32RIPEInvalid: origin
2a13:2b42::/32RIPEInvalid: origin
2a13:2b43::/32RIPEInvalid: origin
2a13:2b44::/32RIPEInvalid: origin
2a13:2b45::/32RIPEInvalid: origin
2a13:2b46::/32RIPEInvalid: origin
2a13:2b47::/32RIPEInvalid: origin

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.