bgpreport

Network · data from 2026-11-12

AS11059 MIFFLIN COUNTY WIRELESS

Registry name: MIFFLIN-COUNTY-WIRELESS - MIFFLIN COUNTY WIRELESS LLC, US · PeeringDB

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

Announced routes

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

206.81.111.0/24 No ROA Other IRR onlyRADB 672 100% 67
64.234.230.0/24 Valid Nonecovered by 64.234.228.0/22 672 100% 67
199.202.225.0/24 Valid Nonecovered by 199.202.224.0/22 672 100% 67
199.202.224.0/22 Valid Other IRR onlyRADB 2 0%low visibility 2
172.110.188.0/24 Valid RIR databaseARIN 672 100% 67
198.13.156.0/24 Valid RIR databaseARIN 672 100% 67
198.13.157.0/24 Valid RIR databaseARIN 672 100% 67
64.234.228.0/22 Valid RIR databaseARIN, RADB 2 0%low visibility 2

AS-SET

AS11059's PeeringDB record names no 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 32 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR2
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: none206.81.111.0/24No ROA covers it. Add a ROA for AS11059, maxLength 24.672 of 673
Route object: RIR206.81.111.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none64.234.230.0/24No route object for it. A route object for 64.234.228.0/22 with origin AS11059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11059 in the RIR database for the space.672 of 673
Route object: none199.202.225.0/24No route object for it. A route object for 199.202.224.0/22 with origin AS11059 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11059 in the RIR database for the space.672 of 673
Route object: RIR199.202.224.0/22Route object only in RADB. Add it in the RIR database for the space.2 of 673

Route objects not announced

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

38.101.242.0/24RADBNo ROA
64.205.32.0/20ARINValid
64.205.48.0/20ARINValid
69.33.128.0/19ARINValid
76.9.96.0/20ARIN, RADBValid
96.62.96.0/23RIPEValid
134.202.17.0/24ARINValid
136.175.64.0/23ARINValid
140.99.144.0/22ARINInvalid: origin
140.99.176.0/22ARINInvalid: origin
143.20.224.0/22RIPEValid
143.20.232.0/22RIPEValid
143.20.240.0/22RIPEValid
150.241.200.0/23RIPEValid
162.141.82.0/23RIPEValid
178.83.0.0/22RIPEInvalid: origin
178.83.216.0/22RIPEInvalid: origin
192.102.96.0/19ARINNo ROA
192.132.128.0/18ARINNo ROA
198.29.96.0/19ARINNo ROA
206.80.235.0/24RADBNo ROA
209.92.160.0/20ARINValid
216.75.72.0/22ARINValid
216.75.76.0/22ARINValid
216.132.144.0/22ARINValid
216.132.200.0/23ARINValid
216.132.202.0/23ARINValid

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.