bgpreport

Network · data from 2026-11-12

AS139009 Windstream Communication Limited

Registry name: WSCL-AS-AP - Windstream Communication Limited, BD · PeeringDB

32IPv4 routes 100.0% RPKI valid · 100.0% with a route object
30IPv6 routes 96.7% RPKI valid · 96.7% with a route object
1RPKI invalid 0 origin · 1 maxLength
0No ROA 1 with no route object for this origin
10Low visibility seen by under 10% of full-table peers
24Route objects not announced registered with origin AS139009, seen from no peer

Announced routes

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

2407:d40:800c::/48 Invalid: maxLength Nonecovered by 2407:d40::/32 8 1%low visibility 3
103.29.238.0/24 Valid RIR databaseAPNIC 673 100% 69
103.43.149.0/24 Valid RIR databaseAPNIC 673 100% 67
103.126.150.0/24 Valid RIR databaseAPNIC 673 100% 69
103.133.206.0/24 Valid RIR databaseAPNIC 673 100% 67
103.138.30.0/23 Valid RIR databaseAPNIC 673 100% 68
103.138.30.0/24 Valid RIR databaseAPNIC 673 100% 69
103.138.31.0/24 Valid RIR databaseAPNIC 673 100% 69
103.144.49.0/24 Valid RIR databaseAPNIC 673 100% 69
103.153.66.0/24 Valid RIR databaseAPNIC 673 100% 69
103.154.49.0/24 Valid RIR databaseAPNIC 673 100% 69
103.187.98.0/24 Valid RIR databaseAPNIC 673 100% 69
103.187.99.0/24 Valid RIR databaseAPNIC 673 100% 69
103.189.158.0/24 Valid RIR databaseAPNIC 673 100% 67
103.244.49.0/24 Valid RIR databaseAPNIC 673 100% 67
14.1.103.0/24 Valid RIR databaseAPNIC 672 100% 69
103.143.139.0/24 Valid RIR databaseAPNIC 672 100% 69
103.146.134.0/24 Valid RIR databaseAPNIC 672 100% 69
103.150.64.0/24 Valid RIR databaseAPNIC 672 100% 69
103.150.69.0/24 Valid RIR databaseAPNIC 672 100% 69
103.189.159.0/24 Valid RIR databaseAPNIC 672 100% 69
160.187.117.0/24 Valid RIR databaseAPNIC 672 100% 69
202.173.121.0/24 Valid RIR databaseAPNIC 672 100% 66
14.1.102.0/24 Valid RIR databaseAPNIC 671 100% 67
103.152.147.0/24 Valid RIR databaseAPNIC 670 100% 68
202.173.123.0/24 Valid RIR databaseAPNIC 670 100% 66
103.161.168.0/24 Valid RIR databaseAPNIC 666 99% 67
103.161.169.0/24 Valid RIR databaseAPNIC 666 99% 67
202.173.120.0/24 Valid RIR databaseAPNIC 666 99% 67
202.173.122.0/24 Valid RIR databaseAPNIC 666 99% 67
14.1.101.0/24 Valid RIR databaseAPNIC 665 99% 67
2401:c680:e::/48 Valid RIR databaseAPNIC 635 100% 69
2407:d40::/48 Valid RIR databaseAPNIC 635 100% 69
2407:d40:140::/48 Valid RIR databaseAPNIC 635 100% 69
2407:d40:126::/48 Valid RIR databaseAPNIC 634 100% 69
2407:d40:103::/48 Valid RIR databaseAPNIC 631 99% 67
2407:d40:f::/48 Valid RIR databaseAPNIC 630 99% 67
2407:d40:202::/48 Valid RIR databaseAPNIC 131 21% 48
2407:d40::/32 Valid RIR databaseAPNIC 126 20% 47
2407:d40:101::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:102::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:106::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:201::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:203::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:204::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:205::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:208::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:8004::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:8007::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:8009::/48 Valid RIR databaseAPNIC 126 20% 47
2407:d40:8011::/48 Valid RIR databaseAPNIC 124 19% 46
2407:d40:114::/48 Valid RIR databaseAPNIC 123 19% 45
2407:d40:8000::/48 Valid RIR databaseAPNIC 123 19% 45
2407:d40:108::/48 Valid RIR databaseAPNIC 13 2%low visibility 9
2407:d40:206::/48 Valid RIR databaseAPNIC 13 2%low visibility 9
2407:d40:207::/48 Valid RIR databaseAPNIC 13 2%low visibility 9
2407:d40:222::/48 Valid RIR databaseAPNIC 13 2%low visibility 9
2407:d40:10f::/48 Valid RIR databaseAPNIC 11 2%low visibility 6
103.161.168.0/23 Valid RIR databaseAPNIC 3 0%low visibility 3
2407:d40:107::/48 Valid RIR databaseAPNIC 3 0%low visibility 4
2407:d40:109::/48 Valid RIR databaseAPNIC 3 0%low visibility 4
14.1.100.0/24 Valid RIR databaseAPNIC 2 0%low visibility 3

AS-SET

PeeringDB's irr_as_set for AS139009: AS-WCL-BD. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS139009 isn't in the set, or no route object for AS139009 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS139009 in itNot covered
AS-WCL-BD APNIC3 member sets in no database: AS-149994, AS-152698, AS-DTIIG-139901 2,11429187,758 Yes 0

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

  • ROA: maxLength1
  • Route object: none1
  • AS-SET: missing member3
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: maxLength2407:d40:800c::/48ROA 2407:d40::/32 AS139009 has maxLength 32; the route is a /48. Raise the maxLength, or add a ROA for 2407:d40:800c::/48.8 of 636
Route object: none2407:d40:800c::/48No route object for it. A route object for 2407:d40::/32 with origin AS139009 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139009 in the RIR database for the space.8 of 636
AS-SET: missing memberAS-WCL-BDAS-WCL-BD (APNIC) lists AS-149994; no IRR database read has it.
AS-SET: missing memberAS-WCL-BDAS-WCL-BD (APNIC) lists AS-152698; no IRR database read has it.
AS-SET: missing memberAS-WCL-BDAS-WCL-BD (APNIC) lists AS-DTIIG-139901; no IRR database read has it.

Route objects not announced

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

14.1.102.0/23APNICValid
49.0.4.0/24APNICValid
103.129.208.0/24APNICValid
103.129.210.0/23APNICValid
103.129.210.0/24APNICValid
103.129.211.0/24APNICValid
103.133.204.0/22APNICValid
103.133.204.0/24APNICValid
103.133.205.0/24APNICValid
103.133.207.0/24APNICValid
103.152.102.0/23APNICValid
103.152.102.0/24APNICValid
103.152.103.0/24APNICValid
103.154.48.0/23APNICValid
103.187.98.0/23APNICValid
103.189.158.0/23APNICValid
202.173.120.0/22APNICValid
202.173.120.0/23APNICValid
202.173.122.0/23APNICValid
2001:470:1f3::/48ARINValid
2407:d40::/36APNICValid
2407:d40:100::/48APNICValid
2407:d40:122::/48APNICValid
2407:d40:142::/48APNICValid

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.