bgpreport

Network · data from 2026-11-12

AS134806 Sky View Online

Registry name: SKYVIEWONLINE-AS-AP - Skyview Online Ltd, BD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134806, 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.89.24.0/24 Invalid: origin Other origin only 0 0%low visibility 1
103.132.43.0/24 Valid Other origin only 672 100% 67
103.126.217.0/24 Valid RIR databaseAPNIC 673 100% 67
103.126.218.0/24 Valid RIR databaseAPNIC 673 100% 67
103.126.219.0/24 Valid RIR databaseAPNIC 673 100% 67
103.183.69.0/24 Valid RIR databaseAPNIC 673 100% 67
103.200.38.0/24 Valid RIR databaseAPNIC 673 100% 67
123.253.65.0/24 Valid RIR databaseAPNIC 673 100% 67
103.126.216.0/22 Valid RIR databaseAPNIC 672 100% 67
103.126.216.0/23 Valid RIR databaseAPNIC 672 100% 67
103.126.216.0/24 Valid RIR databaseAPNIC 672 100% 67
103.126.218.0/23 Valid RIR databaseAPNIC 672 100% 67
103.200.36.0/24 Valid RIR databaseAPNIC 672 100% 68
103.200.37.0/24 Valid RIR databaseAPNIC 672 100% 68
103.200.39.0/24 Valid RIR databaseAPNIC 672 100% 66
123.253.66.0/24 Valid RIR databaseAPNIC 672 100% 67
123.253.67.0/24 Valid RIR databaseAPNIC 672 100% 68
160.238.0.0/24 Valid RIR databaseAPNIC 672 100% 68
103.89.27.0/24 Valid RIR databaseAPNIC 669 99% 68
103.100.235.0/24 Valid RIR databaseAPNIC 669 99% 68
123.253.64.0/24 Valid RIR databaseAPNIC 669 99% 66
2401:1040::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:1::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:3::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:100::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:101::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:102::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:103::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:301::/48 Valid RIR databaseAPNIC 636 100% 70
2401:1040:8100::/40 Valid RIR databaseAPNIC 636 100% 70
2401:1040:2::/48 Valid RIR databaseAPNIC 635 100% 70
103.200.36.0/23 Valid RIR databaseAPNIC 0 0%low visibility 1

AS-SET

AS134806'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 13 are in fix.csv.

  • ROA: origin1
  • Route object: none2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin103.89.24.0/24ROAs covering it name AS151629, not AS134806. If AS134806 should announce it, add a ROA for AS134806.0 of 673
Route object: none103.89.24.0/24Route objects for it name AS151629. Add a route object with origin AS134806 in the RIR database for the space.0 of 673
Route object: none103.132.43.0/24Route objects for it name AS150731. Add a route object with origin AS134806 in the RIR database for the space.672 of 673

Route objects not announced

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

103.89.26.0/24APNICValid
103.200.36.0/22APNICValid
103.200.38.0/23APNICValid
123.253.64.0/22APNICValid
123.253.64.0/23APNICValid
123.253.66.0/23APNICValid
2401:1040::/32APNICValid
2401:1040::/40APNICValid
2401:1040:100::/40APNICValid
2401:1040:300::/40APNICValid

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.