bgpreport

Network · data from 2026-11-12

AS394611 South Central Power Company

Registry name: SOUTHCENTRALPOWER - South Central Power Company, US · PeeringDB

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

Announced routes

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

2607:62c0::/40 No ROA Nonecovered by 2607:62c0::/32 602 95% 67
66.251.240.0/20 No ROA Other IRR onlyRADB 673 100% 67
66.251.242.0/23 No ROA Other IRR onlyRADB 671 100% 67
173.243.236.0/24 No ROA Other IRR onlyRADB 668 99% 67
66.251.240.0/23 No ROA Other IRR onlyRADB 665 99% 67
2607:62c0::/32 No ROA Other IRR onlyRADB 635 100% 69
2607:62c0:100::/41 No ROA Other IRR onlyRADB 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS394611: AS394611:AS-SCP. 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 (AS394611 isn't in the set, or no route object for AS394611 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 objectsAS394611 in itNot covered
AS394611:AS-SCP RADB 116 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 14 are in fix.csv.

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none2607:62c0::/40No ROA covers it. Add a ROA for AS394611, maxLength 40.602 of 636
Route object: none2607:62c0::/40No route object for it. A route object for 2607:62c0::/32 with origin AS394611 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394611 in the RIR database for the space.602 of 636
ROA: none66.251.240.0/20No ROA covers it. Add a ROA for AS394611, maxLength 20.673 of 673
Route object: RIR66.251.240.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none66.251.242.0/23No ROA covers it. Add a ROA for AS394611, maxLength 23.671 of 673
Route object: RIR66.251.242.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none173.243.236.0/24No ROA covers it. Add a ROA for AS394611, maxLength 24.668 of 673
Route object: RIR173.243.236.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none66.251.240.0/23No ROA covers it. Add a ROA for AS394611, maxLength 23.665 of 673
Route object: RIR66.251.240.0/23Route object only in RADB. Add it in the RIR database for the space.665 of 673
ROA: none2607:62c0::/32No ROA covers it. Add a ROA for AS394611, maxLength 32.635 of 636
Route object: RIR2607:62c0::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2607:62c0:100::/41No ROA covers it. Add a ROA for AS394611, maxLength 41.634 of 636
Route object: RIR2607:62c0:100::/41Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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