social.afront.org — A Social Front Organization
Details
up since 2023-11-08 17:27 (7.7 months ago)
- Uptime: 99.39%
- Users: 42 (23 active this month, 29 active last six months)
- Posts: 31395
- Posts per user: 747.50
- Peers: 21192
- Version: mastodon 4.3.0-alpha.4+glitch
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 10:45 — 2024-07-01 10:42
users: 42 (0.01/day)
min/max/avg/stddev: 39 / 42 / 41.99 / 0.19
posts: 31395 (47.75/day)
min/max/avg/stddev: 17876 / 31395 / 30951.91 / 876.85
peers: 21192 (14.72/day)
min/max/avg/stddev: 17023 / 21193 / 21063.29 / 327.00
response_time: 1.061 (-0.01/day)
min/max/avg/stddev: 0 / 80 / 15.08 / 17.85
Crawling Info
First contact: 2021-11-06 (31.8 months ago)
Last successful contact: 2024-07-01 (34.9 seconds ago)
Contact: 35461 successful, 16441 failed.
Average fetch time: 15.08s
Next attempt scheduled for 40.0 minutes from now.
Found through social.cool110.xyz (up)
IP address: 23.128.96.11 (and social.python-gsoc.org.)
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 06:12:47 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-07-01 03:22:43 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-07-01 01:16:08 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-30 17:55:57 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-30 12:53:52 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 23:43:23 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 17:13:07 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 15:43:03 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 11:49:38 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 09:40:59 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 10:42:50 in 0.23s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 08:25:35 in 0.19s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 05:29:51 in 0.21s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 04:47:56 in 0.22s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 04:05:23 in 2.25s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 02:40:24 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-07-01 01:57:53 in 0.18s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 00:34:47 in 0.15s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-30 23:51:46 in 22.51s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-30 23:06:30 in 0.14s]: IP: 23.128.96.11 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 09:13:39 in 0.25s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-30 17:13:04 in 2.88s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-29 18:38:22 in 0.24s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-28 23:47:23 in 3.09s]: IP: 23.128.96.11 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 10:42:50 in 0.55s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 10:00:03 in 0.43s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 09:13:39 in 0.59s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 08:25:35 in 0.30s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 07:39:28 in 0.31s]: IP: 23.128.96.11 / Error: unparseable / HTTP status: 200
- [2024-07-01 06:56:08 in 14.32s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 05:29:51 in 0.27s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 04:47:56 in 0.63s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 04:05:23 in 17.34s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 02:40:24 in 18.90s]: IP: 23.128.96.11 / OK / HTTP status: 200