DNS response history for ns03.web-tennis.com

ns03.web-tennis.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 35 DNS check records, 35 successful responses, 0 failed responses, and 432 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.web-tennis.com.
Records on Selected Date

35

Historical checks stored for this nameserver on selected date

Average Latency

432 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-27 11:16

All timestamps shown in UTC

Latest Resolved IP on Selected Date

202.248.5.5

Most recently resolved hosting IP on selected date

Successful Responses

35

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 ns03.web-tennis.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
35 2026-08-27 11:16 639234253963286387
3 ms 202.248.5.5
34 2026-08-27 10:58 639234243654907465
270 ms 202.248.5.5
33 2026-08-27 10:41 639234233269654413
536 ms 202.248.5.5
32 2026-08-27 10:24 639234222943951923
264 ms 202.248.5.5
31 2026-08-27 10:07 639234212558002823
4 ms 202.248.5.5
30 2026-08-27 09:49 639234202117531850
506 ms 202.248.5.5
29 2026-08-27 09:32 639234191649612722
491 ms 202.248.5.5
28 2026-08-27 09:14 639234181105879568
589 ms 202.248.5.5
27 2026-08-27 08:57 639234170713214496
596 ms 202.248.5.5
26 2026-08-27 08:40 639234160341037652
572 ms 202.248.5.5
25 2026-08-27 08:22 639234149799404224
522 ms 202.248.5.5
24 2026-08-27 08:04 639234139553286469
526 ms 202.248.5.5
23 2026-08-27 07:11 639234107183588293
402 ms 202.248.5.5
22 2026-08-27 06:54 639234096905435724
648 ms 202.248.5.5
21 2026-08-27 06:36 639234086579410775
3 ms 202.248.5.5
20 2026-08-27 06:19 639234076291157956
574 ms 202.248.5.5
19 2026-08-27 06:02 639234065981939454
501 ms 202.248.5.5
18 2026-08-27 05:45 639234055548642997
508 ms 202.248.5.5
17 2026-08-27 05:28 639234045267979603
489 ms 202.248.5.5
16 2026-08-27 05:11 639234034999717463
504 ms 202.248.5.5
15 2026-08-27 04:53 639234024739225358
502 ms 202.248.5.5
14 2026-08-27 04:36 639234014311170162
507 ms 202.248.5.5
13 2026-08-27 04:19 639234003806017640
266 ms 202.248.5.5
12 2026-08-27 04:01 639233993356203030
507 ms 202.248.5.5
11 2026-08-27 03:08 639233961301716608
499 ms 202.248.5.5
10 2026-08-27 02:51 639233950834200647
496 ms 202.248.5.5
9 2026-08-27 02:33 639233940431849026
486 ms 202.248.5.5
8 2026-08-27 02:16 639233930110596398
592 ms 202.248.5.5
7 2026-08-27 01:59 639233919705434540
503 ms 202.248.5.5
6 2026-08-27 01:42 639233909452807845
495 ms 202.248.5.5
5 2026-08-27 01:24 639233899096420820
244 ms 202.248.5.5
4 2026-08-27 01:07 639233888707824939
244 ms 202.248.5.5
3 2026-08-27 00:50 639233878461203802
254 ms 202.248.5.5
2 2026-08-27 00:32 639233868060868209
512 ms 202.248.5.5
1 2026-08-27 00:15 639233857450922991
500 ms 202.248.5.5