social.fuzzyoverlords.org — FuzzyOverlords
Details
up since 2023-08-27 06:25 (10.2 months ago)
- Uptime: 99.85%
- Users: 4 (1 active this month, 2 active last six months)
- Posts: 1161
- Posts per user: 290.25
- Peers: 12003
- Version: mastodon 4.2.8
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 15:42 — 2024-07-01 11:04
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 1161 (0.27/day)
min/max/avg/stddev: 1084 / 1162 / 1155.35 / 19.65
peers: 12003 (7.37/day)
min/max/avg/stddev: 9913 / 12004 / 11826.82 / 525.56
response_time: 2.047 (-0.00/day)
min/max/avg/stddev: 0 / 17 / 3.49 / 3.37
Crawling Info
First contact: 2022-11-06 (19.8 months ago)
Last successful contact: 2024-07-01 (15.3 seconds ago)
Contact: 33290 successful, 753 failed.
Average fetch time: 3.49s
Next attempt scheduled for 18.1 minutes from now.
Found through social.tromdienste.de (up)
IP address: 149.255.39.199 (and fuzzyoverlords.org.)
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 09:02:27 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-07-01 04:35:30 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-07-01 01:22:47 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-06-30 23:45:52 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-06-30 22:43:51 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-06-30 21:21:23 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-06-30 17:40:46 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-06-30 17:21:13 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-06-30 12:39:13 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- [2024-06-30 09:42:53 in 0.00s]: IP: 149.255.39.199 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 11:04:35 in 0.11s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 10:45:00 in 0.13s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 10:25:58 in 0.66s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 10:06:51 in 0.13s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 09:47:31 in 0.14s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 09:26:07 in 1.27s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 08:40:43 in 0.11s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 08:17:52 in 1.24s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 07:55:22 in 0.64s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 07:34:42 in 0.13s]: IP: 149.255.39.199 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 05:53:12 in 0.13s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-06-30 20:40:29 in 0.19s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-06-30 11:54:11 in 0.89s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-06-30 01:57:00 in 0.65s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-06-29 17:02:37 in 0.59s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-06-29 08:36:47 in 1.42s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-06-28 19:29:39 in 0.13s]: IP: 149.255.39.199 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 11:04:35 in 0.35s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 10:45:00 in 0.42s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 10:25:58 in 3.77s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 10:06:51 in 0.28s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 09:47:31 in 0.26s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 09:26:07 in 7.74s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 08:40:43 in 0.28s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 08:17:51 in 4.55s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 07:55:22 in 3.21s]: IP: 149.255.39.199 / OK / HTTP status: 200
- [2024-07-01 07:34:42 in 0.44s]: IP: 149.255.39.199 / OK / HTTP status: 200