bgpreport

Network · data from 2026-11-12

AS134153 Xplore Net

Registry name: XPLORECYBERNET-AS-AP - Xplore Net BD, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134153, 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.138.24.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.176.19.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.96.104.0/23 Valid RIR databaseAPNIC 672 100% 67
103.96.105.0/24 Valid RIR databaseAPNIC 672 100% 68
103.96.106.0/23 Valid RIR databaseAPNIC 672 100% 67
103.96.106.0/24 Valid RIR databaseAPNIC 672 100% 67
103.96.107.0/24 Valid RIR databaseAPNIC 672 100% 68
103.138.26.0/24 Valid RIR databaseAPNIC 672 100% 68
103.138.27.0/24 Valid RIR databaseAPNIC 672 100% 68
103.96.104.0/24 Valid RIR databaseAPNIC 669 99% 68
103.176.18.0/24 Valid RIR databaseAPNIC 669 99% 68
2401:7c40::/32 Valid RIR databaseAPNIC 635 100% 69

AS-SET

AS134153'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 46 are in fix.csv.

  • ROA: origin2
  • Route object: none2
  • Route object: not announced42
ChangePrefix or setDetailFull-table peers
ROA: origin103.138.24.0/24ROAs covering it name AS134186, not AS134153. If AS134153 should announce it, add a ROA for AS134153.0 of 673
Route object: none103.138.24.0/24Route objects for it name AS134186. Add a route object with origin AS134153 in the RIR database for the space.0 of 673
ROA: origin103.176.19.0/24ROAs covering it name AS137453, not AS134153. If AS134153 should announce it, add a ROA for AS134153.0 of 673
Route object: none103.176.19.0/24Route objects for it name AS137453. Add a route object with origin AS134153 in the RIR database for the space.0 of 673

Route objects not announced

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

103.96.104.0/22APNICValid
2401:7c40::/48APNICValid
2401:7c40:1::/48APNICValid
2401:7c40:2::/48APNICValid
2401:7c40:3::/48APNICValid
2401:7c40:4::/48APNICValid
2401:7c40:5::/48APNICValid
2401:7c40:6::/48APNICValid
2401:7c40:7::/48APNICValid
2401:7c40:8::/48APNICValid
2401:7c40:9::/48APNICValid
2401:7c40:a::/48APNICValid
2401:7c40:b::/48APNICValid
2401:7c40:c::/48APNICValid
2401:7c40:d::/48APNICValid
2401:7c40:e::/48APNICValid
2401:7c40:f::/48APNICValid
2401:7c40:10::/48APNICValid
2401:7c40:11::/48APNICValid
2401:7c40:12::/48APNICValid
2401:7c40:13::/48APNICValid
2401:7c40:14::/48APNICValid
2401:7c40:15::/48APNICValid
2401:7c40:16::/48APNICValid
2401:7c40:17::/48APNICValid
2401:7c40:18::/48APNICValid
2401:7c40:19::/48APNICValid
2401:7c40:1a::/48APNICValid
2401:7c40:1b::/48APNICValid
2401:7c40:1c::/48APNICValid
2401:7c40:1d::/48APNICValid
2401:7c40:1f::/48APNICValid
2401:7c40:20::/48APNICValid
2401:7c40:21::/48APNICValid
2401:7c40:22::/48APNICValid
2401:7c40:23::/48APNICValid
2401:7c40:24::/48APNICValid
2401:7c40:25::/48APNICValid
2401:7c40:26::/48APNICValid
2401:7c40:27::/48APNICValid
2401:7c40:28::/48APNICValid
2401:7c40:29::/48APNICValid

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.