social.iwanthorror.com — Mastodon
Details
up since 2023-12-20 12:48 (4.9 months ago)
- Uptime: 100.00%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 273
- Posts per user: 273.00
- Peers: 15
- Version: mastodon 4.2.8
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-05-05 14:39 — 2024-05-18 14:19
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯posts: 273 (3.77/day)
min/max/avg/stddev: 224 / 273 / 251.46 / 15.30
peers: 15 (0.08/day)
min/max/avg/stddev: 14 / 15 / 14.38 / 0.49
response_time: 6.923 (0.25/day)
min/max/avg/stddev: 3 / 33 / 11.30 / 8.85
Crawling Info
First contact: 2023-12-20 (4.9 months ago)
Last successful contact: 2024-05-18 (20.7 minutes ago)
Contact: 4605 successful, 233 failed.
Average fetch time: 11.30s
Next attempt scheduled for 21.1 minutes from now.
Found through social.ruth.run (up)
IP address: 54.38.247.97 (and 929 others, including: sitc.masto.host (down), mastodon.sawdustistan.org (up), i.phill.gg (down), tl.timeattack.zone (down), mastodon.esmevane.com (up), mastodon.heiperlan.de (down), social.grotz.me (down), tavern.calebhearth.com (down), social.kistler.dev (down), social.meawchill.xyz (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-18 12:28:43 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-17 16:34:07 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-17 08:53:33 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 22:36:01 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 08:25:50 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 06:44:08 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 05:03:38 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 00:07:43 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-15 21:55:31 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-15 19:43:09 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-18 14:19:25 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 13:24:31 in 0.75s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 11:41:10 in 0.93s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 10:50:05 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 09:59:17 in 0.51s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 09:15:17 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 07:20:31 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 06:43:18 in 0.67s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 06:05:37 in 0.57s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 05:28:41 in 0.36s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-18 02:26:04 in 0.16s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 13:56:01 in 0.16s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 16:57:51 in 1.87s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-15 15:33:08 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-18 14:19:25 in 1.69s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 13:24:31 in 6.33s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 11:41:10 in 5.92s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 10:50:05 in 1.30s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 09:59:17 in 6.20s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 09:15:17 in 1.42s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 08:34:49 in 2.06s]: IP: 54.38.247.97 / Error: unparseable / HTTP status: 200
- [2024-05-18 07:57:50 in 0.69s]: IP: 54.38.247.97 / Error: unparseable / HTTP status: 200
- [2024-05-18 07:20:31 in 3.03s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-18 06:43:18 in 5.35s]: IP: 54.38.247.97 / OK / HTTP status: 200