Network · data from 2026-11-12

AS55633 DMC-AS-KR-KR - pundang jesaeng general hospital

Registry name: DMC-AS-KR-KR - pundang jesaeng general hospital, KR · not in PeeringDB

4IPv4 routes 0.0% RPKI valid · 25.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

4No ROA 3 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS55633, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS55633, 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.104.112.0/24	No ROA	Other origin only	673 100%	67
221.163.211.128/27	No ROA	None	14 2%low visibility	13
210.120.2.72/29	No ROA	None	10 1%low visibility	10
1.209.184.0/24	No ROA	Other IRR onlyRADB	673 100%	67

210.104.112.0/24

No ROA

Other origin only

673 100%

221.163.211.128/27

No ROA

None

14 2%low visibility

210.120.2.72/29

No ROA

None

10 1%low visibility

1.209.184.0/24

No ROA

Other IRR onlyRADB

673 100%

AS-SET

AS55633 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 8 are in fix.csv.

ROA: none4
Route object: none3
Route object: RIR1

Change	Prefix or set	Detail	Full-table peers
ROA: none	210.104.112.0/24	No ROA covers it. Add a ROA for AS55633, maxLength 24.	673 of 673
Route object: none	210.104.112.0/24	Route objects for it name AS4766. Add a route object with origin AS55633 in the RIR database for the space.	673 of 673
ROA: none	221.163.211.128/27	No ROA covers it. Add a ROA for AS55633, maxLength 27.	14 of 673
Route object: none	221.163.211.128/27	No route object for it. Add a route object with origin AS55633 in the RIR database for the space.	14 of 673
ROA: none	210.120.2.72/29	No ROA covers it. Add a ROA for AS55633, maxLength 29.	10 of 673
Route object: none	210.120.2.72/29	No route object for it. Add a route object with origin AS55633 in the RIR database for the space.	10 of 673
ROA: none	1.209.184.0/24	No ROA covers it. Add a ROA for AS55633, maxLength 24.	673 of 673
Route object: RIR	1.209.184.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

210.104.112.0/24

No ROA covers it. Add a ROA for AS55633, maxLength 24.

673 of 673

Route object: none

210.104.112.0/24

Route objects for it name AS4766. Add a route object with origin AS55633 in the RIR database for the space.

673 of 673

ROA: none

221.163.211.128/27

No ROA covers it. Add a ROA for AS55633, maxLength 27.

14 of 673

Route object: none

221.163.211.128/27

No route object for it. Add a route object with origin AS55633 in the RIR database for the space.

14 of 673

ROA: none

210.120.2.72/29

No ROA covers it. Add a ROA for AS55633, maxLength 29.

10 of 673

Route object: none

210.120.2.72/29

No route object for it. Add a route object with origin AS55633 in the RIR database for the space.

10 of 673

ROA: none

1.209.184.0/24

No ROA covers it. Add a ROA for AS55633, maxLength 24.

673 of 673

Route object: RIR

1.209.184.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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