Network · data from 2026-11-12

AS55839 Microsense

Registry name: MICROSENSE-AS-AP - Microsense Private Limited, IN · PeeringDB

39IPv4 routes 97.4% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

1No ROA 0 with no route object for this origin

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

29Route objects not announced registered with origin AS55839, seen from no peer

Announced routes

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


43.245.138.0/24	No ROA	RIR databaseAPNIC	673 100%	67
43.245.136.0/24	Valid	RIR databaseAPNIC	673 100%	67
43.245.137.0/24	Valid	RIR databaseAPNIC	673 100%	67
43.245.139.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.51.235.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.234.156.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.234.157.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.234.158.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.240.100.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.240.101.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.240.102.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.240.103.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.241.141.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.241.142.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.241.143.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.244.168.0/24	Valid	RIR databaseAPNIC	673 100%	66
103.244.169.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.244.170.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.244.171.0/24	Valid	RIR databaseAPNIC	673 100%	67
116.212.176.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	67
116.212.178.0/24	Valid	RIR databaseAPNIC	673 100%	67
116.212.180.0/24	Valid	RIR databaseAPNIC	673 100%	67
116.212.181.0/24	Valid	RIR databaseAPNIC	673 100%	67
116.212.182.0/24	Valid	RIR databaseAPNIC	673 100%	67
116.212.183.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	67
150.107.192.0/24	Valid	RIR databaseAPNIC	673 100%	67
150.107.193.0/24	Valid	RIR databaseAPNIC	673 100%	67
150.107.194.0/24	Valid	RIR databaseAPNIC	673 100%	67
150.107.195.0/24	Valid	RIR databaseAPNIC	673 100%	67
163.47.208.0/24	Valid	RIR databaseAPNIC	673 100%	67
163.47.209.0/24	Valid	RIR databaseAPNIC	673 100%	67
163.47.210.0/24	Valid	RIR databaseAPNIC	673 100%	67
163.47.211.0/24	Valid	RIR databaseAPNIC	673 100%	67
103.51.236.0/24	Valid	RIR databaseAPNIC	672 100%	67
103.184.22.0/23	Valid	RIR databaseAPNIC	672 100%	67
103.234.159.0/24	Valid	RIR databaseAPNIC	672 100%	67
116.212.179.0/24	Valid	RIR databaseAPNIC	670 100%	67
103.241.140.0/24	Valid	RIR databaseAPNIC	669 99%	66
116.212.177.0/24	Valid	RIR databaseAPNIC	585 87%	66

AS-SET

AS55839'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 30 are in fix.csv.

ROA: none1
Route object: not announced29

Change	Prefix or set	Detail	Full-table peers
ROA: none	43.245.138.0/24	No ROA covers it. Add a ROA for AS55839, maxLength 24.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

43.245.138.0/24

No ROA covers it. Add a ROA for AS55839, maxLength 24.

673 of 673

Route objects not announced

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


103.184.22.0/24	APNIC	Valid
103.184.23.0/24	APNIC	Valid
103.234.156.0/22	APNIC	Valid
103.234.156.0/23	APNIC	Valid
103.234.158.0/23	APNIC	Valid
103.240.100.0/22	APNIC	Valid
103.240.100.0/23	APNIC	Valid
103.240.102.0/23	APNIC	Valid
103.241.140.0/22	APNIC	Valid
103.241.140.0/23	APNIC	Valid
103.241.142.0/23	APNIC	Valid
103.244.168.0/22	APNIC	Valid
103.244.168.0/23	APNIC	Valid
103.244.170.0/23	APNIC	Valid
116.212.176.0/21	APNIC	Valid
116.212.176.0/22	APNIC	Valid
116.212.176.0/23	APNIC	Valid
116.212.178.0/23	APNIC	Valid
116.212.180.0/22	APNIC	Valid
116.212.180.0/23	APNIC	Valid
116.212.182.0/23	APNIC	Valid
163.47.208.0/22	APNIC	Valid
163.47.208.0/23	APNIC	Valid
163.47.210.0/23	APNIC	Valid
202.131.156.0/24	APNIC	Valid
202.131.158.0/24	APNIC	Valid
2406:b500::/32	APNIC	Valid
2406:b500::/36	APNIC	Invalid: maxLength
2406:b500:1000::/36	APNIC	Invalid: maxLength

103.184.22.0/24

APNIC

Valid

103.184.23.0/24

APNIC

Valid

103.234.156.0/22

APNIC

Valid

103.234.156.0/23

APNIC

Valid

103.234.158.0/23

APNIC

Valid

103.240.100.0/22

APNIC

Valid

103.240.100.0/23

APNIC

Valid

103.240.102.0/23

APNIC

Valid

103.241.140.0/22

APNIC

Valid

103.241.140.0/23

APNIC

Valid

103.241.142.0/23

APNIC

Valid

103.244.168.0/22

APNIC

Valid

103.244.168.0/23

APNIC

Valid

103.244.170.0/23

APNIC

Valid

116.212.176.0/21

APNIC

Valid

116.212.176.0/22

APNIC

Valid

116.212.176.0/23

APNIC

Valid

116.212.178.0/23

APNIC

Valid

116.212.180.0/22

APNIC

Valid

116.212.180.0/23

APNIC

Valid

116.212.182.0/23

APNIC

Valid

163.47.208.0/22

APNIC

Valid

163.47.208.0/23

APNIC

Valid

163.47.210.0/23

APNIC

Valid

202.131.156.0/24

APNIC

Valid

202.131.158.0/24

APNIC

Valid

2406:b500::/32

APNIC

Valid

2406:b500::/36

APNIC

Invalid: maxLength

2406:b500:1000::/36

APNIC

Invalid: maxLength

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.