social.python-gsoc.org — Python GSoC Social
Details
up since 2024-06-10 00:59 (21.4 days ago)
- Uptime: 99.96%
- Users: 40 (33 active this month, 42 active last six months)
- Posts: 140
- Posts per user: 3.50
- Peers: 1303
- Version: mastodon 4.3.0-alpha.4+glitch
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 10:48 — 2024-07-01 10:21
users: 40 (0.00/day)
min/max/avg/stddev: 40 / 40 / 40.00 / 0.00
⋯ ⋯posts: 139 (3.46/day)
min/max/avg/stddev: 91 / 140 / 113.68 / 12.67
peers: 1303 (9.25/day)
min/max/avg/stddev: 493 / 1303 / 1218.67 / 136.51
response_time: 0.619 (-0.01/day)
min/max/avg/stddev: 0 / 91 / 19.37 / 21.93
Crawling Info
First contact: 2024-02-03 (4.9 months ago)
Last successful contact: 2024-07-01 (73.3 minutes ago)
Latest attempt: 2024-07-01 (25.4 minutes ago)
Contact: 4271 successful, 907 failed.
Average fetch time: 19.37s
Next attempt scheduled for 19.2 minutes from now.
Found through bitbang.social (up)
IP address: 23.128.96.11 (and social.afront.org.)
Staff
![](https://social.python-gsoc.org/system/accounts/avatars/111/859/896/694/300/322/original/50296214f3c3833a.jpg)
You should probably really follow me over on @warthog9
Python Software Foundation Fellow
Python GSoC org admin / infrastructure
I do not represent, or speak, for the PSF, or GSoC.
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 10:21:26 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-07-01 06:17:37 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-07-01 00:53:46 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-30 18:35:06 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-30 03:55:21 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-30 00:53:42 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 22:36:29 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 19:33:02 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 12:22:27 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-06-29 09:23:21 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 09:33:29 in 0.24s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 07:52:57 in 0.22s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 07:05:21 in 2.01s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 05:30:46 in 37.97s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 04:44:04 in 0.13s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 03:57:48 in 0.00s]: IP: 23.128.96.11 / Error: http / HTTP status: -1
- [2024-07-01 03:10:33 in 0.18s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 02:24:36 in 1.96s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 01:39:09 in 0.19s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 00:07:16 in 0.14s]: IP: 23.128.96.11 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 04:44:04 in 12.81s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-30 06:59:28 in 0.17s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-29 11:38:04 in 0.28s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-06-28 16:17:37 in 5.73s]: IP: 23.128.96.11 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 09:33:29 in 0.71s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 07:52:57 in 0.50s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 07:05:21 in 5.23s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 05:30:46 in 0.45s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 04:44:03 in 30.72s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 03:57:48 in 0.61s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 03:10:33 in 0.49s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 02:24:36 in 25.15s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 01:39:09 in 0.51s]: IP: 23.128.96.11 / OK / HTTP status: 200
- [2024-07-01 00:07:16 in 0.31s]: IP: 23.128.96.11 / OK / HTTP status: 200