taidum.social — TeamTaidum Mastodon Server
Mastodon instance for any and all Taidums! Proceed with caution: furry and banana bread-related content inside.
Details
up since 2024-04-15 18:47 (17.1 days ago)
- Uptime: 98.99%
- Users: 23 (6 active this month, 16 active last six months)
- Posts: 81
- Posts per user: 3.52
- Peers: 10830
- Version: mastodon 4.3.0-alpha.1+glitch
- Registrations: Open
Stats 2024-04-18 22:30 — 2024-05-02 20:27
users: 23 (0.00/day)
min/max/avg/stddev: 23 / 23 / 23.00 / 0.00
⋯ ⋯posts: 81 (0.15/day)
min/max/avg/stddev: 79 / 81 / 79.24 / 0.59
peers: 10830 (5.68/day)
min/max/avg/stddev: 10752 / 10830 / 10787.48 / 23.16
response_time: 8.975 (0.50/day)
min/max/avg/stddev: 0 / 50 / 11.20 / 11.08
Crawling Info
First contact: 2023-08-14 (8.6 months ago)
Last successful contact: 2024-05-02 (21.4 minutes ago)
Contact: 15110 successful, 4065 failed.
Average fetch time: 11.32s
Next attempt scheduled for 15.2 minutes from now.
Found through thegoatery.dyndns.org (up)
IP address: 104.21.94.152
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-02 18:37:12 in 1.71s]: IP: 172.67.137.104 / Error: http / HTTP status: 403
- [2024-05-02 11:49:49 in 3.17s]: IP: 104.21.94.152 / Error: http / HTTP status: 403
- [2024-05-02 11:13:11 in 1.39s]: IP: 172.67.137.104 / Error: http / HTTP status: 403
- [2024-05-02 09:21:55 in 1.76s]: IP: 104.21.94.152 / Error: http / HTTP status: 403
- [2024-05-02 08:08:10 in 1.00s]: IP: 172.67.137.104 / Error: http / HTTP status: 403
- [2024-05-02 05:01:18 in 1.32s]: IP: 104.21.94.152 / Error: http / HTTP status: 403
- [2024-05-02 04:24:28 in 1.60s]: IP: 172.67.137.104 / Error: http / HTTP status: 403
- [2024-05-02 02:33:52 in 2.40s]: IP: 104.21.94.152 / Error: http / HTTP status: 403
- [2024-05-02 01:19:41 in 1.31s]: IP: 104.21.94.152 / Error: http / HTTP status: 403
- [2024-05-02 00:42:11 in 3.36s]: IP: 172.67.137.104 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-05-02 20:27:35 in 0.49s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 19:50:43 in 0.14s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 19:13:57 in 0.23s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 18:00:09 in 0.13s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 17:22:49 in 0.10s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 16:45:59 in 0.13s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 15:31:12 in 0.12s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 14:54:08 in 0.13s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 14:16:55 in 0.10s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 13:40:00 in 0.14s]: IP: 172.67.137.104 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-02 19:13:57 in 0.12s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-01 12:34:32 in 0.17s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-01 02:24:57 in 0.12s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-04-30 16:42:17 in 0.42s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-04-30 07:54:49 in 0.12s]: IP: 104.21.94.152 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-02 20:27:35 in 0.55s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 19:50:43 in 0.46s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 19:13:57 in 0.42s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 18:00:09 in 0.55s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 17:22:49 in 0.47s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 16:45:59 in 0.47s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 15:31:12 in 0.39s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 14:54:08 in 0.61s]: IP: 172.67.137.104 / OK / HTTP status: 200
- [2024-05-02 14:16:55 in 0.42s]: IP: 104.21.94.152 / OK / HTTP status: 200
- [2024-05-02 13:40:00 in 0.35s]: IP: 172.67.137.104 / OK / HTTP status: 200