DNS response history for ns03.jimdo-server.com

ns03.jimdo-server.com 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-27. For this date, NameServerHistory found 32 DNS check records, 31 successful responses, 1 failed responses, and 175 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 ns03.jimdo-server.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

175 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 10:14

All timestamps shown in UTC

Latest Resolved IP on Selected Date

89.146.248.4

Most recently resolved hosting IP on selected date

Successful Responses

31

Checks that returned a measurable response

Failed Responses

1

Checks with no response or no returned latency

Failure Rate

3%

Based on the selected date history

Selected Date Status

Responsive

At least one successful response exists on selected date

History for ns03.jimdo-server.com

Showing DNS history for 2026-08-27 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
32 2026-08-27 10:14 639234222943951923
39 ms 89.146.248.4
31 2026-08-27 09:57 639234212558002823
21 ms 89.146.248.4
30 2026-08-27 09:40 639234202117531850
29 ms 89.146.248.4
29 2026-08-27 09:22 639234191649612722
130 ms 89.146.248.4
28 2026-08-27 09:05 639234181105879568
15 ms 89.146.248.4
27 2026-08-27 08:47 639234170713214496
16 ms 89.146.248.4
26 2026-08-27 08:30 639234160341037652
12 ms 89.146.248.4
25 2026-08-27 08:13 639234149799404224
2022 ms 89.146.248.4
24 2026-08-27 07:56 639234139553286469
16 ms 89.146.248.4
23 2026-08-27 07:02 639234107183588293
21 ms 89.146.248.4
22 2026-08-27 06:44 639234096905435724
253 ms 89.146.248.4
21 2026-08-27 06:27 639234086579410775
13 ms 89.146.248.4
20 2026-08-27 06:10 639234076291157956
33 ms 89.146.248.4
19 2026-08-27 05:53 639234065981939454
30 ms 89.146.248.4
18 2026-08-27 05:36 639234055548642997
17 ms 89.146.248.4
17 2026-08-27 05:18 639234045267979603
144 ms 89.146.248.4
16 2026-08-27 05:01 639234034999717463
17 ms 89.146.248.4
15 2026-08-27 04:44 639234024739225358
15 ms 89.146.248.4
14 2026-08-27 04:27 639234014311170162
-
13 2026-08-27 04:09 639234003806017640
46 ms 89.146.248.4
12 2026-08-27 03:52 639233993356203030
55 ms 89.146.248.4
11 2026-08-27 02:59 639233961301716608
15 ms 89.146.248.4
10 2026-08-27 02:41 639233950834200647
48 ms 89.146.248.4
9 2026-08-27 02:24 639233940431849026
11 ms 89.146.248.4
8 2026-08-27 02:06 639233930110596398
141 ms 89.146.248.4
7 2026-08-27 01:49 639233919705434540
19 ms 89.146.248.4
6 2026-08-27 01:32 639233909452807845
2047 ms 89.146.248.4
5 2026-08-27 01:15 639233899096420820
60 ms 89.146.248.4
4 2026-08-27 00:58 639233888707824939
32 ms 89.146.248.4
3 2026-08-27 00:40 639233878461203802
24 ms 89.146.248.4
2 2026-08-27 00:23 639233868060868209
20 ms 89.146.248.4
1 2026-08-27 00:05 639233857450922991
72 ms 89.146.248.4