bgpreport

Network · data from 2026-11-12

AS38006 TQT-AS-AP - Time Quantum Technologies Sdn. Bhd.

Registry name: TQT-AS-AP - Time Quantum Technologies Sdn. Bhd., MY · not in PeeringDB

1IPv4 routes 0.0% 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
14Route objects not announced registered with origin AS38006, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS38006, 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.
203.189.16.0/21 No ROA Other IRR onlyNTTCOM 673 100% 66

AS-SET

AS38006 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 16 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced14
ChangePrefix or setDetailFull-table peers
ROA: none203.189.16.0/21No ROA covers it. Add a ROA for AS38006, maxLength 21.673 of 673
Route object: RIR203.189.16.0/21Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

203.189.16.0/22NTTCOM, RADBNo ROA
203.189.16.0/23NTTCOM, RADBNo ROA
203.189.16.0/24NTTCOM, RADBNo ROA
203.189.17.0/24NTTCOM, RADBNo ROA
203.189.18.0/23NTTCOM, RADBNo ROA
203.189.18.0/24NTTCOM, RADBNo ROA
203.189.19.0/24NTTCOM, RADBNo ROA
203.189.20.0/22NTTCOM, RADBNo ROA
203.189.20.0/23NTTCOM, RADBNo ROA
203.189.20.0/24NTTCOM, RADBNo ROA
203.189.21.0/24NTTCOM, RADBNo ROA
203.189.22.0/23NTTCOM, RADBNo ROA
203.189.22.0/24NTTCOM, RADBNo ROA
203.189.23.0/24NTTCOM, RADBNo ROA

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.