bgpreport

Network · data from 2026-11-12

AS996 JY-MOBILE-COMMUNICATIONS - JY Mobile Communications

Registry name: JY-MOBILE-COMMUNICATIONS - JY Mobile Communications, US · not in PeeringDB

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

Announced routes

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

2a0b:d503::/32 Valid Nonecovered by 2a0b:d500::/29 605 95% 67
2a0b:d504::/32 Valid Nonecovered by 2a0b:d500::/29 605 95% 67
2a0b:d505::/32 Valid Nonecovered by 2a0b:d500::/29 605 95% 67
167.253.61.0/24 Valid Other IRR onlyRADB 669 99% 67
2a0a:ba03::/32 Valid Other IRR onlyRADB 605 95% 67
66.207.176.0/22 Valid RIR databaseARIN, RADB 671 100% 67
66.207.184.0/22 Valid RIR databaseARIN, RADB 671 100% 67
82.24.0.0/22 Valid RIR databaseRADB, RIPE 669 99% 67
167.148.130.0/23 Valid RIR databaseRADB, RIPE 669 99% 67
217.77.16.0/21 Valid RIR databaseRADB, RIPE 668 99% 67

AS-SET

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

  • Route object: none3
  • Route object: RIR2
  • Route object: not announced48
ChangePrefix or setDetailFull-table peers
Route object: none2a0b:d503::/32No route object for it. A route object for 2a0b:d500::/29 with origin AS996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS996 in the RIR database for the space.605 of 636
Route object: none2a0b:d504::/32No route object for it. A route object for 2a0b:d500::/29 with origin AS996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS996 in the RIR database for the space.605 of 636
Route object: none2a0b:d505::/32No route object for it. A route object for 2a0b:d500::/29 with origin AS996 covers it (filters allowing more-specifics accept it). Add a route object with origin AS996 in the RIR database for the space.605 of 636
Route object: RIR167.253.61.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2a0a:ba03::/32Route object only in RADB. Add it in the RIR database for the space.605 of 636

Route objects not announced

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

37.19.64.0/22RADBValid
37.218.208.0/21RADB, RIPEValid
37.218.208.0/24RIPEValid
77.47.180.0/22RADB, RIPEValid
81.22.131.0/24RADB, RIPEValid
84.32.136.0/22RADB, RIPEValid
88.216.248.0/22RADB, RIPEValid
89.34.224.0/23RADB, RIPEValid
89.42.143.0/24RADB, RIPEValid
89.46.0.0/24RADB, RIPEValid
89.47.127.0/24RADB, RIPEValid
89.185.86.0/23RADBNo ROA
92.51.44.0/22RADBNo ROA
109.172.74.0/23RADBNo ROA
109.172.84.0/22RADBNo ROA
149.62.32.0/22RADBNo ROA
157.254.34.0/23ARIN, RADBValid
175.29.128.0/21APNIC, RADBValid
175.29.128.0/22APNICValid
175.29.128.0/23APNICValid
175.29.128.0/24APNICValid
175.29.129.0/24APNICValid
175.29.130.0/23APNICValid
175.29.130.0/24APNICValid
175.29.131.0/24APNICValid
175.29.132.0/22APNICValid
175.29.132.0/23APNICValid
175.29.132.0/24APNICValid
175.29.133.0/24APNICValid
175.29.134.0/23APNICValid
175.29.134.0/24APNICValid
175.29.135.0/24APNICValid
176.46.140.0/22RADBNo ROA
176.46.144.0/20RADBNo ROA
178.92.80.0/24RADB, RIPEValid
178.92.82.0/24RADB, RIPEValid
188.191.100.0/24RADB, RIPEValid
188.191.106.0/24RADB, RIPEValid
192.228.126.0/23ARIN, RADBValid
193.163.45.0/24RADBNo ROA
193.233.120.0/22RADBNo ROA
207.170.172.0/22ARINValid
212.111.211.0/24RADBValid
217.144.55.0/24RADBNo ROA
2a0a:ba00::/29RADB, RIPEValid
2a0b:d500::/29RADBValid
2a0b:d500::/32RADBValid
2a0b:d501::/32RADBValid

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.