Network · data from 2026-11-12

AS24122 BDCOM Online

Registry name: BDCOM-BD-AS-AP - BDCOM Online Limited, BD · PeeringDB

48IPv4 routes 100.0% RPKI valid · 97.9% with a route object

4IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 1 with no route object for this origin

7Low visibility seen by under 10% of full-table peers

11Route objects not announced registered with origin AS24122, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS24122, 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.


210.4.68.0/23	Valid	Other origin onlycovered by 210.4.64.0/21	0 0%low visibility	1
43.243.204.0/24	Valid	RIR databaseAPNIC	672 100%	67
43.243.205.0/24	Valid	RIR databaseAPNIC	672 100%	67
43.243.206.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.16.73.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.16.75.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.80.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.82.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.84.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.89.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.90.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.91.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.93.0/24	Valid	RIR databaseAPNIC	672 100%	67
119.40.95.0/24	Valid	RIR databaseAPNIC	672 100%	67
43.243.206.0/23	Valid	RIR databaseAPNIC	671 100%	67
43.243.207.0/24	Valid	RIR databaseAPNIC	671 100%	67
103.16.72.0/24	Valid	RIR databaseAPNIC	671 100%	67
103.16.74.0/24	Valid	RIR databaseAPNIC	671 100%	67
119.40.80.0/20	Valid	RIR databaseAPNIC, RADB	671 100%	67
119.40.81.0/24	Valid	RIR databaseAPNIC	671 100%	67
119.40.83.0/24	Valid	RIR databaseAPNIC	671 100%	67
119.40.85.0/24	Valid	RIR databaseAPNIC	671 100%	67
119.40.86.0/24	Valid	RIR databaseAPNIC	671 100%	67
119.40.87.0/24	Valid	RIR databaseAPNIC	671 100%	67
119.40.94.0/24	Valid	RIR databaseAPNIC	671 100%	66
210.4.64.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.65.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.67.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.70.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.71.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.74.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.77.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.78.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.79.0/24	Valid	RIR databaseAPNIC	671 100%	67
210.4.66.0/23	Valid	RIR databaseAPNIC	670 100%	67
210.4.66.0/24	Valid	RIR databaseAPNIC	670 100%	67
210.4.68.0/24	Valid	RIR databaseAPNIC	670 100%	67
210.4.69.0/24	Valid	RIR databaseAPNIC	670 100%	67
210.4.72.0/24	Valid	RIR databaseAPNIC	670 100%	67
210.4.73.0/24	Valid	RIR databaseAPNIC	670 100%	67
210.4.75.0/24	Valid	RIR databaseAPNIC	670 100%	67
210.4.76.0/24	Valid	RIR databaseAPNIC	670 100%	67
2403:4000::/32	Valid	RIR databaseAPNIC	635 100%	69
2403:4000:17::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:4000:18::/48	Valid	RIR databaseAPNIC	635 100%	69
2403:4000:19::/48	Valid	RIR databaseAPNIC	635 100%	69
119.40.80.0/21	Valid	RIR databaseAPNIC	0 0%low visibility	1
119.40.88.0/21	Valid	RIR databaseAPNIC	0 0%low visibility	1
119.40.88.0/22	Valid	RIR databaseAPNIC	0 0%low visibility	1
119.40.88.0/24	Valid	RIR databaseAPNIC	0 0%low visibility	1
210.4.64.0/20	Valid	RIR databaseAPNIC, RADB	0 0%low visibility	1
210.4.74.0/23	Valid	RIR databaseAPNIC	0 0%low visibility	1

210.4.68.0/23

Valid

Other origin onlycovered by 210.4.64.0/21

0 0%low visibility

43.243.204.0/24

Valid

RIR databaseAPNIC

672 100%

43.243.205.0/24

Valid

RIR databaseAPNIC

672 100%

43.243.206.0/24

Valid

RIR databaseAPNIC

672 100%

103.16.73.0/24

Valid

RIR databaseAPNIC

672 100%

103.16.75.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.80.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.82.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.84.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.89.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.90.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.91.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.93.0/24

Valid

RIR databaseAPNIC

672 100%

119.40.95.0/24

Valid

RIR databaseAPNIC

672 100%

43.243.206.0/23

Valid

RIR databaseAPNIC

671 100%

43.243.207.0/24

Valid

RIR databaseAPNIC

671 100%

103.16.72.0/24

Valid

RIR databaseAPNIC

671 100%

103.16.74.0/24

Valid

RIR databaseAPNIC

671 100%

119.40.80.0/20

Valid

RIR databaseAPNIC, RADB

671 100%

119.40.81.0/24

Valid

RIR databaseAPNIC

671 100%

119.40.83.0/24

Valid

RIR databaseAPNIC

671 100%

119.40.85.0/24

Valid

RIR databaseAPNIC

671 100%

119.40.86.0/24

Valid

RIR databaseAPNIC

671 100%

119.40.87.0/24

Valid

RIR databaseAPNIC

671 100%

119.40.94.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.64.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.65.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.67.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.70.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.71.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.74.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.77.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.78.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.79.0/24

Valid

RIR databaseAPNIC

671 100%

210.4.66.0/23

Valid

RIR databaseAPNIC

670 100%

210.4.66.0/24

Valid

RIR databaseAPNIC

670 100%

210.4.68.0/24

Valid

RIR databaseAPNIC

670 100%

210.4.69.0/24

Valid

RIR databaseAPNIC

670 100%

210.4.72.0/24

Valid

RIR databaseAPNIC

670 100%

210.4.73.0/24

Valid

RIR databaseAPNIC

670 100%

210.4.75.0/24

Valid

RIR databaseAPNIC

670 100%

210.4.76.0/24

Valid

RIR databaseAPNIC

670 100%

2403:4000::/32

Valid

RIR databaseAPNIC

635 100%

2403:4000:17::/48

Valid

RIR databaseAPNIC

635 100%

2403:4000:18::/48

Valid

RIR databaseAPNIC

635 100%

2403:4000:19::/48

Valid

RIR databaseAPNIC

635 100%

119.40.80.0/21

Valid

RIR databaseAPNIC

0 0%low visibility

119.40.88.0/21

Valid

RIR databaseAPNIC

0 0%low visibility

119.40.88.0/22

Valid

RIR databaseAPNIC

0 0%low visibility

119.40.88.0/24

Valid

RIR databaseAPNIC

0 0%low visibility

210.4.64.0/20

Valid

RIR databaseAPNIC, RADB

0 0%low visibility

210.4.74.0/23

Valid

RIR databaseAPNIC

0 0%low visibility

AS-SET

AS24122'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 12 are in fix.csv.

Route object: none1
Route object: not announced11

Change	Prefix or set	Detail	Full-table peers
Route object: none	210.4.68.0/23	Route objects for it name AS4628. A route object for 210.4.64.0/21 with origin AS24122 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24122 in the RIR database for the space.	0 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: none

210.4.68.0/23

Route objects for it name AS4628. A route object for 210.4.64.0/21 with origin AS24122 covers it (filters allowing more-specifics accept it). Add a route object with origin AS24122 in the RIR database for the space.

0 of 673

Route objects not announced

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


43.243.204.0/23	APNIC	Valid
103.16.72.0/22	APNIC	Valid
103.16.72.0/23	APNIC	Valid
103.16.74.0/23	APNIC	Valid
119.40.80.0/23	APNIC	Valid
119.40.84.0/23	APNIC	Valid
119.40.92.0/22	APNIC, RADB	Valid
119.40.92.0/24	APNIC	Valid
210.4.64.0/21	APNIC, RADB	Valid
210.4.70.0/23	APNIC, RADB	Valid
210.4.72.0/21	APNIC, RADB	Valid

43.243.204.0/23

APNIC

Valid

103.16.72.0/22

APNIC

Valid

103.16.72.0/23

APNIC

Valid

103.16.74.0/23

APNIC

Valid

119.40.80.0/23

APNIC

Valid

119.40.84.0/23

APNIC

Valid

119.40.92.0/22

APNIC, RADB

Valid

119.40.92.0/24

APNIC

Valid

210.4.64.0/21

APNIC, RADB

Valid

210.4.70.0/23

APNIC, RADB

Valid

210.4.72.0/21

APNIC, RADB

Valid

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.