bgpreport

Network · data from 2026-11-12

AS15270 AS-PAETEC-NET - Windstream Communications LLC

Registry name: AS-PAETEC-NET - Windstream Communications LLC, US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS15270, 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.
40.136.18.0/24 Invalid: origin None 2 0%low visibility 2
64.80.41.0/24 Invalid: origin None 2 0%low visibility 2
64.80.255.0/24 Invalid: origin None 2 0%low visibility 2
64.199.211.0/24 Invalid: origin None 2 0%low visibility 2
74.8.227.0/24 Invalid: origin None 2 0%low visibility 2
74.11.91.0/24 Invalid: origin None 2 0%low visibility 2
209.253.205.0/24 Invalid: origin None 2 0%low visibility 2

AS-SET

AS15270 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 14 are in fix.csv.

  • ROA: origin7
  • Route object: none7
ChangePrefix or setDetailFull-table peers
ROA: origin40.136.18.0/24ROAs covering it name AS7029, not AS15270. If AS15270 should announce it, add a ROA for AS15270.2 of 673
Route object: none40.136.18.0/24No route object for it. Add a route object with origin AS15270 in the RIR database for the space.2 of 673
ROA: origin64.80.41.0/24ROAs covering it name AS7029, not AS15270. If AS15270 should announce it, add a ROA for AS15270.2 of 673
Route object: none64.80.41.0/24No route object for it. Add a route object with origin AS15270 in the RIR database for the space.2 of 673
ROA: origin64.80.255.0/24ROAs covering it name AS7029, not AS15270. If AS15270 should announce it, add a ROA for AS15270.2 of 673
Route object: none64.80.255.0/24No route object for it. Add a route object with origin AS15270 in the RIR database for the space.2 of 673
ROA: origin64.199.211.0/24ROAs covering it name AS7029, not AS15270. If AS15270 should announce it, add a ROA for AS15270.2 of 673
Route object: none64.199.211.0/24No route object for it. Add a route object with origin AS15270 in the RIR database for the space.2 of 673
ROA: origin74.8.227.0/24ROAs covering it name AS7029, not AS15270. If AS15270 should announce it, add a ROA for AS15270.2 of 673
Route object: none74.8.227.0/24No route object for it. Add a route object with origin AS15270 in the RIR database for the space.2 of 673
ROA: origin74.11.91.0/24ROAs covering it name AS7029, not AS15270. If AS15270 should announce it, add a ROA for AS15270.2 of 673
Route object: none74.11.91.0/24No route object for it. Add a route object with origin AS15270 in the RIR database for the space.2 of 673
ROA: origin209.253.205.0/24ROAs covering it name AS7029, not AS15270. If AS15270 should announce it, add a ROA for AS15270.2 of 673
Route object: none209.253.205.0/24No route object for it. Add a route object with origin AS15270 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS15270 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.