bgpreport

Network · data from 2026-11-12

AS14315 1GServers

Registry name: 1GSERVERS - 1GSERVERS, LLC, US · PeeringDB

65IPv4 routes 80.0% RPKI valid · 87.7% with a route object
8IPv6 routes 37.5% RPKI valid · 75.0% with a route object
4RPKI invalid 4 origin · 0 maxLength
14No ROA 10 with no route object for this origin
5Low visibility seen by under 10% of full-table peers
25Route objects not announced registered with origin AS14315, seen from no peer

Announced routes

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

172.98.209.0/24 Invalid: origin Other origin only 9 1%low visibility 9
108.165.185.0/24 Invalid: origin Other origin only 7 1%low visibility 8
173.0.97.0/24 Invalid: origin Other origin only 7 1%low visibility 8
199.182.168.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2602:f66f:60::/44 No ROA None 329 52% 64
2602:f66f:70::/44 No ROA None 328 52% 64
155.103.66.0/24 No ROA None 123 18% 43
155.103.67.0/24 No ROA None 123 18% 43
23.158.120.0/24 No ROA Other IRR onlyRADB 671 100% 67
104.251.122.0/23 No ROA Other IRR onlyRADB 671 100% 67
136.175.8.0/22 No ROA Other IRR onlyRADB 671 100% 67
142.202.240.0/22 No ROA Other IRR onlyRADB 671 100% 67
206.168.190.0/23 No ROA Other IRR onlyRADB 671 100% 67
207.32.216.0/22 No ROA Other IRR onlyRADB 671 100% 67
96.47.160.0/22 No ROA Other IRR onlyRADB 670 100% 67
2605:8340::/32 No ROA Other IRR onlyRADB 636 100% 67
2605:9d00:0:100::/56 No ROA Other IRR onlyRADB 49 8%low visibility 30
2a03:8b80::/29 No ROA RIR databaseRIPE 635 100% 67
198.134.24.0/24 Valid Nonecovered by 198.134.24.0/23 671 100% 67
198.134.25.0/24 Valid Nonecovered by 198.134.24.0/23 671 100% 67
162.213.1.0/24 Valid Other IRR onlyRADB 671 100% 67
212.189.40.0/24 Valid Other IRR onlyRADB 671 100% 67
45.59.104.0/24 Valid Other IRR onlyRADB 670 100% 67
23.94.110.0/24 Valid RIR databaseARIN, RADB 671 100% 67
23.142.92.0/24 Valid RIR databaseARIN 671 100% 67
40.223.85.0/24 Valid RIR databaseARIN, RADB 671 100% 67
48.103.137.0/24 Valid RIR databaseRIPE 671 100% 67
50.114.160.0/24 Valid RIR databaseARIN 671 100% 67
50.114.203.0/24 Valid RIR databaseARIN, RADB 671 100% 67
64.50.186.0/24 Valid RIR databaseARIN, RADB 671 100% 67
85.121.240.0/24 Valid RIR databaseRIPE 671 100% 67
94.139.32.0/24 Valid RIR databaseRIPE 671 100% 67
103.196.20.0/24 Valid RIR databaseAPNIC 671 100% 67
104.164.46.0/24 Valid RIR databaseARIN, RADB 671 100% 67
104.193.195.0/24 Valid RIR databaseARIN 671 100% 67
107.182.130.0/24 Valid RIR databaseARIN 671 100% 67
108.59.244.0/24 Valid RIR databaseARIN 671 100% 67
130.12.115.0/24 Valid RIR databaseARIN 671 100% 67
136.0.33.0/24 Valid RIR databaseARIN, RADB 671 100% 67
136.0.82.0/24 Valid RIR databaseARIN, RADB 671 100% 67
136.0.116.0/24 Valid RIR databaseARIN 671 100% 67
136.0.157.0/24 Valid RIR databaseARIN 671 100% 67
137.175.30.0/24 Valid RIR databaseARIN, RADB 671 100% 67
144.225.51.0/24 Valid RIR databaseARIN 671 100% 67
155.117.9.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
157.254.221.0/24 Valid RIR databaseARIN, RADB 671 100% 67
173.0.109.0/24 Valid RIR databaseARIN, RADB 671 100% 67
173.0.110.0/24 Valid RIR databaseARIN, RADB 671 100% 67
177.202.119.0/24 Valid RIR databaseRIPE 671 100% 67
179.254.92.0/24 Valid RIR databaseRIPE 671 100% 67
184.174.20.0/24 Valid RIR databaseARIN, RADB 671 100% 67
199.101.198.0/24 Valid RIR databaseARIN, RADB 671 100% 67
199.204.161.0/24 Valid RIR databaseARIN, RADB 671 100% 67
201.58.151.0/24 Valid RIR databaseRIPE 671 100% 67
205.207.255.0/24 Valid RIR databaseARIN 671 100% 67
212.162.148.0/24 Valid RIR databaseRIPE 671 100% 67
216.122.187.0/24 Valid RIR databaseARIN, RADB 671 100% 67
45.42.46.0/24 Valid RIR databaseARIN, RADB 670 100% 67
72.14.136.0/24 Valid RIR databaseARIN, RADB 670 100% 67
74.120.121.0/24 Valid RIR databaseARIN, RADB 670 100% 67
104.234.238.0/24 Valid RIR databaseARIN, RADB 670 100% 67
108.186.183.0/24 Valid RIR databaseARIN, RADB 670 100% 67
154.194.50.0/24 Valid RIR databaseAFRINIC, RADB 670 100% 67
172.82.183.0/24 Valid RIR databaseARIN 670 100% 67
200.229.20.0/24 Valid RIR databaseARIN, RADB 670 100% 67
45.43.221.0/24 Valid RIR databaseARIN 669 99% 67
45.202.109.0/24 Valid RIR databaseAFRINIC, RADB 669 99% 67
64.205.73.0/24 Valid RIR databaseARIN, RADB 668 99% 67
77.67.88.0/24 Valid RIR databaseRADB, RIPE 664 99% 67
65.87.27.0/24 Valid RIR databaseARIN, RADB 656 97% 67
2620:13e:500e::/48 Valid RIR databaseARIN 636 100% 67
2a0c:9f00:a000::/48 Valid RIR databaseRIPE 636 100% 67
2a0f:1580::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS14315: RADB::AS-1GSERVERS. 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 (AS14315 isn't in the set, or no route object for AS14315 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 objectsAS14315 in itNot covered
RADB::AS-1GSERVERS RADB5 member sets in no database: AS-14397, AS-DURABLE, AS-NINJA-IX, AS214390:AS-MEMBERS, AS64249:AS-PEERS-PHX 2151,408 Yes 8

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

  • ROA: origin4
  • ROA: none14
  • Route object: none10
  • Route object: RIR12
  • AS-SET: missing member5
  • Route object: not announced25
ChangePrefix or setDetailFull-table peers
ROA: origin172.98.209.0/24ROAs covering it name AS834, not AS14315. If AS14315 should announce it, add a ROA for AS14315.9 of 673
Route object: none172.98.209.0/24Route objects for it name AS834. Add a route object with origin AS14315 in the RIR database for the space.9 of 673
ROA: origin108.165.185.0/24ROAs covering it name AS218522, not AS14315. If AS14315 should announce it, add a ROA for AS14315.7 of 673
Route object: none108.165.185.0/24Route objects for it name AS218522. Add a route object with origin AS14315 in the RIR database for the space.7 of 673
ROA: origin173.0.97.0/24ROAs covering it name AS40676, not AS14315. If AS14315 should announce it, add a ROA for AS14315.7 of 673
Route object: none173.0.97.0/24Route objects for it name AS40676. Add a route object with origin AS14315 in the RIR database for the space.7 of 673
ROA: origin199.182.168.0/24ROAs covering it name AS834, not AS14315. If AS14315 should announce it, add a ROA for AS14315.2 of 673
Route object: none199.182.168.0/24Route objects for it name AS834. Add a route object with origin AS14315 in the RIR database for the space.2 of 673
ROA: none2602:f66f:60::/44No ROA covers it. Add a ROA for AS14315, maxLength 44.329 of 636
Route object: none2602:f66f:60::/44No route object for it. Add a route object with origin AS14315 in the RIR database for the space.329 of 636
ROA: none2602:f66f:70::/44No ROA covers it. Add a ROA for AS14315, maxLength 44.328 of 636
Route object: none2602:f66f:70::/44No route object for it. Add a route object with origin AS14315 in the RIR database for the space.328 of 636
ROA: none155.103.66.0/24No ROA covers it. Add a ROA for AS14315, maxLength 24.123 of 673
Route object: none155.103.66.0/24No route object for it. Add a route object with origin AS14315 in the RIR database for the space.123 of 673
ROA: none155.103.67.0/24No ROA covers it. Add a ROA for AS14315, maxLength 24.123 of 673
Route object: none155.103.67.0/24No route object for it. Add a route object with origin AS14315 in the RIR database for the space.123 of 673
ROA: none23.158.120.0/24No ROA covers it. Add a ROA for AS14315, maxLength 24.671 of 673
Route object: RIR23.158.120.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none104.251.122.0/23No ROA covers it. Add a ROA for AS14315, maxLength 23.671 of 673
Route object: RIR104.251.122.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none136.175.8.0/22No ROA covers it. Add a ROA for AS14315, maxLength 22.671 of 673
Route object: RIR136.175.8.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none142.202.240.0/22No ROA covers it. Add a ROA for AS14315, maxLength 22.671 of 673
Route object: RIR142.202.240.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none206.168.190.0/23No ROA covers it. Add a ROA for AS14315, maxLength 23.671 of 673
Route object: RIR206.168.190.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none207.32.216.0/22No ROA covers it. Add a ROA for AS14315, maxLength 22.671 of 673
Route object: RIR207.32.216.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none96.47.160.0/22No ROA covers it. Add a ROA for AS14315, maxLength 22.670 of 673
Route object: RIR96.47.160.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2605:8340::/32No ROA covers it. Add a ROA for AS14315, maxLength 32.636 of 636
Route object: RIR2605:8340::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2605:9d00:0:100::/56No ROA covers it. Add a ROA for AS14315, maxLength 56.49 of 636
Route object: RIR2605:9d00:0:100::/56Route object only in RADB. Add it in the RIR database for the space.49 of 636
ROA: none2a03:8b80::/29No ROA covers it. Add a ROA for AS14315, maxLength 29.635 of 636
Route object: none198.134.24.0/24No route object for it. A route object for 198.134.24.0/23 with origin AS14315 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14315 in the RIR database for the space.671 of 673
Route object: none198.134.25.0/24No route object for it. A route object for 198.134.24.0/23 with origin AS14315 covers it (filters allowing more-specifics accept it). Add a route object with origin AS14315 in the RIR database for the space.671 of 673
Route object: RIR162.213.1.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR212.189.40.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR45.59.104.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
AS-SET: missing memberRADB::AS-1GSERVERSAS-1GSERVERS (RADB) lists AS-14397; no IRR database read has it.
AS-SET: missing memberRADB::AS-1GSERVERSAS-1GSERVERS (RADB) lists AS-DURABLE; no IRR database read has it.
AS-SET: missing memberRADB::AS-1GSERVERSAS-1GSERVERS (RADB) lists AS-NINJA-IX; no IRR database read has it.
AS-SET: missing memberRADB::AS-1GSERVERSAS-1GSERVERS (RADB) lists AS214390:AS-MEMBERS; no IRR database read has it.
AS-SET: missing memberRADB::AS-1GSERVERSAS-1GSERVERS (RADB) lists AS64249:AS-PEERS-PHX; no IRR database read has it.

Route objects not announced

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

45.196.70.0/23RADBNo ROA
45.196.88.0/23RADBNo ROA
45.196.110.0/23RADBNo ROA
45.196.114.0/23RADBNo ROA
45.197.137.0/24AFRINICInvalid: origin
45.202.197.0/24AFRINICInvalid: origin
67.220.64.0/24ARINValid
103.28.68.0/24ARINValid
154.82.19.0/24AFRINICInvalid: origin
154.84.128.0/22RADBNo ROA
154.84.132.0/23RADBNo ROA
154.88.68.0/22RADBNo ROA
154.89.128.0/22RADBNo ROA
154.89.136.0/22RADBNo ROA
154.196.8.0/22AFRINICInvalid: origin
156.224.64.0/22AFRINIC, RADBNo ROA
156.224.68.0/22AFRINIC, RADBNo ROA
198.134.24.0/23ARINValid
2001:470:4d5::/48ARINValid
2602:f277:e00::/40ARINValid
2602:f277:f00::/40ARINValid
2602:f5cb::/40ARINValid
2606:fc40:4000::/48ARINValid
2a0f:85c1:b49::/48RIPEValid
2a13:a5c7:2710::/44RIPEValid

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.