Network · data from 2026-11-12
AS19113 DUKE-ENERGY - Duke Energy Corporation
Registry name: DUKE-ENERGY - Duke Energy Corporation, US · not in PeeringDB
14IPv4 routes
0.0% RPKI valid · 21.4% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
14No ROA
11 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
8Route objects not announced
registered with origin AS19113, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS19113, 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.
| 148.134.248.0/24 | No ROA | Nonecovered by 148.134.0.0/16 | 673 100% |
| 148.134.249.0/24 | No ROA | Nonecovered by 148.134.0.0/16 | 673 100% |
| 159.110.138.0/23 | No ROA | None | 673 100% |
| 148.134.240.0/24 | No ROA | Nonecovered by 148.134.0.0/16 | 672 100% |
| 148.134.241.0/24 | No ROA | Nonecovered by 148.134.0.0/16 | 672 100% |
| 159.110.14.0/23 | No ROA | None | 672 100% |
| 159.110.132.0/22 | No ROA | None | 672 100% |
| 159.110.0.0/19 | No ROA | None | 671 100% |
| 159.110.128.0/19 | No ROA | None | 671 100% |
| 192.234.125.0/24 | No ROA | None | 671 100% |
| 192.234.128.0/24 | No ROA | None | 671 100% |
| 192.234.122.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 192.234.123.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
| 192.234.127.0/24 | No ROA | Other IRR onlyRADB | 671 100% |
AS-SET
AS19113 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 36 are in fix.csv.
- ROA: none14
- Route object: none11
- Route object: RIR3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 148.134.248.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: none | 148.134.248.0/24 | No route object for it. A route object for 148.134.0.0/16 with origin AS19113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 148.134.249.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: none | 148.134.249.0/24 | No route object for it. A route object for 148.134.0.0/16 with origin AS19113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 159.110.138.0/23 | No ROA covers it. Add a ROA for AS19113, maxLength 23. |
| Route object: none | 159.110.138.0/23 | No route object for it. Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 148.134.240.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: none | 148.134.240.0/24 | No route object for it. A route object for 148.134.0.0/16 with origin AS19113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 148.134.241.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: none | 148.134.241.0/24 | No route object for it. A route object for 148.134.0.0/16 with origin AS19113 covers it (filters allowing more-specifics accept it). Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 159.110.14.0/23 | No ROA covers it. Add a ROA for AS19113, maxLength 23. |
| Route object: none | 159.110.14.0/23 | No route object for it. Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 159.110.132.0/22 | No ROA covers it. Add a ROA for AS19113, maxLength 22. |
| Route object: none | 159.110.132.0/22 | No route object for it. Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 159.110.0.0/19 | No ROA covers it. Add a ROA for AS19113, maxLength 19. |
| Route object: none | 159.110.0.0/19 | No route object for it. Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 159.110.128.0/19 | No ROA covers it. Add a ROA for AS19113, maxLength 19. |
| Route object: none | 159.110.128.0/19 | No route object for it. Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 192.234.125.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: none | 192.234.125.0/24 | No route object for it. Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 192.234.128.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: none | 192.234.128.0/24 | No route object for it. Add a route object with origin AS19113 in the RIR database for the space. |
| ROA: none | 192.234.122.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: RIR | 192.234.122.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.234.123.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: RIR | 192.234.123.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 192.234.127.0/24 | No ROA covers it. Add a ROA for AS19113, maxLength 24. |
| Route object: RIR | 192.234.127.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS19113 whose prefix no peer sees AS19113 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 139.46.0.0/16 | RADB | No ROA |
| 148.134.0.0/16 | RADB | No ROA |
| 162.113.0.0/16 | RADB | No ROA |
| 192.195.243.0/24 | RADB | No ROA |
| 192.234.124.0/24 | RADB | No ROA |
| 192.234.126.0/24 | RADB | No ROA |
| 192.234.167.0/24 | RADB | No ROA |
| 2406:10::/32 | RADB | No ROA |
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.