misskey.takahe.socialDetails
up since 2024-06-12 23:03 (22.9 days ago)
- Uptime: 94.78%
- Users: 198
- Posts: 3455
- Posts per user: 17.45
- Peers: 11911
- Version: takahe 0.10.1
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-21 21:04 — 2024-07-05 20:29
users: 198 (0.00/day)
min/max/avg/stddev: 198 / 198 / 198.00 / 0.00
⋯ ⋯posts: 3455 (0.00/day)
min/max/avg/stddev: 3455 / 3455 / 3455.00 / 0.00
⋯ ⋯peers: 11911 (3.75/day)
min/max/avg/stddev: 11859 / 11911 / 11885.80 / 15.03
response_time: 1.925 (-2.43/day)
min/max/avg/stddev: 0 / 61 / 11.01 / 14.06
Crawling Info
First contact: 2023-08-17 (10.6 months ago)
Last successful contact: 2024-07-05 (44.4 minutes ago)
Latest attempt: 2024-07-05 (7.1 minutes ago)
Contact: 10148 successful, 1405 failed.
Average fetch time: 11.01s
Next attempt scheduled for 28.9 minutes from now.
Found through fedi.mtth.org (up)
IP address: 104.198.180.195 (and 6 others: feditest-service.aeracode.org (down), feditest.aeracode.org (down), shuuji3.takahe.social (up), fedi.mtth.org (up), jointakahe.takahe.social (up), takahe.social (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 17:22:56 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-05 16:46:10 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-05 04:15:21 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-05 02:19:21 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-04 23:04:09 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-04 19:09:07 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-04 15:49:42 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-04 12:29:16 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-04 11:09:20 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- [2024-07-04 05:42:38 in 0.00s]: IP: 104.198.180.195 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 19:52:36 in 0.22s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 19:15:41 in 0.22s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 18:37:43 in 0.13s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 18:00:07 in 0.23s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 16:08:29 in 0.14s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 15:30:51 in 0.18s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 14:53:53 in 0.44s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 14:17:00 in 0.12s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 13:40:48 in 0.14s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 13:04:56 in 0.20s]: IP: 104.198.180.195 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 14:53:53 in 0.58s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 02:57:56 in 0.29s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-04 00:49:56 in 0.30s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-03 08:12:13 in 1.04s]: IP: 104.198.180.195 / OK / HTTP status: 200
- /nodeinfo/2.0/ ₍⇗₎
- [2024-07-05 20:29:50 in 0.45s]: IP: 104.198.180.195 / Error: unparseable / HTTP status: 200
- [2024-07-05 19:52:36 in 1.00s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 19:15:41 in 0.74s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 18:37:43 in 1.04s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 18:00:06 in 1.19s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 16:08:29 in 0.92s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 15:30:51 in 1.02s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 14:53:53 in 2.87s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 14:17:00 in 0.77s]: IP: 104.198.180.195 / OK / HTTP status: 200
- [2024-07-05 13:40:48 in 0.83s]: IP: 104.198.180.195 / OK / HTTP status: 200