bgpreport

Network · data from 2026-11-12

AS54552 SP-US-EAST1 - Samaritan's Purse

Registry name: SP-US-EAST1 - Samaritan's Purse, US · not in PeeringDB

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

Announced routes

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

91.132.80.0/22 Valid Other IRR onlyRADB 673 100% 67
185.234.253.0/24 Valid Other IRR onlyRADB 673 100% 67
23.138.144.0/24 Valid RIR databaseARIN, RADB 673 100% 67

AS-SET

AS54552 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 11 are in fix.csv.

  • Route object: RIR2
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: RIR91.132.80.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR185.234.253.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

74.123.116.0/22RADBValid
74.123.116.0/23ARINValid
216.39.244.0/22ARIN, RADBValid
216.39.244.0/24ARINValid
216.39.245.0/24ARINValid
216.39.246.0/24ARINValid
216.39.247.0/24ARINValid
2620:13f:b000::/44RADBValid
2a13:ac0::/29RADBNo 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.