DNS response history for ns2.ejbc.kr

ns2.ejbc.kr is a DNS nameserver monitored by NameServerHistory. This page provides historical DNS response-time data, nameserver uptime signals, DNS latency observations, resolved IP history, successful response counts, failed response counts, and reliability indicators for this nameserver.

The selected UTC date is 2026-08-25. For this date, NameServerHistory found 38 DNS check records, 38 successful responses, 0 failed responses, and 492 ms average response time. Current selected-date status: At least one successful DNS response was recorded for the selected date.

  • Use this report to investigate historical DNS uptime and nameserver reliability.
  • Compare DNS latency changes, failed DNS checks, and response behavior over time.
  • Review the latest resolved IP address and raw DNS check history for ns2.ejbc.kr.
Records on Selected Date

38

Historical checks stored for this nameserver on selected date

Average Latency

492 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 12:59

All timestamps shown in UTC

Latest Resolved IP on Selected Date

61.109.250.126

Most recently resolved hosting IP on selected date

Successful Responses

38

Checks that returned a measurable response

Failed Responses

0

Checks with no response or no returned latency

Failure Rate

0%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns2.ejbc.kr

Showing DNS history for 2026-08-25 UTC. Newest records appear first.

Latency bars are scaled to a maximum of 5000 ms for quick visual comparison.

# Query Time (UTC) Correlation ID Latency Response IP Address
38 2026-08-25 12:59 639232587225721862
546 ms 61.109.250.126
37 2026-08-25 12:42 639232576780683689
485 ms 61.109.250.126
36 2026-08-25 12:24 639232566381512620
542 ms 61.109.250.126
35 2026-08-25 12:07 639232556111768563
495 ms 61.109.250.126
34 2026-08-25 11:50 639232545839529039
466 ms 61.109.250.126
33 2026-08-25 11:33 639232535349285207
478 ms 61.109.250.126
32 2026-08-25 11:15 639232524938080723
486 ms 61.109.250.126
31 2026-08-25 10:22 639232492740373468
248 ms 61.109.250.126
30 2026-08-25 10:04 639232482235303141
475 ms 61.109.250.126
29 2026-08-25 09:47 639232471861770303
484 ms 61.109.250.126
28 2026-08-25 09:30 639232461630217327
553 ms 61.109.250.126
27 2026-08-25 09:12 639232451282965990
528 ms 61.109.250.126
26 2026-08-25 08:55 639232440814614938
542 ms 61.109.250.126
25 2026-08-25 08:38 639232430410720425
480 ms 61.109.250.126
24 2026-08-25 08:20 639232420003096185
538 ms 61.109.250.126
23 2026-08-25 08:03 639232409467287444
513 ms 61.109.250.126
22 2026-08-25 07:46 639232399077195997
500 ms 61.109.250.126
21 2026-08-25 07:28 639232388731528337
236 ms 61.109.250.126
20 2026-08-25 07:11 639232378288598612
467 ms 61.109.250.126
19 2026-08-25 06:17 639232346196373643
548 ms 61.109.250.126
18 2026-08-25 06:00 639232336112370741
529 ms 61.109.250.126
17 2026-08-25 05:44 639232326146508970
479 ms 61.109.250.126
16 2026-08-25 05:27 639232316189381720
537 ms 61.109.250.126
15 2026-08-25 05:10 639232306217998913
479 ms 61.109.250.126
14 2026-08-25 04:54 639232296255744174
513 ms 61.109.250.126
13 2026-08-25 04:37 639232286095760789
547 ms 61.109.250.126
12 2026-08-25 04:20 639232276086186273
527 ms 61.109.250.126
11 2026-08-25 04:03 639232265900986425
468 ms 61.109.250.126
10 2026-08-25 03:47 639232255723518075
504 ms 61.109.250.126
9 2026-08-25 03:29 639232245484452890
473 ms 61.109.250.126
8 2026-08-25 03:12 639232235157175331
537 ms 61.109.250.126
7 2026-08-25 02:19 639232203197189095
478 ms 61.109.250.126
6 2026-08-25 02:02 639232192844564298
465 ms 61.109.250.126
5 2026-08-25 01:45 639232182496008942
476 ms 61.109.250.126
4 2026-08-25 01:27 639232172197053132
506 ms 61.109.250.126
3 2026-08-25 00:34 639232140250307418
540 ms 61.109.250.126
2 2026-08-25 00:17 639232129927860324
479 ms 61.109.250.126
1 2026-08-25 00:00 639232119551972438
534 ms 61.109.250.126