bgpreport

Network · data from 2026-11-12

AS55554 True International Gateway

Registry name: INTER-IIT-TIG-AS-AP - True International Gateway Co., Ltd., TH · PeeringDB

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

Announced routes

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

122.144.30.0/24 Valid Other origin only 4 1%low visibility 4
122.144.29.0/24 Valid RIR databaseAPNIC 4 1%low visibility 4
122.144.31.0/24 Valid RIR databaseAPNIC 4 1%low visibility 4

AS-SET

AS55554'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.

  • Route object: none1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none122.144.30.0/24Route objects for it name AS38081. Add a route object with origin AS55554 in the RIR database for the space.4 of 673

Route objects not announced

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

27.123.19.0/24APNICValid
61.91.221.0/24APNICValid
113.21.240.0/24APNICValid
113.21.242.0/24APNIC, RADBValid
122.144.27.0/24APNICValid

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.