bgpreport

Network · data from 2026-11-12

AS209697 PARKERBROADBAND Parker Broadband LLC

Registry name: PARKERBROADBAND Parker Broadband LLC, US · not in PeeringDB

24IPv4 routes 58.3% RPKI valid · 41.7% with a route object
0IPv6 routes
7RPKI invalid 7 origin · 0 maxLength
3No ROA 14 with no route object for this origin
23Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS209697, seen from no peer

Announced routes

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

46.34.38.0/24 Invalid: origin Other origin only 2 0%low visibility 2
84.55.19.0/24 Invalid: origin Other origin only 2 0%low visibility 2
88.209.200.0/24 Invalid: origin None 2 0%low visibility 2
91.200.255.0/24 Invalid: origin Other origin only 2 0%low visibility 2
141.226.243.0/24 Invalid: origin Other origin only 2 0%low visibility 2
195.8.200.0/24 Invalid: origin Other origin only 2 0%low visibility 2
92.113.4.0/24 Invalid: origin Other origin only 1 0%low visibility 1
104.164.82.0/24 No ROA None 2 0%low visibility 2
104.164.89.0/24 No ROA None 2 0%low visibility 2
104.164.96.0/24 No ROA None 2 0%low visibility 2
14.102.8.0/24 Valid None 2 0%low visibility 2
96.43.110.0/24 Valid Nonecovered by 96.43.110.0/23 2 0%low visibility 2
159.148.255.0/24 Valid Other origin only 2 0%low visibility 2
194.179.137.0/24 Valid Nonecovered by 194.179.136.0/23 2 0%low visibility 2
92.113.9.0/24 Valid RIR databaseRADB, RIPE 670 100% 67
46.34.42.0/23 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
46.34.49.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
67.210.102.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2
89.38.40.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
157.254.28.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2
157.254.31.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2
185.194.29.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
192.177.28.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2
192.177.31.0/24 Valid RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

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

  • ROA: origin7
  • ROA: none3
  • Route object: none14
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: origin46.34.38.0/24ROAs covering it name AS25198, not AS209697. If AS209697 should announce it, add a ROA for AS209697.2 of 673
Route object: none46.34.38.0/24Route objects for it name AS25198. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: origin84.55.19.0/24ROAs covering it name AS834, not AS209697. If AS209697 should announce it, add a ROA for AS209697.2 of 673
Route object: none84.55.19.0/24Route objects for it name AS834. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: origin88.209.200.0/24ROAs covering it name AS834, not AS209697. If AS209697 should announce it, add a ROA for AS209697.2 of 673
Route object: none88.209.200.0/24No route object for it. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: origin91.200.255.0/24ROAs covering it name AS834, not AS209697. If AS209697 should announce it, add a ROA for AS209697.2 of 673
Route object: none91.200.255.0/24Route objects for it name AS834. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: origin141.226.243.0/24ROAs covering it name AS834, not AS209697. If AS209697 should announce it, add a ROA for AS209697.2 of 673
Route object: none141.226.243.0/24Route objects for it name AS834. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: origin195.8.200.0/24ROAs covering it name AS834, not AS209697. If AS209697 should announce it, add a ROA for AS209697.2 of 673
Route object: none195.8.200.0/24Route objects for it name AS834. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: origin92.113.4.0/24ROAs covering it name AS137410, not AS209697. If AS209697 should announce it, add a ROA for AS209697.1 of 673
Route object: none92.113.4.0/24Route objects for it name AS834. Add a route object with origin AS209697 in the RIR database for the space.1 of 673
ROA: none104.164.82.0/24No ROA covers it. Add a ROA for AS209697, maxLength 24.2 of 673
Route object: none104.164.82.0/24No route object for it. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: none104.164.89.0/24No ROA covers it. Add a ROA for AS209697, maxLength 24.2 of 673
Route object: none104.164.89.0/24No route object for it. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
ROA: none104.164.96.0/24No ROA covers it. Add a ROA for AS209697, maxLength 24.2 of 673
Route object: none104.164.96.0/24No route object for it. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
Route object: none14.102.8.0/24No route object for it. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
Route object: none96.43.110.0/24No route object for it. A route object for 96.43.110.0/23 with origin AS209697 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209697 in the RIR database for the space.2 of 673
Route object: none159.148.255.0/24Route objects for it name AS401838. Add a route object with origin AS209697 in the RIR database for the space.2 of 673
Route object: none194.179.137.0/24No route object for it. A route object for 194.179.136.0/23 with origin AS209697 covers it (filters allowing more-specifics accept it). Add a route object with origin AS209697 in the RIR database for the space.2 of 673

Route objects not announced

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

45.147.156.0/24RADB, RIPEValid
45.147.157.0/24RADB, RIPEValid
45.147.158.0/24RADB, RIPEValid
46.34.47.0/24RADB, RIPEValid
46.34.55.0/24RADB, RIPEValid
46.182.207.0/24RADB, RIPEValid
62.112.206.0/24RADB, RIPEValid
64.253.93.0/24ARIN, RADBValid
77.111.116.0/24RADB, RIPEValid
77.111.121.0/24RADB, RIPEValid
77.242.157.0/24RADB, RIPEValid
84.55.23.0/24RADB, RIPEValid
85.208.46.0/24RADB, RIPEValid
88.209.220.0/24RADB, RIPEValid
89.42.92.0/24RADB, RIPEValid
89.42.93.0/24RADB, RIPEValid
89.43.142.0/24RADB, RIPEValid
89.46.4.0/24RADB, RIPEValid
89.47.123.0/24RADB, RIPEValid
89.47.124.0/24RADB, RIPEValid
92.61.102.0/24RADB, RIPEValid
96.43.110.0/23ARIN, RADBValid
102.129.157.0/24RADBValid
185.54.14.0/23RADB, RIPEValid
192.228.113.0/24ARIN, RADBValid
193.149.179.0/24RADB, RIPEValid
194.179.136.0/23RADBValid

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.