Network · data from 2026-11-12
AS213800 asdf JAIYEON SIM
Registry name: asdf JAIYEON SIM, KR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213800, 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.
| 45.207.58.0/24 | Invalid: origin | RIR databaseAFRINIC | 1 0%low visibility |
| 151.243.151.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
AS-SET
AS213800 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 2 are in fix.csv.
- ROA: origin1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.207.58.0/24 | ROAs covering it name AS17561, AS152726, not AS213800. If AS213800 should announce it, add a ROA for AS213800. |
Route objects not announced
Route objects with origin AS213800 whose prefix no peer sees AS213800 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 199.177.177.0/24 | ALTDB | No 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.