DNS response history for ns1.jem.net

ns1.jem.net 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 28 DNS check records, 28 successful responses, 0 failed responses, and 812 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 ns1.jem.net.
Records on Selected Date

28

Historical checks stored for this nameserver on selected date

Average Latency

812 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-25 09:32

All timestamps shown in UTC

Latest Resolved IP on Selected Date

207.148.248.143

Most recently resolved hosting IP on selected date

Successful Responses

28

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 ns1.jem.net

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
28 2026-08-25 09:32 639232461630217327
4545 ms 207.148.248.143
27 2026-08-25 09:15 639232451282965990
2810 ms 207.148.248.143
26 2026-08-25 08:58 639232440814614938
8 ms 207.148.248.143
25 2026-08-25 08:40 639232430410720425
5 ms 207.148.248.143
24 2026-08-25 08:23 639232420003096185
187 ms 207.148.248.143
23 2026-08-25 08:05 639232409467287444
92 ms 207.148.248.143
22 2026-08-25 07:48 639232399077195997
109 ms 207.148.248.143
21 2026-08-25 07:30 639232388731528337
104 ms 207.148.248.143
20 2026-08-25 07:13 639232378288598612
601 ms 207.148.248.143
19 2026-08-25 06:19 639232346196373643
1508 ms 207.148.248.143
18 2026-08-25 06:02 639232336112370741
1510 ms 207.148.248.143
17 2026-08-25 05:46 639232326146508970
92 ms 207.148.248.143
16 2026-08-25 05:29 639232316189381720
2 ms 207.148.248.143
15 2026-08-25 05:12 639232306217998913
2605 ms 207.148.248.143
14 2026-08-25 04:56 639232296255744174
1603 ms 207.148.248.143
13 2026-08-25 04:39 639232286095760789
601 ms 207.148.248.143
12 2026-08-25 04:22 639232276086186273
600 ms 207.148.248.143
11 2026-08-25 04:05 639232265900986425
96 ms 207.148.248.143
10 2026-08-25 03:49 639232255723518075
1684 ms 207.148.248.143
9 2026-08-25 03:32 639232245484452890
592 ms 207.148.248.143
8 2026-08-25 03:15 639232235157175331
595 ms 207.148.248.143
7 2026-08-25 02:21 639232203197189095
99 ms 207.148.248.143
6 2026-08-25 02:04 639232192844564298
93 ms 207.148.248.143
5 2026-08-25 01:47 639232182496008942
98 ms 207.148.248.143
4 2026-08-25 01:29 639232172197053132
94 ms 207.148.248.143
3 2026-08-25 00:36 639232140250307418
183 ms 207.148.248.143
2 2026-08-25 00:19 639232129927860324
100 ms 207.148.248.143
1 2026-08-25 00:02 639232119551972438
2109 ms 207.148.248.143