DNS response history for dns2.phs.com

dns2.phs.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-28. For this date, NameServerHistory found 32 DNS check records, 32 successful responses, 0 failed responses, and 444 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 dns2.phs.com.
Records on Selected Date

32

Historical checks stored for this nameserver on selected date

Average Latency

444 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-28 13:25

All timestamps shown in UTC

Latest Resolved IP on Selected Date

149.111.120.109

Most recently resolved hosting IP on selected date

Successful Responses

32

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 dns2.phs.com

Showing DNS history for 2026-08-28 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-28 13:25 639235195230848570
521 ms 149.111.120.109
31 2026-08-28 13:07 639235184840503274
514 ms 149.111.120.109
30 2026-08-28 12:50 639235174453894956
521 ms 149.111.120.109
29 2026-08-28 12:32 639235163898672622
66 ms 149.111.120.109
28 2026-08-28 11:39 639235132147470568
17 ms 149.111.120.109
27 2026-08-28 11:22 639235121907744088
517 ms 149.111.120.109
26 2026-08-28 11:05 639235111428014262
515 ms 149.111.120.109
25 2026-08-28 10:48 639235100921813626
12 ms 149.111.120.109
24 2026-08-28 09:54 639235068670703481
518 ms 149.111.120.109
23 2026-08-28 09:36 639235058337459445
511 ms 149.111.120.109
22 2026-08-28 09:19 639235047825109146
518 ms 149.111.120.109
21 2026-08-28 09:02 639235037383229033
518 ms 149.111.120.109
20 2026-08-28 08:08 639235005619242711
516 ms 149.111.120.109
19 2026-08-28 07:51 639234995310346584
517 ms 149.111.120.109
18 2026-08-28 07:34 639234984946548933
129 ms 149.111.120.109
17 2026-08-28 07:17 639234974608077290
521 ms 149.111.120.109
16 2026-08-28 06:23 639234942529845595
11 ms 149.111.120.109
15 2026-08-28 06:06 639234932259126627
2044 ms 149.111.120.109
14 2026-08-28 05:49 639234921916735988
518 ms 149.111.120.109
13 2026-08-28 05:32 639234911470038027
519 ms 149.111.120.109
12 2026-08-28 04:39 639234879588411654
131 ms 149.111.120.109
11 2026-08-28 04:21 639234869341589104
528 ms 149.111.120.109
10 2026-08-28 04:04 639234859012216675
18 ms 149.111.120.109
9 2026-08-28 03:47 639234848695364934
518 ms 149.111.120.109
8 2026-08-28 02:54 639234816952458162
212 ms 149.111.120.109
7 2026-08-28 02:37 639234806773081598
189 ms 149.111.120.109
6 2026-08-28 02:20 639234796382955255
511 ms 149.111.120.109
5 2026-08-28 02:03 639234786015782563
515 ms 149.111.120.109
4 2026-08-28 01:09 639234753811917646
513 ms 149.111.120.109
3 2026-08-28 00:52 639234743739767811
514 ms 149.111.120.109
2 2026-08-28 00:35 639234733372362811
514 ms 149.111.120.109
1 2026-08-28 00:18 639234723048550337
516 ms 149.111.120.109