bgpreport

Network · data from 2026-11-12

AS136184 Y LINX (PVT.) LIMITED

Registry name: YLINX-AS-AP - Y LINX (PVT.) LIMITED, PK · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS136184, 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.
149.112.56.0/24 Invalid: origin None 52 8%low visibility 33
149.112.57.0/24 Invalid: origin None 52 8%low visibility 33
2607:df80::/32 No ROA Other IRR onlyRADB 634 100% 70
103.84.52.0/24 No ROA RIR databaseAPNIC 671 100% 67
2400:90c0::/32 No ROA RIR databaseAPNIC, RADB 634 100% 70
103.84.55.0/24 Valid RIR databaseAPNIC 673 100% 68
45.120.196.0/22 Valid RIR databaseAPNIC 672 100% 66
103.83.89.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
103.83.91.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
185.228.92.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
185.228.93.0/24 Valid RIR databaseRADB, RIPE 671 100% 67

AS-SET

AS136184'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 21 are in fix.csv.

  • ROA: origin2
  • ROA: none3
  • Route object: none2
  • Route object: RIR1
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: origin149.112.56.0/24ROAs covering it name AS395734, not AS136184. If AS136184 should announce it, add a ROA for AS136184.52 of 673
Route object: none149.112.56.0/24No route object for it. Add a route object with origin AS136184 in the RIR database for the space.52 of 673
ROA: origin149.112.57.0/24ROAs covering it name AS395734, not AS136184. If AS136184 should announce it, add a ROA for AS136184.52 of 673
Route object: none149.112.57.0/24No route object for it. Add a route object with origin AS136184 in the RIR database for the space.52 of 673
ROA: none2607:df80::/32No ROA covers it. Add a ROA for AS136184, maxLength 32.634 of 636
Route object: RIR2607:df80::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
ROA: none103.84.52.0/24No ROA covers it. Add a ROA for AS136184, maxLength 24.671 of 673
ROA: none2400:90c0::/32No ROA covers it. Add a ROA for AS136184, maxLength 32.634 of 636

Route objects not announced

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

45.120.196.0/23APNICValid
45.120.196.0/24APNICValid
45.120.197.0/24APNICValid
45.120.198.0/23APNICValid
45.120.198.0/24APNICValid
45.120.199.0/24APNICValid
103.83.88.0/22APNIC, RADBValid
103.83.88.0/24APNICValid
103.83.90.0/24APNICValid
103.84.52.0/22RADBNo ROA
185.228.92.0/22RADBValid
185.228.94.0/24RADB, RIPEValid
185.228.95.0/24RADB, RIPEValid

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.