bgpreport

Network · data from 2026-11-12

AS45896 MobiFone Global and Technology Jsc

Registry name: MOBIFONEGLOBAL-AS-VN - Mobifone Global JSC, VN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45896, 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.

203.131.247.64/27 Invalid: origin None 0 0%low visibility 1
45.125.205.128/28 Invalid: maxLength Nonecovered by 45.125.205.0/24 0 0%low visibility 1
45.125.211.96/28 Invalid: maxLength Nonecovered by 45.125.211.0/24 0 0%low visibility 1
103.19.166.104/29 Invalid: maxLength Nonecovered by 103.19.166.0/24 0 0%low visibility 1
103.37.33.48/28 Invalid: maxLength Nonecovered by 103.37.33.0/24 0 0%low visibility 1
2406:51c0::/32 No ROA Other IRR onlyNTTCOM 635 100% 69
103.37.29.0/24 Valid RIR databaseAPNIC, NTTCOM 673 100% 66
103.38.136.0/22 Valid RIR databaseAPNIC 673 100% 66
103.38.136.0/24 Valid RIR databaseAPNIC 673 100% 66
111.91.234.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 66
45.125.209.0/24 Valid RIR databaseAPNIC, NTTCOM 672 100% 66
103.19.164.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
111.91.233.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
45.125.200.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
45.125.204.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
45.125.208.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.19.166.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
103.19.167.0/24 Valid RIR databaseAPNIC 671 100% 67
103.37.28.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.28.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.30.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.31.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.32.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.32.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.33.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.34.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.37.35.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.38.137.0/24 Valid RIR databaseAPNIC 671 100% 67
103.38.138.0/24 Valid RIR databaseAPNIC 671 100% 67
103.38.139.0/24 Valid RIR databaseAPNIC 671 100% 67
103.234.88.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.234.89.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.234.90.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.234.91.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.237.64.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.237.64.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.237.65.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.237.66.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.237.67.0/24 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
111.91.235.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 671 100% 67
45.125.200.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.201.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.202.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.203.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.204.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.205.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.206.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.207.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.208.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.210.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
45.125.211.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
103.19.164.0/22 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
103.19.165.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
103.234.88.0/24 Valid RIR databaseAPNIC, NTTCOM 670 100% 67
111.91.232.0/24 Valid RIR databaseAPNIC, RADB 670 100% 67
2001:df0:2e8::/48 Valid RIR databaseAPNIC, NTTCOM 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS45896: AS45896:AS-DS. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS45896 isn't in the set, or no route object for AS45896 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS45896 in itNot covered
AS45896:AS-DS NTTCOMlists itself further down 2452100,967 Yes 5

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

  • ROA: origin1
  • ROA: maxLength4
  • ROA: none1
  • Route object: none5
  • Route object: RIR1
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: origin203.131.247.64/27ROAs covering it name AS2914, not AS45896. If AS45896 should announce it, add a ROA for AS45896.0 of 673
Route object: none203.131.247.64/27No route object for it. Add a route object with origin AS45896 in the RIR database for the space.0 of 673
ROA: maxLength45.125.205.128/28ROA 45.125.204.0/22 AS45896 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 45.125.205.128/28.0 of 673
Route object: none45.125.205.128/28No route object for it. A route object for 45.125.205.0/24 with origin AS45896 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45896 in the RIR database for the space.0 of 673
ROA: maxLength45.125.211.96/28ROA 45.125.208.0/22 AS45896 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 45.125.211.96/28.0 of 673
Route object: none45.125.211.96/28No route object for it. A route object for 45.125.211.0/24 with origin AS45896 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45896 in the RIR database for the space.0 of 673
ROA: maxLength103.19.166.104/29ROA 103.19.164.0/22 AS45896 has maxLength 24; the route is a /29. Raise the maxLength, or add a ROA for 103.19.166.104/29.0 of 673
Route object: none103.19.166.104/29No route object for it. A route object for 103.19.166.0/24 with origin AS45896 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45896 in the RIR database for the space.0 of 673
ROA: maxLength103.37.33.48/28ROA 103.37.32.0/22 AS45896 has maxLength 24; the route is a /28. Raise the maxLength, or add a ROA for 103.37.33.48/28.0 of 673
Route object: none103.37.33.48/28No route object for it. A route object for 103.37.33.0/24 with origin AS45896 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS45896 in the RIR database for the space.0 of 673
ROA: none2406:51c0::/32No ROA covers it. Add a ROA for AS45896, maxLength 32.635 of 636
Route object: RIR2406:51c0::/32Route object only in NTTCOM. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

45.125.200.0/23APNICValid
45.125.202.0/23APNICValid
45.125.204.0/23APNICValid
45.125.206.0/23APNICValid
45.125.208.0/23APNICValid
45.125.210.0/23APNICValid
103.19.164.0/23APNICValid
103.19.166.0/23APNICValid
103.37.28.0/23APNICValid
103.37.30.0/23APNICValid
103.37.32.0/23APNICValid
103.37.34.0/23APNICValid
103.38.136.0/23APNICValid
103.38.138.0/23APNICValid
103.234.88.0/23APNICValid
103.234.90.0/23APNICValid
103.237.64.0/23APNICValid
103.237.66.0/23APNICValid
111.91.232.0/22APNICValid
111.91.232.0/23APNICValid
111.91.234.0/23APNICValid

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.