crowleyclub.com — The Crowley Club
Details
up since 2023-08-27 09:25 (8.7 months ago)
- Uptime: 99.85%
- Users: 2 (1 active this month, 1 active last six months)
- Posts: 1335
- Posts per user: 667.50
- Peers: 10296
- Version: mastodon 4.2.8
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-05-05 13:24 — 2024-05-18 17:48
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 1335 (1.15/day)
min/max/avg/stddev: 1319 / 1335 / 1326.70 / 4.88
peers: 10296 (3.02/day)
min/max/avg/stddev: 10254 / 10298 / 10269.54 / 14.00
response_time: 3.423 (-0.53/day)
min/max/avg/stddev: 1 / 46 / 7.47 / 7.27
Crawling Info
First contact: 2022-05-19 (24.0 months ago)
Last successful contact: 2024-05-18 (16.0 minutes ago)
Contact: 39691 successful, 4420 failed.
Average fetch time: 7.47s
Next attempt scheduled for 17.2 minutes from now.
Found through charlestown.social (down)
IP address: 176.31.213.231 (and 153 others, including: chicken.rodeo (down), swingset.social (up), relay.plush.city (down), nologo.social (up), machikadon.online (up), witchy.space (down), laserdisc.party (up), grand-duchy.net (up), social.crockett.network (down), gielen.dk (down))
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-18 12:25:47 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-05-18 02:29:19 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-05-17 22:25:32 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-05-17 18:50:10 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-05-17 18:15:20 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-05-17 16:35:53 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-05-17 16:04:18 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-05-16 19:08:58 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-05-16 13:24:37 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-05-16 09:02:57 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-18 17:48:51 in 0.20s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 17:12:08 in 0.19s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 16:36:51 in 0.21s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 15:58:44 in 0.20s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 15:21:10 in 0.22s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 14:42:55 in 0.20s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 14:00:22 in 1.18s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 13:14:43 in 0.21s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 11:45:15 in 0.39s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 11:05:13 in 1.14s]: IP: 176.31.213.231 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-18 15:21:10 in 0.17s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 06:06:39 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-17 19:54:55 in 0.17s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-17 04:18:15 in 0.17s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-16 14:12:23 in 3.34s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-15 23:55:34 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-18 17:48:51 in 1.34s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 17:12:08 in 1.38s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 16:36:51 in 1.32s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 15:58:44 in 1.37s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 15:21:10 in 1.30s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 14:42:55 in 1.39s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 14:00:22 in 16.72s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-05-18 13:14:43 in 1.32s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 11:45:15 in 7.46s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-05-18 11:05:13 in 13.77s]: IP: 176.31.213.231 / OK / HTTP status: 200