bgpreport

Network · data from 2026-11-12

AS30088 GC-852-30088 - GTHost

Registry name: GC-852-30088 - GTHost, US · not in PeeringDB

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

Announced routes

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

136.176.124.0/24 Valid Other origin only 669 99% 67
136.176.125.0/24 Valid Other origin only 669 99% 67
23.95.180.0/24 Valid Other IRR onlyRADB 670 100% 67
40.223.18.0/24 Valid RIR databaseARIN, RADB 673 100% 67
64.204.147.0/24 Valid RIR databaseARIN, RADB 673 100% 67
64.204.212.0/24 Valid RIR databaseARIN, RADB 673 100% 67
68.67.199.0/24 Valid RIR databaseARIN, RADB 673 100% 67
76.9.100.0/24 Valid RIR databaseARIN, RADB 673 100% 67
93.177.115.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
95.155.131.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
136.176.76.0/24 Valid RIR databaseARIN 673 100% 67
151.242.31.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
155.117.245.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
159.253.3.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
173.232.114.0/24 Valid RIR databaseARIN, RADB 673 100% 67
192.228.123.0/24 Valid RIR databaseARIN, RADB 673 100% 67
193.178.115.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
202.50.253.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
212.17.226.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
212.17.227.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
212.17.233.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
216.122.160.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.122.183.0/24 Valid RIR databaseARIN, RADB 673 100% 67
216.122.186.0/24 Valid RIR databaseARIN, RADB 673 100% 67
217.217.193.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
74.115.2.0/24 Valid RIR databaseARIN, RADB 672 100% 67
80.174.118.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
217.217.194.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
157.254.251.0/24 Valid RIR databaseARIN, RADB 671 100% 67
162.221.15.0/24 Valid RIR databaseARIN, RADB 671 100% 67
172.252.128.0/24 Valid RIR databaseARIN, RADB 671 100% 67
199.235.2.0/24 Valid RIR databaseARIN, RADB 671 100% 67
207.210.125.0/24 Valid RIR databaseARIN, RADB 671 100% 67
50.3.39.0/24 Valid RIR databaseARIN, RADB 670 100% 67
64.83.69.0/24 Valid RIR databaseARIN, RADB 670 100% 67
64.83.79.0/24 Valid RIR databaseARIN, RADB 670 100% 67
74.115.0.0/24 Valid RIR databaseARIN, RADB 670 100% 67
173.232.182.0/24 Valid RIR databaseARIN, RADB 670 100% 67
76.9.109.0/24 Valid RIR databaseARIN, RADB 668 99% 67
178.93.212.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
198.1.233.0/24 Valid RIR databaseARIN, RADB 668 99% 67

AS-SET

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

  • Route object: none2
  • Route object: RIR1
  • Route object: not announced32
ChangePrefix or setDetailFull-table peers
Route object: none136.176.124.0/24Route objects for it name AS63023. Add a route object with origin AS30088 in the RIR database for the space.669 of 673
Route object: none136.176.125.0/24Route objects for it name AS63023. Add a route object with origin AS30088 in the RIR database for the space.669 of 673
Route object: RIR23.95.180.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

45.43.206.0/24ARIN, RADBValid
45.43.207.0/24ARIN, RADBValid
45.138.190.0/24RIPEInvalid: origin
45.138.191.0/24RIPEInvalid: origin
50.3.38.0/24ARIN, RADBValid
67.43.36.0/24ARIN, RADBValid
67.210.101.0/24ARIN, RADBValid
68.67.203.0/24ARIN, RADBValid
68.166.192.0/24ARIN, RADBValid
68.166.193.0/24ARIN, RADBValid
68.166.195.0/24ARIN, RADBValid
71.19.129.0/24ARIN, RADBValid
71.19.132.0/24ARIN, RADBValid
82.25.187.0/24RADB, RIPEValid
95.135.164.0/24RADB, RIPEValid
104.166.69.0/24ARIN, RADBValid
141.195.125.0/24ARIN, RADBValid
160.202.68.0/24ARIN, RADBValid
173.44.162.0/24ARIN, RADBValid
173.232.201.0/24ARIN, RADBValid
178.83.209.0/24RADB, RIPEValid
178.83.210.0/24RADB, RIPEValid
178.83.211.0/24RADB, RIPEValid
178.93.86.0/24RADB, RIPEValid
178.93.95.0/24RADB, RIPEValid
178.94.179.0/24RADB, RIPEValid
181.41.196.0/24RADB, RIPEValid
181.215.88.0/24RADB, RIPEValid
181.215.114.0/24RADB, RIPEValid
188.221.77.0/24RADB, RIPEValid
188.221.79.0/24RADB, RIPEValid
217.217.212.0/24RADB, RIPEValid

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.