mastodon.calciumsigma.com — Calciumsigma's Mastodon Server
Details
up since 2024-11-26 03:36 (89.3 days ago)
- Uptime: 89.63%
- Users: 11 (0 active this month, 1 active last six months)
- Posts: 55
- Posts per user: 5.00
- Peers: 166512
- Version: mastodon 4.0.6
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 16:42 — 2025-02-23 10:38
users: 11 (0.00/day)
min/max/avg/stddev: 11 / 11 / 11.00 / 0.00
⋯ —posts: 55 (0.00/day)
min/max/avg/stddev: 55 / 55 / 55.00 / 0.00
⋯ —peers: 166512 (18.74/day)
min/max/avg/stddev: 166498 / 166512 / 166506.67 / 6.18
response_time: 1.186 (-2.14/day)
min/max/avg/stddev: 1 / 2 / 2.15 / 0.69
Crawling Info
First contact: 2022-12-21 (26.1 months ago)
Last successful contact: 2025-02-23 (53.7 minutes ago)
Contact: 33730 successful, 3026 failed.
Average fetch time: 2.15s
Next attempt scheduled for 37.9 minutes ago.
Found through kazv.moe (up)
IP address: 20.127.227.42 (and movie.calciumsigma.com.)
Staff
johndavis@mastodon.calciumsigma.com
I run the instance mastodon.calciumsigma.com, as well as a bunch of other stuff.
Responses
- /api/v1/instance ₍⇗₎
- [2025-02-23 10:38:32 in 0.11s]: IP: 20.127.227.42 / OK / HTTP status: 200
- [2025-02-23 07:53:15 in 0.18s]: IP: 20.127.227.42 / OK / HTTP status: 200
- [2025-02-22 16:42:36 in 0.50s]: IP: 20.127.227.42 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-23 07:53:15 in 0.13s]: IP: 20.127.227.42 / Error: unparseable / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-02-23 10:38:32 in 0.40s]: IP: 20.127.227.42 / OK / HTTP status: 200
- [2025-02-23 07:53:15 in 0.88s]: IP: 20.127.227.42 / OK / HTTP status: 200
- [2025-02-22 16:42:36 in 1.75s]: IP: 20.127.227.42 / OK / HTTP status: 200
Federation Info
Peers: 166512