bgpreport

Network · data from 2026-11-12

AS140867 International Gateway Co.,Ltd. (NIX)

Registry name: IGCL-AS-AP - International gateway co., Ltd, TH · PeeringDB

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

Announced routes

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

102.177.178.0/24 No ROA RIR databaseAFRINIC, NTTCOM, RADB 672 100% 68
103.100.141.0/24 Valid RIR databaseAPNIC, RADB 673 100% 68
103.100.142.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
103.113.47.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 673 100% 68
103.113.46.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 66
2402:b740:8001::/48 Valid RIR databaseAPNIC, RADB 38 6%low visibility 29
2402:b740:8f00::/48 Valid RIR databaseAPNIC, RADB 38 6%low visibility 29

AS-SET

PeeringDB's irr_as_set for AS140867: AS-INTERNATIONALGATEWAY. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS140867 isn't in the set, or no route object for AS140867 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS140867 in itNot covered
AS-INTERNATIONALGATEWAY RADB 236136,096 Yes 0
APNIC (also) 010 No 7

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

  • ROA: none1
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: none102.177.178.0/24No ROA covers it. Add a ROA for AS140867, maxLength 24.672 of 673

Route objects not announced

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

102.177.179.0/24AFRINIC, NTTCOMNo ROA
103.100.142.0/23APNICValid
103.100.143.0/24APNIC, RADBValid
103.113.45.0/24APNIC, RADBValid
103.113.46.0/23APNIC, NTTCOM, RADBValid
154.197.112.0/23NTTCOMNo ROA
156.249.134.0/23RADBNo ROA
156.249.188.0/23RADBNo ROA
156.253.0.0/23RADBNo ROA
2402:b740:8000::/33APNIC, RADBValid

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.