Network · data from 2026-11-12

AS153610 Tenbyte

Registry name: TENBYTELIMITED-AS-AP - Tenbyte Limited, BD · PeeringDB

9IPv4 routes 77.8% RPKI valid · 77.8% with a route object

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 2 with no route object for this origin

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

2Route objects not announced registered with origin AS153610, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS153610, 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.164.90.0/24	Invalid: origin	Other origin only	268 40%	63
103.164.91.0/24	Invalid: origin	Other origin only	268 40%	63
103.153.213.0/24	Valid	RIR databaseAPNIC	673 100%	66
163.61.156.0/23	Valid	RIR databaseAPNIC	673 100%	67
163.61.157.0/24	Valid	RIR databaseAPNIC	673 100%	67
138.252.198.0/23	Valid	RIR databaseAPNIC	672 100%	67
138.252.198.0/24	Valid	RIR databaseAPNIC	672 100%	66
138.252.199.0/24	Valid	RIR databaseAPNIC	672 100%	66
163.61.156.0/24	Valid	RIR databaseAPNIC	670 100%	67

AS-SET

AS153610'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 6 are in fix.csv.

ROA: origin2
Route object: none2
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	103.164.90.0/24	ROAs covering it name AS10075, not AS153610. If AS153610 should announce it, add a ROA for AS153610.	268 of 673
Route object: none	103.164.90.0/24	Route objects for it name AS10075. Add a route object with origin AS153610 in the RIR database for the space.	268 of 673
ROA: origin	103.164.91.0/24	ROAs covering it name AS10075, not AS153610. If AS153610 should announce it, add a ROA for AS153610.	268 of 673
Route object: none	103.164.91.0/24	Route objects for it name AS10075. Add a route object with origin AS153610 in the RIR database for the space.	268 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

103.164.90.0/24

ROAs covering it name AS10075, not AS153610. If AS153610 should announce it, add a ROA for AS153610.

268 of 673

Route object: none

103.164.90.0/24

Route objects for it name AS10075. Add a route object with origin AS153610 in the RIR database for the space.

268 of 673

ROA: origin

103.164.91.0/24

ROAs covering it name AS10075, not AS153610. If AS153610 should announce it, add a ROA for AS153610.

268 of 673

Route object: none

103.164.91.0/24

Route objects for it name AS10075. Add a route object with origin AS153610 in the RIR database for the space.

268 of 673

Route objects not announced

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


2001:df5:19c0::/48	APNIC	Valid
2001:df6:7640::/48	APNIC	Valid

2001:df5:19c0::/48

APNIC

Valid

2001:df6:7640::/48

APNIC

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.