bgpreport

Network · data from 2026-11-12

AS137235 AS137235 Wired ISP Inc.

Registry name: AS137235 Wired ISP Inc., US · not in PeeringDB

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

Announced routes

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

151.243.165.0/24 Invalid: origin Other origin only 2 0%low visibility 2
178.83.190.0/24 Invalid: origin None 2 0%low visibility 2
89.31.234.0/24 Valid Other IRR onlyRADB 672 100% 66
213.220.42.0/24 Valid Other IRR onlyRADB 672 100% 66
102.211.235.0/24 Valid Other IRR onlyRADB 671 100% 66
185.194.228.0/24 Valid Other IRR onlyRADB 671 100% 66
213.210.52.0/24 Valid Other IRR onlyRADB 669 99% 67
23.230.87.0/24 Valid RIR databaseARIN, RADB 672 100% 67
82.47.55.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
143.20.89.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
162.141.114.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
178.95.4.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
178.95.239.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.13.224.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
193.58.146.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
31.56.23.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
62.144.39.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
95.134.43.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
140.150.225.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
141.11.231.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
143.14.162.0/24 Valid RIR databaseRADB, RIPE 671 100% 66
151.243.255.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
178.83.93.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
192.228.118.0/24 Valid RIR databaseARIN, RADB 671 100% 66
2.56.254.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
45.135.226.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
45.136.39.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
143.20.98.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
151.244.247.0/24 Valid RIR databaseRADB, RIPE 670 100% 66
45.91.137.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
45.137.195.0/24 Valid RIR databaseRADB, RIPE 669 99% 66
151.243.15.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
45.145.243.0/24 Valid RIR databaseRADB, RIPE 668 99% 67

AS-SET

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

  • ROA: origin2
  • Route object: none2
  • Route object: RIR5
ChangePrefix or setDetailFull-table peers
ROA: origin151.243.165.0/24ROAs covering it name AS834, not AS137235. If AS137235 should announce it, add a ROA for AS137235.2 of 673
Route object: none151.243.165.0/24Route objects for it name AS834. Add a route object with origin AS137235 in the RIR database for the space.2 of 673
ROA: origin178.83.190.0/24ROAs covering it name AS834, not AS137235. If AS137235 should announce it, add a ROA for AS137235.2 of 673
Route object: none178.83.190.0/24No route object for it. Add a route object with origin AS137235 in the RIR database for the space.2 of 673
Route object: RIR89.31.234.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR213.220.42.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR102.211.235.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR185.194.228.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR213.210.52.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS137235 is announced.

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.