bgpreport

Network · data from 2026-11-12

AS134687 TWIDC-AS-AP - TWIDC Limited

Registry name: TWIDC-AS-AP - TWIDC Limited, HK · not in PeeringDB

2IPv4 routes 0.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
23Route objects not announced registered with origin AS134687, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS134687, 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.230.194.0/24 No ROA Other origin only 672 100% 67
45.127.184.0/24 No ROA Other IRR onlyNTTCOM, RADB 2 0%low visibility 2

AS-SET

AS134687 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 27 are in fix.csv.

  • ROA: none2
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced23
ChangePrefix or setDetailFull-table peers
ROA: none103.230.194.0/24No ROA covers it. Add a ROA for AS134687, maxLength 24.672 of 673
Route object: none103.230.194.0/24Route objects for it name AS9584, AS21859, AS38186, AS55720, AS133467, AS137941. Add a route object with origin AS134687 in the RIR database for the space.672 of 673
ROA: none45.127.184.0/24No ROA covers it. Add a ROA for AS134687, maxLength 24.2 of 673
Route object: RIR45.127.184.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

45.127.185.0/24NTTCOM, RADBNo ROA
45.127.187.0/24NTTCOM, RADBNo ROA
103.196.125.0/24NTTCOM, RADBNo ROA
103.196.127.0/24NTTCOM, RADBNo ROA
154.89.12.0/22AFRINICInvalid: origin
154.91.144.0/23AFRINICNo ROA
154.93.4.0/22AFRINICInvalid: origin
154.93.4.0/24AFRINICInvalid: origin
154.93.5.0/24AFRINICInvalid: origin
154.93.6.0/24AFRINICInvalid: origin
154.93.7.0/24AFRINICInvalid: origin
154.197.36.0/22AFRINICNo ROA
154.197.36.0/24AFRINICInvalid: origin
154.197.37.0/24AFRINICInvalid: origin
154.197.38.0/24AFRINICInvalid: origin
154.197.39.0/24AFRINICInvalid: origin
154.211.8.0/22NTTCOM, RADBNo ROA
154.211.8.0/23NTTCOM, RADBNo ROA
154.211.10.0/23NTTCOM, RADBNo ROA
156.227.216.0/23AFRINIC, RADBNo ROA
156.230.2.0/24AFRINICInvalid: origin
156.230.8.0/23NTTCOM, RADBNo ROA
156.230.10.0/24AFRINICInvalid: origin

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.