bgpreport

Network · data from 2026-11-12

AS11620 SUCCEED-NET - Succeed.Net

Registry name: SUCCEED-NET - Succeed.Net, US · not in PeeringDB

28IPv4 routes 92.9% RPKI valid · 50.0% with a route object
0IPv6 routes
2RPKI invalid 0 origin · 2 maxLength
0No ROA 14 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS11620, seen from no peer

Announced routes

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

207.173.132.0/23 Invalid: maxLength Nonecovered by 207.173.128.0/20 44 7%low visibility 27
207.173.134.0/23 Invalid: maxLength Nonecovered by 207.173.128.0/20 44 7%low visibility 27
64.57.96.0/24 Valid Nonecovered by 64.57.96.0/21 672 100% 67
64.57.100.0/24 Valid Nonecovered by 64.57.96.0/21 672 100% 67
64.57.108.0/22 Valid Nonecovered by 64.57.104.0/21 672 100% 67
66.255.224.0/24 Valid Nonecovered by 66.255.224.0/21 672 100% 67
66.255.227.0/24 Valid Nonecovered by 66.255.224.0/21 672 100% 67
66.255.228.0/22 Valid Nonecovered by 66.255.224.0/21 672 100% 67
66.255.236.0/23 Valid Nonecovered by 66.255.232.0/21 672 100% 67
66.255.239.0/24 Valid Nonecovered by 66.255.232.0/21 672 100% 67
147.124.32.0/22 Valid Nonecovered by 147.124.32.0/21 672 100% 67
147.124.32.0/24 Valid Nonecovered by 147.124.32.0/21 672 100% 67
74.116.200.0/24 Valid Nonecovered by 74.116.200.0/22 671 100% 67
74.116.204.0/24 Valid Nonecovered by 74.116.204.0/22 671 100% 67
64.57.101.0/24 Valid Other IRR onlyRADB 672 100% 67
64.57.104.0/24 Valid Other IRR onlyRADB 672 100% 67
64.57.107.0/24 Valid Other IRR onlyRADB 672 100% 67
64.57.108.0/24 Valid Other IRR onlyRADB 672 100% 67
207.173.128.0/20 Valid Other IRR onlyRADB 672 100% 67
64.57.96.0/20 Valid RIR databaseARIN, RADB 672 100% 67
64.57.96.0/21 Valid RIR databaseARIN 672 100% 67
64.57.104.0/21 Valid RIR databaseARIN, RADB 672 100% 67
66.255.224.0/20 Valid RIR databaseARIN, RADB 672 100% 67
66.255.224.0/21 Valid RIR databaseARIN 672 100% 67
66.255.232.0/21 Valid RIR databaseARIN 672 100% 67
74.116.200.0/21 Valid RIR databaseARIN, RADB 672 100% 67
147.124.32.0/20 Valid RIR databaseARIN, RADB 672 100% 67
147.124.32.0/21 Valid RIR databaseARIN 672 100% 67

AS-SET

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

  • ROA: maxLength2
  • Route object: none14
  • Route object: RIR5
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: maxLength207.173.132.0/23ROA 207.173.128.0/20 AS11620 has maxLength 20; the route is a /23. Raise the maxLength, or add a ROA for 207.173.132.0/23.44 of 673
Route object: none207.173.132.0/23No route object for it. A route object for 207.173.128.0/20 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.44 of 673
ROA: maxLength207.173.134.0/23ROA 207.173.128.0/20 AS11620 has maxLength 20; the route is a /23. Raise the maxLength, or add a ROA for 207.173.134.0/23.44 of 673
Route object: none207.173.134.0/23No route object for it. A route object for 207.173.128.0/20 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.44 of 673
Route object: none64.57.96.0/24No route object for it. A route object for 64.57.96.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none64.57.100.0/24No route object for it. A route object for 64.57.96.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none64.57.108.0/22No route object for it. A route object for 64.57.104.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none66.255.224.0/24No route object for it. A route object for 66.255.224.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none66.255.227.0/24No route object for it. A route object for 66.255.224.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none66.255.228.0/22No route object for it. A route object for 66.255.224.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none66.255.236.0/23No route object for it. A route object for 66.255.232.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none66.255.239.0/24No route object for it. A route object for 66.255.232.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none147.124.32.0/22No route object for it. A route object for 147.124.32.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none147.124.32.0/24No route object for it. A route object for 147.124.32.0/21 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.672 of 673
Route object: none74.116.200.0/24No route object for it. A route object for 74.116.200.0/22 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.671 of 673
Route object: none74.116.204.0/24No route object for it. A route object for 74.116.204.0/22 with origin AS11620 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11620 in the RIR database for the space.671 of 673
Route object: RIR64.57.101.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR64.57.104.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR64.57.107.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR64.57.108.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR207.173.128.0/20Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

74.116.200.0/22ARINValid
74.116.204.0/22ARINValid
147.124.40.0/21ARINValid
209.210.251.0/24ARIN, RADBValid
2605:8740::/28ARIN, RADBValid

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.