bgpreport

Network · data from 2026-11-12

AS63844 ONCL-BD - One Net Communication Ltd

Registry name: ONCL-BD - One Net Communication Ltd, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS63844, 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.77.252.0/24 Valid RIR databaseAPNIC 673 100% 68
103.41.244.0/24 Valid RIR databaseAPNIC 672 100% 68
103.41.245.0/24 Valid RIR databaseAPNIC 672 100% 68
103.77.253.0/24 Valid RIR databaseAPNIC 672 100% 68
116.206.252.0/24 Valid RIR databaseAPNIC 672 100% 67
116.206.254.0/24 Valid RIR databaseAPNIC 672 100% 67
116.206.255.0/24 Valid RIR databaseAPNIC 672 100% 67
116.206.253.0/24 Valid RIR databaseAPNIC 669 99% 67

AS-SET

AS63844 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 36 are in fix.csv.

  • Route object: not announced36

Route objects not announced

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

103.41.244.0/23APNICValid
103.77.252.0/23APNICValid
116.206.252.0/22APNICValid
116.206.252.0/23APNICValid
116.206.254.0/23APNICValid
2405:9140::/32APNICValid
2405:9140::/33APNICValid
2405:9140::/34APNICValid
2405:9140::/35APNICValid
2405:9140::/36APNICValid
2405:9140:1000::/36APNICValid
2405:9140:2000::/35APNICValid
2405:9140:2000::/36APNICValid
2405:9140:3000::/36APNICValid
2405:9140:4000::/34APNICValid
2405:9140:4000::/35APNICValid
2405:9140:4000::/36APNICValid
2405:9140:5000::/36APNICValid
2405:9140:6000::/35APNICValid
2405:9140:6000::/36APNICValid
2405:9140:7000::/36APNICValid
2405:9140:8000::/33APNICValid
2405:9140:8000::/34APNICValid
2405:9140:8000::/35APNICValid
2405:9140:8000::/36APNICValid
2405:9140:9000::/36APNICValid
2405:9140:a000::/35APNICValid
2405:9140:a000::/36APNICValid
2405:9140:b000::/36APNICValid
2405:9140:c000::/34APNICValid
2405:9140:c000::/35APNICValid
2405:9140:c000::/36APNICValid
2405:9140:d000::/36APNICValid
2405:9140:e000::/35APNICValid
2405:9140:e000::/36APNICValid
2405:9140: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.