mi.tebukuro.xyz — Facebook3
Details
up since 2024-07-05 03:47 (20.3 hours ago)
- Uptime: 99.57%
- Users: 22
- Posts: 4282
- Posts per user: 194.64
- Peers: 352
- Version: misskey 2023.12.2
- Source code: https://github.com/misskey-dev/misskey
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-22 04:10 — 2024-07-06 00:05
users: 22 (0.07/day)
min/max/avg/stddev: 21 / 22 / 21.37 / 0.48
posts: 4282 (1.71/day)
min/max/avg/stddev: 4258 / 4282 / 4268.65 / 6.65
peers: 352 (0.14/day)
min/max/avg/stddev: 350 / 352 / 351.06 / 1.00
response_time: 1.002 (-0.20/day)
min/max/avg/stddev: 0 / 10 / 2.05 / 1.68
Crawling Info
First contact: 2023-01-25 (17.3 months ago)
Last successful contact: 2024-07-05 (48.3 minutes ago)
Latest attempt: 2024-07-06 (20.7 seconds ago)
Contact: 9202 successful, 6649 failed.
Average fetch time: 2.06s
Next attempt scheduled for 14.7 minutes from now.
Found through p1.a9z.dev (up)
IP address: 172.67.136.68 (and tebukuro.xyz.)
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-06 00:05:17 in 0.00s]: IP: 172.67.136.68 / Error: http / HTTP status: -1
- [2024-07-05 23:49:06 in 1.00s]: IP: 172.67.136.68 / Error: http / HTTP status: 403
- [2024-07-05 23:33:13 in 1.00s]: IP: 172.67.136.68 / Error: http / HTTP status: 403
- [2024-07-05 23:01:21 in 0.85s]: IP: 104.21.26.127 / Error: http / HTTP status: 403
- [2024-07-05 22:13:03 in 0.00s]: IP: 104.21.26.127 / Error: http / HTTP status: -1
- [2024-07-05 21:57:12 in 1.16s]: IP: 104.21.26.127 / Error: http / HTTP status: 403
- [2024-07-05 21:41:10 in 0.81s]: IP: 172.67.136.68 / Error: http / HTTP status: 403
- [2024-07-05 21:09:26 in 0.73s]: IP: 104.21.26.127 / Error: http / HTTP status: 403
- [2024-07-05 20:53:33 in 0.00s]: IP: 104.21.26.127 / Error: http / HTTP status: -1
- [2024-07-05 19:17:01 in 0.00s]: IP: 172.67.136.68 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 19:33:17 in 0.18s]: IP: 172.67.136.68 / Error: http / HTTP status: 404
- [2024-07-05 11:13:28 in 0.16s]: IP: 104.21.26.127 / Error: http / HTTP status: 404
- [2024-07-05 10:57:20 in 0.13s]: IP: 104.21.26.127 / Error: http / HTTP status: 404
- [2024-07-05 10:41:22 in 0.14s]: IP: 104.21.26.127 / Error: http / HTTP status: 404
- [2024-07-05 09:53:35 in 0.13s]: IP: 172.67.136.68 / Error: http / HTTP status: 404
- [2024-07-05 04:34:24 in 0.16s]: IP: 104.21.26.127 / Error: http / HTTP status: 404
- [2024-07-04 21:23:37 in 0.16s]: IP: 104.21.26.127 / Error: http / HTTP status: 404
- [2024-07-04 17:56:35 in 0.16s]: IP: 104.21.26.127 / Error: http / HTTP status: 404
- [2024-07-04 13:06:32 in 0.13s]: IP: 172.67.136.68 / Error: http / HTTP status: 404
- [2024-07-04 02:53:39 in 0.16s]: IP: 172.67.136.68 / Error: http / HTTP status: 404
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 18:11:50 in 0.20s]: IP: 172.67.136.68 / OK / HTTP status: 200
- [2024-07-05 08:33:31 in 0.18s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-04 23:31:13 in 0.20s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-04 10:09:27 in 0.17s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-03 23:38:40 in 0.17s]: IP: 172.67.136.68 / OK / HTTP status: 200
- [2024-07-03 14:59:51 in 0.17s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-03 06:43:54 in 0.18s]: IP: 172.67.136.68 / OK / HTTP status: 200
- /nodeinfo/2.1 ₍⇗₎
- [2024-07-05 23:17:19 in 0.64s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-05 22:45:19 in 0.66s]: IP: 172.67.136.68 / OK / HTTP status: 200
- [2024-07-05 22:29:24 in 0.67s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-05 21:25:19 in 0.67s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-05 20:37:17 in 0.72s]: IP: 172.67.136.68 / OK / HTTP status: 200
- [2024-07-05 20:21:14 in 0.64s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-05 20:05:26 in 0.70s]: IP: 172.67.136.68 / OK / HTTP status: 200
- [2024-07-05 19:49:38 in 0.68s]: IP: 104.21.26.127 / OK / HTTP status: 200
- [2024-07-05 19:33:17 in 0.73s]: IP: 172.67.136.68 / OK / HTTP status: 200
- [2024-07-05 19:01:02 in 0.60s]: IP: 172.67.136.68 / OK / HTTP status: 200