DNS response history for ns2.swe.jp

ns2.swe.jp 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-26. For this date, NameServerHistory found 31 DNS check records, 31 successful responses, 0 failed responses, and 547 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.swe.jp.
Records on Selected Date

31

Historical checks stored for this nameserver on selected date

Average Latency

547 ms

Calculated from available response records

Latest Check on Selected Date

2026-08-26 09:53

All timestamps shown in UTC

Latest Resolved IP on Selected Date

160.16.206.138

Most recently resolved hosting IP on selected date

Successful Responses

31

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.swe.jp

Showing DNS history for 2026-08-26 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
31 2026-08-26 09:53 639233339545274518
513 ms 160.16.206.138
30 2026-08-26 09:36 639233329214918079
552 ms 160.16.206.138
29 2026-08-26 09:18 639233318749762337
560 ms 160.16.206.138
28 2026-08-26 09:01 639233308387917838
557 ms 160.16.206.138
27 2026-08-26 08:44 639233297961740122
511 ms 160.16.206.138
26 2026-08-26 08:26 639233287487159094
513 ms 160.16.206.138
25 2026-08-26 08:09 639233276995531707
510 ms 160.16.206.138
24 2026-08-26 07:51 639233266521568229
517 ms 160.16.206.138
23 2026-08-26 07:34 639233256081047431
503 ms 160.16.206.138
22 2026-08-26 06:40 639233223620132921
514 ms 160.16.206.138
21 2026-08-26 06:23 639233213287814244
506 ms 160.16.206.138
20 2026-08-26 06:05 639233202925983161
552 ms 160.16.206.138
19 2026-08-26 05:48 639233192644780696
506 ms 160.16.206.138
18 2026-08-26 05:31 639233182401183833
555 ms 160.16.206.138
17 2026-08-26 05:14 639233172074181051
530 ms 160.16.206.138
16 2026-08-26 04:57 639233161808421455
494 ms 160.16.206.138
15 2026-08-26 04:39 639233151357344052
711 ms 160.16.206.138
14 2026-08-26 04:22 639233141034116946
511 ms 160.16.206.138
13 2026-08-26 04:05 639233130828334142
541 ms 160.16.206.138
12 2026-08-26 03:48 639233120373450007
555 ms 160.16.206.138
11 2026-08-26 03:30 639233110066216193
554 ms 160.16.206.138
10 2026-08-26 02:37 639233078065410564
528 ms 160.16.206.138
9 2026-08-26 02:20 639233067787457832
761 ms 160.16.206.138
8 2026-08-26 02:03 639233057501801162
500 ms 160.16.206.138
7 2026-08-26 01:46 639233047089431703
519 ms 160.16.206.138
6 2026-08-26 01:28 639233036754790688
487 ms 160.16.206.138
5 2026-08-26 01:11 639233026412602472
577 ms 160.16.206.138
4 2026-08-26 00:54 639233016064066127
519 ms 160.16.206.138
3 2026-08-26 00:37 639233005922655772
518 ms 160.16.206.138
2 2026-08-26 00:20 639232995672256907
774 ms 160.16.206.138
1 2026-08-26 00:03 639232985300872416
506 ms 160.16.206.138