bgpreport

Network · data from 2026-11-12

AS400268 SWIFTCURRENT

Registry name: SWIFTCURRENT-CONNECT - Pierce Pepin Cooperative Services, US · PeeringDB

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

Announced routes

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

152.55.128.0/21 Valid Nonecovered by 152.55.128.0/20 673 100% 67
140.106.32.0/21 Valid Nonecovered by 140.106.32.0/20 669 99% 67
140.106.40.0/21 Valid Nonecovered by 140.106.32.0/20 669 99% 67
140.106.47.0/24 Valid Nonecovered by 140.106.32.0/20 669 99% 67
160.79.98.0/24 Valid Nonecovered by 160.79.96.0/21 669 99% 67
66.129.32.0/22 Valid Nonecovered by 66.129.32.0/21 667 99% 67
66.129.36.0/22 Valid Nonecovered by 66.129.32.0/21 667 99% 67
160.79.96.0/22 Valid Nonecovered by 160.79.96.0/21 667 99% 67
160.79.100.0/22 Valid Nonecovered by 160.79.96.0/21 667 99% 67
66.129.32.0/23 Valid Nonecovered by 66.129.32.0/21 98 15% 37
66.129.34.0/23 Valid Nonecovered by 66.129.32.0/21 98 15% 37
66.129.38.0/23 Valid Nonecovered by 66.129.32.0/21 98 15% 37
140.106.32.0/22 Valid Nonecovered by 140.106.32.0/20 98 15% 37
140.106.36.0/22 Valid Nonecovered by 140.106.32.0/20 98 15% 37
140.106.40.0/22 Valid Nonecovered by 140.106.32.0/20 98 15% 37
140.106.44.0/22 Valid Nonecovered by 140.106.32.0/20 98 15% 37
152.55.128.0/22 Valid Nonecovered by 152.55.128.0/20 98 15% 37
160.79.96.0/23 Valid Nonecovered by 160.79.96.0/21 98 15% 37
160.79.98.0/23 Valid Nonecovered by 160.79.96.0/21 98 15% 37
160.79.100.0/23 Valid Nonecovered by 160.79.96.0/21 98 15% 37
160.79.102.0/23 Valid Nonecovered by 160.79.96.0/21 98 15% 37
152.55.128.0/20 Valid RIR databaseARIN 673 100% 67
66.129.32.0/21 Valid RIR databaseARIN 669 99% 67
140.106.32.0/20 Valid RIR databaseARIN 669 99% 67
160.79.96.0/21 Valid RIR databaseARIN 669 99% 67
2606:79c0::/32 Valid RIR databaseARIN 635 100% 67

AS-SET

AS400268's PeeringDB record names no 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 21 are in fix.csv.

  • Route object: none21
ChangePrefix or setDetailFull-table peers
Route object: none152.55.128.0/21No route object for it. A route object for 152.55.128.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.673 of 673
Route object: none140.106.32.0/21No route object for it. A route object for 140.106.32.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.669 of 673
Route object: none140.106.40.0/21No route object for it. A route object for 140.106.32.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.669 of 673
Route object: none140.106.47.0/24No route object for it. A route object for 140.106.32.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.669 of 673
Route object: none160.79.98.0/24No route object for it. A route object for 160.79.96.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.669 of 673
Route object: none66.129.32.0/22No route object for it. A route object for 66.129.32.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.667 of 673
Route object: none66.129.36.0/22No route object for it. A route object for 66.129.32.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.667 of 673
Route object: none160.79.96.0/22No route object for it. A route object for 160.79.96.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.667 of 673
Route object: none160.79.100.0/22No route object for it. A route object for 160.79.96.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.667 of 673
Route object: none66.129.32.0/23No route object for it. A route object for 66.129.32.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none66.129.34.0/23No route object for it. A route object for 66.129.32.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none66.129.38.0/23No route object for it. A route object for 66.129.32.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none140.106.32.0/22No route object for it. A route object for 140.106.32.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none140.106.36.0/22No route object for it. A route object for 140.106.32.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none140.106.40.0/22No route object for it. A route object for 140.106.32.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none140.106.44.0/22No route object for it. A route object for 140.106.32.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none152.55.128.0/22No route object for it. A route object for 152.55.128.0/20 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none160.79.96.0/23No route object for it. A route object for 160.79.96.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none160.79.98.0/23No route object for it. A route object for 160.79.96.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none160.79.100.0/23No route object for it. A route object for 160.79.96.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673
Route object: none160.79.102.0/23No route object for it. A route object for 160.79.96.0/21 with origin AS400268 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400268 in the RIR database for the space.98 of 673

Route objects not announced

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