yunase.com — Mastodon
Details
up since 2024-06-07 04:34 (24.3 days ago)
- Uptime: 99.76%
- Users: 1 (0 active this month, 1 active last six months)
- Posts: 2
- Posts per user: 2.00
- Peers: 24
- Version: mastodon 4.2.9
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-30 23:26 — 2024-07-01 12:32
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ —posts: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ —peers: 24 (0.04/day)
min/max/avg/stddev: 13 / 24 / 18.50 / 5.50
response_time: 3.123 (0.01/day)
min/max/avg/stddev: 0 / 4 / 2.12 / 1.54
Crawling Info
First contact: 2023-08-15 (10.6 months ago)
Last successful contact: 2024-07-01 (14.8 minutes ago)
Contact: 10116 successful, 449 failed.
Average fetch time: 2.12s
Next attempt scheduled for 10.3 seconds from now.
Found through mastodon-japan.net (up)
IP address: 139.99.39.10 (and 199 others, including: beyonoyasashiisekai.hostdon.ne.jp (up), iyasaretai.pw (up), puzzl.hostdon.ne.jp (up), m.legrand.im (down), hirasakain.fedicity.net (up), msoc.hostdon.ne.jp (down), mst.csoundc.info (up), su.kurotanesou.online (down), backhwa.fedicity.net (down), matsudon.hostdon.ne.jp (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 11:43:31 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 10:54:21 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 09:49:44 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 09:33:46 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 08:38:06 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 06:35:45 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 04:57:21 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 04:09:08 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 03:53:23 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- [2024-07-01 02:48:34 in 0.00s]: IP: 139.99.39.10 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 12:32:28 in 0.37s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 12:16:04 in 0.22s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 11:59:21 in 0.28s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 11:26:46 in 0.28s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 11:10:43 in 0.22s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 10:38:49 in 0.21s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 10:21:54 in 0.87s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 10:05:51 in 0.19s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 09:14:47 in 0.36s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 08:55:32 in 0.80s]: IP: 139.99.39.10 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 11:26:46 in 0.26s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 01:57:35 in 0.21s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-06-30 16:17:30 in 0.26s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-06-30 07:04:22 in 0.79s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-06-29 05:08:25 in 0.54s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-06-28 17:31:31 in 0.73s]: IP: 139.99.39.10 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 12:32:28 in 1.43s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 12:16:04 in 0.86s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 11:59:20 in 1.31s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 11:26:46 in 1.15s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 11:10:43 in 0.91s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 10:38:49 in 0.78s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 10:21:54 in 4.78s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 10:05:50 in 1.04s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 09:14:47 in 2.41s]: IP: 139.99.39.10 / OK / HTTP status: 200
- [2024-07-01 08:55:32 in 3.42s]: IP: 139.99.39.10 / OK / HTTP status: 200