Network · data from 2026-11-12

AS38592 Chittagong Online

Registry name: CTGONLINE-AS-AP - Chittagong Online Limited AS38592 AP, BD · PeeringDB

43IPv4 routes 100.0% RPKI valid · 100.0% with a route object

5IPv6 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

21Route objects not announced registered with origin AS38592, seen from no peer

Announced routes

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


119.10.168.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	67
101.2.160.0/21	Valid	RIR databaseAPNIC, RADB	672 100%	66
101.2.160.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
101.2.161.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
101.2.163.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
101.2.164.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
101.2.165.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
101.2.166.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
101.2.167.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
103.5.232.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	66
103.5.232.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
103.5.233.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
103.5.234.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
103.5.235.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	66
119.10.168.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	66
119.10.169.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
119.10.170.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
119.10.172.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	66
119.10.172.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
119.10.175.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
163.47.84.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	66
163.47.84.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
163.47.85.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
163.47.86.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
163.47.87.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
202.65.168.0/21	Valid	RIR databaseAPNIC, NTTCOM, RADB	672 100%	66
202.65.168.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
202.65.169.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
202.65.170.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
202.65.171.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
202.65.175.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
203.80.188.0/22	Valid	RIR databaseAPNIC, RADB	672 100%	66
203.80.188.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
203.80.189.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
203.80.190.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
203.80.191.0/24	Valid	RIR databaseAPNIC, RADB	672 100%	67
101.2.162.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	68
119.10.171.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	68
119.10.173.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	68
119.10.174.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	68
202.65.172.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	68
202.65.173.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	68
202.65.174.0/24	Valid	RIR databaseAPNIC, RADB	670 100%	68
2402:2300::/32	Valid	RIR databaseAPNIC, RADB	635 100%	69
2402:2300:1211::/48	Valid	RIR databaseAPNIC, RADB	635 100%	69
2402:2300:1212::/48	Valid	RIR databaseAPNIC	635 100%	69
2402:2300:1215::/48	Valid	RIR databaseAPNIC	635 100%	69
2402:2300:1220::/44	Valid	RIR databaseAPNIC	635 100%	69

AS-SET

AS38592'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 21 are in fix.csv.

Route object: not announced21

Route objects not announced

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


101.2.160.0/22	APNIC	Valid
101.2.160.0/23	APNIC	Valid
101.2.162.0/23	APNIC	Valid
101.2.164.0/22	APNIC	Valid
101.2.164.0/23	APNIC	Valid
101.2.166.0/23	APNIC	Valid
103.5.232.0/23	APNIC	Valid
103.5.234.0/23	APNIC	Valid
119.10.172.0/23	APNIC	Valid
119.10.174.0/23	APNIC	Valid
163.47.84.0/23	APNIC	Valid
163.47.86.0/23	APNIC	Valid
202.65.168.0/22	APNIC, RADB	Valid
202.65.168.0/23	APNIC	Valid
202.65.170.0/23	APNIC	Valid
202.65.172.0/22	APNIC	Valid
202.65.172.0/23	APNIC, RADB	Valid
202.65.174.0/23	APNIC	Valid
203.80.188.0/23	APNIC	Valid
203.80.190.0/23	APNIC	Valid
2402:2300::/48	APNIC, RADB	Valid

101.2.160.0/22

APNIC

Valid

101.2.160.0/23

APNIC

Valid

101.2.162.0/23

APNIC

Valid

101.2.164.0/22

APNIC

Valid

101.2.164.0/23

APNIC

Valid

101.2.166.0/23

APNIC

Valid

103.5.232.0/23

APNIC

Valid

103.5.234.0/23

APNIC

Valid

119.10.172.0/23

APNIC

Valid

119.10.174.0/23

APNIC

Valid

163.47.84.0/23

APNIC

Valid

163.47.86.0/23

APNIC

Valid

202.65.168.0/22

APNIC, RADB

Valid

202.65.168.0/23

APNIC

Valid

202.65.170.0/23

APNIC

Valid

202.65.172.0/22

APNIC

Valid

202.65.172.0/23

APNIC, RADB

Valid

202.65.174.0/23

APNIC

Valid

203.80.188.0/23

APNIC

Valid

203.80.190.0/23

APNIC

Valid

2402:2300::/48

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.