bgpreport

Network · data from 2026-11-12

AS136395 EXPERT-AS-AP - Mahfujul Haque t/a Expert Online

Registry name: EXPERT-AS-AP - Mahfujul Haque t/a Expert Online, BD · not in PeeringDB

11IPv4 routes 100.0% RPKI valid · 100.0% with a route object
8IPv6 routes 100.0% RPKI valid · 100.0% with a route object
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
112Route objects not announced registered with origin AS136395, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS136395, 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.
103.86.108.0/24 Valid RIR databaseAPNIC 673 100% 69
103.86.109.0/24 Valid RIR databaseAPNIC 673 100% 69
103.213.36.0/24 Valid RIR databaseAPNIC 673 100% 69
202.181.5.0/24 Valid RIR databaseAPNIC 673 100% 69
202.181.6.0/24 Valid RIR databaseAPNIC 673 100% 69
202.181.7.0/24 Valid RIR databaseAPNIC 673 100% 69
103.86.110.0/24 Valid RIR databaseAPNIC 672 100% 67
103.86.111.0/24 Valid RIR databaseAPNIC 672 100% 67
103.179.54.0/24 Valid RIR databaseAPNIC 672 100% 67
103.213.37.0/24 Valid RIR databaseAPNIC 672 100% 67
202.181.4.0/24 Valid RIR databaseAPNIC 672 100% 67
2400:bcc0:1000::/36 Valid RIR databaseAPNIC 631 99% 67
2400:bcc0:1003::/48 Valid RIR databaseAPNIC 631 99% 67
2400:bcc0:1006::/48 Valid RIR databaseAPNIC 631 99% 67
2400:bcc0:1016::/48 Valid RIR databaseAPNIC 631 99% 67
2400:bcc0:1017::/48 Valid RIR databaseAPNIC 631 99% 67
2400:bcc0:101d::/48 Valid RIR databaseAPNIC 631 99% 67
2400:bcc0:1022::/48 Valid RIR databaseAPNIC 631 99% 67
2400:bcc0:4000::/36 Valid RIR databaseAPNIC 631 99% 67

AS-SET

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

  • Route object: not announced112

Route objects not announced

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

103.86.108.0/22APNICValid
103.86.108.0/23APNICValid
103.213.36.0/23APNICValid
202.181.4.0/22APNICValid
202.181.4.0/23APNICValid
202.181.6.0/23APNICValid
2001:df0:48c0::/48APNICValid
2001:df0:48c0::/49APNICValid
2001:df0:48c0:8000::/49APNICValid
2400:bcc0::/32APNICValid
2400:bcc0::/36APNICValid
2400:bcc0:1::/48APNICValid
2400:bcc0:2::/48APNICValid
2400:bcc0:3::/48APNICValid
2400:bcc0:4::/48APNICValid
2400:bcc0:9::/48APNICValid
2400:bcc0:1000::/48APNICValid
2400:bcc0:1001::/48APNICValid
2400:bcc0:1002::/48APNICValid
2400:bcc0:1004::/48APNICValid
2400:bcc0:1005::/48APNICValid
2400:bcc0:1007::/48APNICValid
2400:bcc0:1008::/48APNICValid
2400:bcc0:1009::/48APNICValid
2400:bcc0:100a::/48APNICValid
2400:bcc0:100b::/48APNICValid
2400:bcc0:100c::/48APNICValid
2400:bcc0:1010::/48APNICValid
2400:bcc0:1011::/48APNICValid
2400:bcc0:101c::/48APNICValid
2400:bcc0:1023::/48APNICValid
2400:bcc0:1028::/48APNICValid
2400:bcc0:1029::/48APNICValid
2400:bcc0:102e::/48APNICValid
2400:bcc0:1033::/48APNICValid
2400:bcc0:1034::/48APNICValid
2400:bcc0:2000::/36APNICValid
2400:bcc0:3000::/36APNICValid
2400:bcc0:3001::/48APNICValid
2400:bcc0:3002::/48APNICValid
2400:bcc0:3003::/48APNICValid
2400:bcc0:3004::/48APNICValid
2400:bcc0:3005::/48APNICValid
2400:bcc0:3006::/48APNICValid
2400:bcc0:300b::/48APNICValid
2400:bcc0:300c::/48APNICValid
2400:bcc0:3010::/48APNICValid
2400:bcc0:3011::/48APNICValid
2400:bcc0:3016::/48APNICValid
2400:bcc0:3017::/48APNICValid
2400:bcc0:301c::/48APNICValid
2400:bcc0:301d::/48APNICValid
2400:bcc0:3022::/48APNICValid
2400:bcc0:3023::/48APNICValid
2400:bcc0:3028::/48APNICValid
2400:bcc0:3029::/48APNICValid
2400:bcc0:302e::/48APNICValid
2400:bcc0:5000::/36APNICValid
2400:bcc0:6000::/36APNICValid
2400:bcc0:7000::/36APNICValid
2400:bcc0:8000::/36APNICValid
2400:bcc0:9000::/36APNICValid
2400:bcc0:a000::/36APNICValid
2400:bcc0:b000::/36APNICValid
2400:bcc0:c000::/36APNICValid
2400:bcc0:d000::/36APNICValid
2400:bcc0:e000::/36APNICValid
2400:bcc0:f000::/36APNICValid
2401:5e0::/32APNICValid
2401:5e0::/36APNICValid
2401:5e0:1::/48APNICValid
2401:5e0:2::/48APNICValid
2401:5e0:3::/48APNICValid
2401:5e0:4::/48APNICValid
2401:5e0:1000::/36APNICValid
2401:5e0:1000::/48APNICValid
2401:5e0:1001::/48APNICValid
2401:5e0:1002::/48APNICValid
2401:5e0:1003::/48APNICValid
2401:5e0:1004::/48APNICValid
2401:5e0:1005::/48APNICValid
2401:5e0:1006::/48APNICValid
2401:5e0:1007::/48APNICValid
2401:5e0:1008::/48APNICValid
2401:5e0:1009::/48APNICValid
2401:5e0:100a::/48APNICValid
2401:5e0:100b::/48APNICValid
2401:5e0:100c::/48APNICValid
2401:5e0:100d::/48APNICValid
2401:5e0:100e::/48APNICValid
2401:5e0:100f::/48APNICValid
2401:5e0:1010::/48APNICValid
2401:5e0:2000::/36APNICValid
2401:5e0:2000::/48APNICValid
2401:5e0:2001::/48APNICValid
2401:5e0:2002::/48APNICValid
2401:5e0:2003::/48APNICValid
2401:5e0:2004::/48APNICValid
2401:5e0:2005::/48APNICValid
2401:5e0:3000::/36APNICValid
2401:5e0:4000::/36APNICValid
2401:5e0:5000::/36APNICValid
2401:5e0:6000::/36APNICValid
2401:5e0:7000::/36APNICValid
2401:5e0:8000::/36APNICValid
2401:5e0:9000::/36APNICValid
2401:5e0:a000::/36APNICValid
2401:5e0:b000::/36APNICValid
2401:5e0:c000::/36APNICValid
2401:5e0:d000::/36APNICValid
2401:5e0:e000::/36APNICValid
2401:5e0:f000::/36APNICValid

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.