bgpreport

Network · data from 2026-11-12

AS400909 TRAVCHIS - TRAVCHIS, LLC

Registry name: TRAVCHIS - TRAVCHIS, LLC, US · not in PeeringDB

56IPv4 routes 73.2% RPKI valid · 73.2% with a route object
0IPv6 routes
13RPKI invalid 13 origin · 0 maxLength
2No ROA 15 with no route object for this origin
14Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS400909, seen from no peer

Announced routes

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

157.254.160.0/23 Invalid: origin Other origin only 5 1%low visibility 4
146.103.8.0/23 Invalid: origin Other origin only 4 1%low visibility 3
193.7.203.0/24 Invalid: origin Other origin only 4 1%low visibility 3
213.145.76.0/23 Invalid: origin None 4 1%low visibility 3
213.145.78.0/23 Invalid: origin None 4 1%low visibility 3
31.6.28.0/23 Invalid: origin Other origin only 3 0%low visibility 3
77.93.150.0/23 Invalid: origin Other origin only 3 0%low visibility 3
82.206.14.0/23 Invalid: origin Other origin only 3 0%low visibility 3
83.147.30.0/23 Invalid: origin Other origin only 3 0%low visibility 3
94.241.162.0/23 Invalid: origin Other origin only 3 0%low visibility 3
5.102.108.0/22 Invalid: origin Other origin only 1 0%low visibility 1
140.99.84.0/23 Invalid: origin Other origin only 1 0%low visibility 1
154.16.18.0/24 Invalid: origin Other origin only 1 0%low visibility 1
185.252.162.0/23 No ROA None 670 100% 67
178.208.178.0/23 No ROA None 4 1%low visibility 3
194.179.138.0/23 Valid Other IRR onlyRADB 673 100% 66
82.153.32.0/24 Valid Other IRR onlyRADB 671 100% 67
82.152.105.0/24 Valid Other IRR onlyRADB 667 99% 67
93.127.150.0/23 Valid Other IRR onlyRADB 666 99% 67
31.56.125.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
82.38.149.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
89.213.124.0/23 Valid RIR databaseRADB, RIPE 673 100% 66
143.20.52.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
185.194.206.0/23 Valid RIR databaseRADB, RIPE 673 100% 66
185.213.249.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
195.211.51.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
45.154.156.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
82.163.228.0/22 Valid RIR databaseRADB, RIPE 672 100% 67
178.208.180.0/23 Valid RIR databaseRADB, RIPE 672 100% 67
104.234.127.0/24 Valid RIR databaseARIN, RADB 671 100% 67
141.11.54.0/23 Valid RIR databaseRADB, RIPE 671 100% 66
141.11.162.0/23 Valid RIR databaseRADB, RIPE 671 100% 66
141.11.168.0/23 Valid RIR databaseRADB, RIPE 671 100% 66
141.11.170.0/23 Valid RIR databaseRADB, RIPE 671 100% 66
141.11.206.0/23 Valid RIR databaseRADB, RIPE 671 100% 66
141.11.222.0/23 Valid RIR databaseRADB, RIPE 671 100% 67
185.219.190.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
185.238.229.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
81.5.189.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
13.141.61.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
89.47.100.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
91.226.59.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
151.242.6.0/24 Valid RIR databaseRADB, RIPE 667 99% 67
216.185.39.0/24 Valid RIR databaseARIN, RADB 667 99% 67
2.27.138.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
31.57.148.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
37.202.214.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
82.29.118.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
109.176.204.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
178.253.26.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
185.226.56.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
185.226.58.0/23 Valid RIR databaseRADB, RIPE 666 99% 67
23.27.226.0/24 Valid RIR databaseARIN, RADB 664 99% 67
79.175.103.0/24 Valid RIR databaseRADB, RIPE 664 99% 67
185.208.156.0/24 Valid RIR databaseRIPE 664 99% 67
217.216.149.0/24 Valid RIR databaseRADB, RIPE 664 99% 67

AS-SET

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

  • ROA: origin13
  • ROA: none2
  • Route object: none15
  • Route object: RIR4
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin157.254.160.0/23ROAs covering it name AS18978, AS26739, not AS400909. If AS400909 should announce it, add a ROA for AS400909.5 of 673
Route object: none157.254.160.0/23Route objects for it name AS18978, AS26739. Add a route object with origin AS400909 in the RIR database for the space.5 of 673
ROA: origin146.103.8.0/23ROAs covering it name AS834, not AS400909. If AS400909 should announce it, add a ROA for AS400909.4 of 673
Route object: none146.103.8.0/23Route objects for it name AS834. Add a route object with origin AS400909 in the RIR database for the space.4 of 673
ROA: origin193.7.203.0/24ROAs covering it name AS57043, not AS400909. If AS400909 should announce it, add a ROA for AS400909.4 of 673
Route object: none193.7.203.0/24Route objects for it name AS57043. Add a route object with origin AS400909 in the RIR database for the space.4 of 673
ROA: origin213.145.76.0/23ROAs covering it name AS834, not AS400909. If AS400909 should announce it, add a ROA for AS400909.4 of 673
Route object: none213.145.76.0/23No route object for it. Add a route object with origin AS400909 in the RIR database for the space.4 of 673
ROA: origin213.145.78.0/23ROAs covering it name AS834, not AS400909. If AS400909 should announce it, add a ROA for AS400909.4 of 673
Route object: none213.145.78.0/23No route object for it. Add a route object with origin AS400909 in the RIR database for the space.4 of 673
ROA: origin31.6.28.0/23ROAs covering it name AS834, not AS400909. If AS400909 should announce it, add a ROA for AS400909.3 of 673
Route object: none31.6.28.0/23Route objects for it name AS834. Add a route object with origin AS400909 in the RIR database for the space.3 of 673
ROA: origin77.93.150.0/23ROAs covering it name AS834, AS8851, AS19905, not AS400909. If AS400909 should announce it, add a ROA for AS400909.3 of 673
Route object: none77.93.150.0/23Route objects for it name AS834. Add a route object with origin AS400909 in the RIR database for the space.3 of 673
ROA: origin82.206.14.0/23ROAs covering it name AS834, not AS400909. If AS400909 should announce it, add a ROA for AS400909.3 of 673
Route object: none82.206.14.0/23Route objects for it name AS834. Add a route object with origin AS400909 in the RIR database for the space.3 of 673
ROA: origin83.147.30.0/23ROAs covering it name AS834, not AS400909. If AS400909 should announce it, add a ROA for AS400909.3 of 673
Route object: none83.147.30.0/23Route objects for it name AS834. Add a route object with origin AS400909 in the RIR database for the space.3 of 673
ROA: origin94.241.162.0/23ROAs covering it name AS197703, not AS400909. If AS400909 should announce it, add a ROA for AS400909.3 of 673
Route object: none94.241.162.0/23Route objects for it name AS197703. Add a route object with origin AS400909 in the RIR database for the space.3 of 673
ROA: origin5.102.108.0/22ROAs covering it name AS270158, AS270172, not AS400909. If AS400909 should announce it, add a ROA for AS400909.1 of 673
Route object: none5.102.108.0/22Route objects for it name AS270158, AS270172. Add a route object with origin AS400909 in the RIR database for the space.1 of 673
ROA: origin140.99.84.0/23ROAs covering it name AS834, not AS400909. If AS400909 should announce it, add a ROA for AS400909.1 of 673
Route object: none140.99.84.0/23Route objects for it name AS834. Add a route object with origin AS400909 in the RIR database for the space.1 of 673
ROA: origin154.16.18.0/24ROAs covering it name AS152606, not AS400909. If AS400909 should announce it, add a ROA for AS400909.1 of 673
Route object: none154.16.18.0/24Route objects for it name AS9087, AS152606. Add a route object with origin AS400909 in the RIR database for the space.1 of 673
ROA: none185.252.162.0/23No ROA covers it. Add a ROA for AS400909, maxLength 23.670 of 673
Route object: none185.252.162.0/23No route object for it. Add a route object with origin AS400909 in the RIR database for the space.670 of 673
ROA: none178.208.178.0/23No ROA covers it. Add a ROA for AS400909, maxLength 23.4 of 673
Route object: none178.208.178.0/23No route object for it. Add a route object with origin AS400909 in the RIR database for the space.4 of 673
Route object: RIR194.179.138.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR82.153.32.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR82.152.105.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR93.127.150.0/23Route object only in RADB. Add it in the RIR database for the space.666 of 673

Route objects not announced

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

37.202.192.0/24RIPEInvalid: origin
89.34.228.0/24RIPEInvalid: 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.