Network · data from 2026-11-12

AS63768 THIENBINH-AS-VN - Thien Binh Software Service Company Limited

Registry name: THIENBINH-AS-VN - Thien Binh Software Service Company Limited, VN · not in PeeringDB

4IPv4 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

3Route objects not announced registered with origin AS63768, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS63768, 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.78.76.0/24	Valid	RIR databaseAPNIC, NTTCOM	671 100%	67
103.78.77.0/24	Valid	RIR databaseAPNIC, NTTCOM	670 100%	67
103.78.78.0/24	Valid	RIR databaseAPNIC, NTTCOM	670 100%	67
103.78.79.0/24	Valid	RIR databaseAPNIC, NTTCOM	651 97%	66

AS-SET

AS63768 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 3 are in fix.csv.

Route object: not announced3

Route objects not announced

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


103.78.76.0/22	APNIC, NTTCOM, RADB	Valid
103.78.76.0/23	APNIC, NTTCOM	Valid
103.78.78.0/23	APNIC, NTTCOM	Valid

103.78.76.0/22

APNIC, NTTCOM, RADB

Valid

103.78.76.0/23

APNIC, NTTCOM

Valid

103.78.78.0/23

APNIC, NTTCOM

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.