social.zedpro.me — Mastodon
In this day and age is it important for everyone to host a decentralised social network instance, so this is mine. Just another ZedPro Mastodon server!
Details
up since 2023-08-27 08:48 (10.2 months ago)
- Uptime: 99.55%
- Users: 1 (0 active this month, 13 active last six months)
- Posts: -33
- Posts per user: -33.00
- Peers: 904
- Version: mastodon 4.0.2
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-24 13:21 — 2024-07-01 12:35
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: -33 (-0.12/day)
min/max/avg/stddev: -33 / 1 / -27.33 / 12.67
peers: 904 (1.12/day)
min/max/avg/stddev: 586 / 904 / 849.50 / 117.85
response_time: 3.678 (0.01/day)
min/max/avg/stddev: 0 / 39 / 9.96 / 13.25
Crawling Info
First contact: 2021-07-06 (35.8 months ago)
Last successful contact: 2024-07-01 (22.6 minutes ago)
Contact: 53704 successful, 16232 failed.
Average fetch time: 9.96s
Next attempt scheduled for 11.9 minutes from now.
Found through blob.cat (up)
IP address: 168.138.187.73
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 09:00:21 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-07-01 05:51:34 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-07-01 02:19:54 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-06-30 23:58:26 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-06-30 22:04:19 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-06-30 21:28:02 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-06-30 18:52:46 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-06-30 14:51:10 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-06-30 13:33:58 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- [2024-06-30 04:15:58 in 0.00s]: IP: 168.138.187.73 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 12:35:07 in 0.20s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 11:59:21 in 0.22s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 11:24:07 in 0.90s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 10:49:36 in 0.22s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 10:14:46 in 0.19s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 09:38:18 in 0.57s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 08:19:25 in 0.90s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 07:39:45 in 0.46s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 07:03:03 in 0.21s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 06:26:51 in 0.21s]: IP: 168.138.187.73 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 06:26:51 in 0.20s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-06-30 19:32:57 in 1.01s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-06-30 05:34:02 in 0.19s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-06-29 02:45:28 in 0.20s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-06-28 13:44:00 in 0.19s]: IP: 168.138.187.73 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 12:35:07 in 0.71s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 11:59:21 in 1.26s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 11:24:07 in 3.48s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 10:49:36 in 1.29s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 10:14:46 in 0.94s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 09:38:18 in 4.04s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 08:19:25 in 3.58s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 07:39:45 in 3.86s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 07:03:03 in 0.81s]: IP: 168.138.187.73 / OK / HTTP status: 200
- [2024-07-01 06:26:51 in 1.32s]: IP: 168.138.187.73 / OK / HTTP status: 200