bgpreport

Network · data from 2026-11-12

AS33391 SECURITY-FINANCE - SECURITY FINANCE CORPORATION OF SPARTANBURG

Registry name: SECURITY-FINANCE - SECURITY FINANCE CORPORATION OF SPARTANBURG, US · not in PeeringDB

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

Announced routes

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

74.113.17.0/24 No ROA Nonecovered by 74.113.16.0/22 672 100% 67
74.113.16.0/24 No ROA Other IRR onlyRADB 673 100% 67
74.113.18.0/24 No ROA Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none1
  • Route object: RIR2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none74.113.17.0/24No ROA covers it. Add a ROA for AS33391, maxLength 24.672 of 673
Route object: none74.113.17.0/24No route object for it. A route object for 74.113.16.0/22 with origin AS33391 covers it (filters allowing more-specifics accept it). Add a route object with origin AS33391 in the RIR database for the space.672 of 673
ROA: none74.113.16.0/24No ROA covers it. Add a ROA for AS33391, maxLength 24.673 of 673
Route object: RIR74.113.16.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none74.113.18.0/24No ROA covers it. Add a ROA for AS33391, maxLength 24.672 of 673
Route object: RIR74.113.18.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

70.150.24.0/23BBOI, RADBNo ROA
74.113.16.0/21RADBNo ROA
74.113.16.0/22RADBNo 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.