k.tkngh.jp — 唐津ネットワークサービス
Details
up since 2024-06-20 14:34 (6.2 days ago)
- Uptime: 99.98%
- Users: 9 (4 active this month, 9 active last six months)
- Posts: 2196
- Posts per user: 244.00
- Peers: 1927
- Version: kmyblue 4.3.0-alpha.3+kmyblue.12.0-dev
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-13 06:26 — 2024-06-26 19:36
users: 9 (0.00/day)
min/max/avg/stddev: 9 / 9 / 9.00 / 0.00
⋯ ⋯posts: 2196 (8.89/day)
min/max/avg/stddev: 2074 / 2196 / 2125.12 / 32.08
peers: 1927 (8.46/day)
min/max/avg/stddev: 1811 / 1927 / 1871.54 / 34.43
response_time: 2.501 (-0.07/day)
min/max/avg/stddev: 0 / 49 / 4.62 / 6.95
Crawling Info
First contact: 2024-03-26 (3.0 months ago)
Last successful contact: 2024-06-26 (15.3 minutes ago)
Contact: 8993 successful, 554 failed.
Average fetch time: 4.66s
Next attempt scheduled for 6.8 minutes from now.
Found through skaya.ligun.net (up)
IP address: 162.43.16.100 (and m.tkngh.jp.)
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-06-26 18:51:16 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 18:02:56 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 17:14:47 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 16:51:58 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 14:32:35 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 12:38:35 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 11:26:19 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 04:11:20 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 03:48:50 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- [2024-06-26 02:16:50 in 0.00s]: IP: 162.43.16.100 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-06-26 19:36:56 in 0.14s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 19:14:14 in 0.13s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 18:27:14 in 0.62s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 17:38:31 in 1.00s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 16:28:44 in 0.12s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 16:05:36 in 0.13s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 15:42:47 in 0.13s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 15:19:52 in 1.01s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 14:56:20 in 0.57s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 14:09:52 in 0.15s]: IP: 162.43.16.100 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-06-26 19:36:56 in 0.22s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 09:06:24 in 6.51s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-25 21:29:47 in 1.01s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-25 12:52:12 in 1.19s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-24 22:34:16 in 0.22s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-24 11:01:14 in 0.21s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-24 01:34:43 in 0.71s]: IP: 162.43.16.100 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-06-26 19:36:56 in 0.43s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 19:14:14 in 0.57s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 18:27:14 in 2.47s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 17:38:31 in 13.29s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 16:28:44 in 0.41s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 16:05:36 in 0.46s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 15:42:46 in 0.57s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 15:19:52 in 5.49s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 14:56:20 in 2.09s]: IP: 162.43.16.100 / OK / HTTP status: 200
- [2024-06-26 14:09:52 in 0.54s]: IP: 162.43.16.100 / OK / HTTP status: 200