bgpreport

Network · data from 2026-11-12

AS395500 WILSONCREEK - Wilson Creek Communications, LLC

Registry name: WILSONCREEK - Wilson Creek Communications, LLC, US · not in PeeringDB

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

Announced routes

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

12.215.164.0/24 No ROA None 673 100% 67
38.79.85.0/24 No ROA None 672 100% 67
12.156.142.0/24 No ROA Other IRR onlyRADB 673 100% 67
12.156.143.0/24 No ROA Other IRR onlyRADB 673 100% 67
12.156.142.0/23 No ROA Other IRR onlyALTDB 2 0%low visibility 2
2605:7c40:4000::/36 Valid Nonecovered by 2605:7c40::/32 606 95% 68
2605:7c40:1000::/36 Valid Nonecovered by 2605:7c40::/32 605 95% 67
2605:7c40:5000::/36 Valid Nonecovered by 2605:7c40::/32 1 0%low visibility 1
141.193.210.0/24 Valid Other IRR onlyRADB 672 100% 67
141.193.211.0/24 Valid Other IRR onlyRADB 672 100% 67
72.29.188.0/24 Valid RIR databaseARIN 670 100% 67

AS-SET

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

  • ROA: none5
  • Route object: none5
  • Route object: RIR5
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none12.215.164.0/24No ROA covers it. Add a ROA for AS395500, maxLength 24.673 of 673
Route object: none12.215.164.0/24No route object for it. Add a route object with origin AS395500 in the RIR database for the space.673 of 673
ROA: none38.79.85.0/24No ROA covers it. Add a ROA for AS395500, maxLength 24.672 of 673
Route object: none38.79.85.0/24No route object for it. Add a route object with origin AS395500 in the RIR database for the space.672 of 673
ROA: none12.156.142.0/24No ROA covers it. Add a ROA for AS395500, maxLength 24.673 of 673
Route object: RIR12.156.142.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none12.156.143.0/24No ROA covers it. Add a ROA for AS395500, maxLength 24.673 of 673
Route object: RIR12.156.143.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none12.156.142.0/23No ROA covers it. Add a ROA for AS395500, maxLength 23.2 of 673
Route object: RIR12.156.142.0/23Route object only in ALTDB. Add it in the RIR database for the space.2 of 673
Route object: none2605:7c40:4000::/36No route object for it. A route object for 2605:7c40::/32 with origin AS395500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395500 in the RIR database for the space.606 of 636
Route object: none2605:7c40:1000::/36No route object for it. A route object for 2605:7c40::/32 with origin AS395500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395500 in the RIR database for the space.605 of 636
Route object: none2605:7c40:5000::/36No route object for it. A route object for 2605:7c40::/32 with origin AS395500 covers it (filters allowing more-specifics accept it). Add a route object with origin AS395500 in the RIR database for the space.1 of 636
Route object: RIR141.193.210.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR141.193.211.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

141.193.210.0/23ALTDB, ARINValid
2605:7c40::/32ARINValid

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.