bgpreport

Network · data from 2026-11-12

AS45402 SAMSUNGLIFESERVICE-AS-KR-KR - SAMSUNG LIFE SERVICE

Registry name: SAMSUNGLIFESERVICE-AS-KR-KR - SAMSUNG LIFE SERVICE, KR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45402, 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.
210.108.67.0/24 No ROA Other IRR onlyRADB 33 5%low visibility 26

AS-SET

AS45402 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 3 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none210.108.67.0/24No ROA covers it. Add a ROA for AS45402, maxLength 24.33 of 673
Route object: RIR210.108.67.0/24Route object only in RADB. Add it in the RIR database for the space.33 of 673

Route objects not announced

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

21.108.67.0/24RADBNo 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.