social.sceneworld.org — Scene World Magazine
Details
up since 2023-08-27 04:55 (10.2 months ago)
- Uptime: 99.87%
- Users: 5 (3 active this month, 4 active last six months)
- Posts: 331
- Posts per user: 66.20
- Peers: 8774
- Version: mastodon 4.2.9
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-19 17:04 — 2024-07-03 14:15
users: 5 (0.00/day)
min/max/avg/stddev: 5 / 5 / 5.00 / 0.00
⋯ ⋯posts: 331 (0.36/day)
min/max/avg/stddev: 227 / 332 / 314.79 / 37.63
peers: 8774 (7.14/day)
min/max/avg/stddev: 6734 / 8775 / 8442.10 / 728.24
response_time: 3.177 (0.01/day)
min/max/avg/stddev: 0 / 33 / 4.72 / 5.79
Crawling Info
First contact: 2023-01-01 (18.0 months ago)
Last successful contact: 2024-07-03 (21.4 minutes ago)
Contact: 27277 successful, 1017 failed.
Average fetch time: 4.73s
Next attempt scheduled for 73.5 seconds from now.
Found through social.fedcast.ch (up)
IP address: 54.38.247.97 (and 931 others, including: omg.wtf.sh (up), tl.timeattack.zone (down), mastodon.heiperlan.de (down), social.grotz.me (down), social.kistler.dev (down), social.meawchill.xyz (down), social.cereza.de (down), social.b4tech.cc (up), social.postninja.net (down), cave.mvu.pl (down))
Staff
![](https://cdn.masto.host/socialsceneworldorg/accounts/avatars/109/613/869/376/956/147/original/85805669f4ca3c24.png)
I am organizer and founder of @sceneworld Magazine, a Blogger, a Podcast co-host http://linktr.ee/nafcom
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 07:39:42 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-03 04:52:29 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-03 04:05:07 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-02 23:22:16 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-02 15:36:58 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-01 20:20:41 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-01 14:25:43 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-01 09:58:26 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-01 05:44:13 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-07-01 03:45:09 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-03 14:15:26 in 0.20s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 13:51:53 in 0.32s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 13:27:58 in 0.28s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 13:03:39 in 0.50s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 12:40:30 in 0.42s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 12:17:50 in 0.20s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 11:54:44 in 0.55s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 11:08:10 in 0.54s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 10:22:10 in 0.65s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 09:36:53 in 0.36s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 12:17:50 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 00:09:25 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-02 16:00:31 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-02 02:58:35 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-01 14:51:40 in 0.52s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-01 04:32:12 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-06-30 18:06:01 in 0.19s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-03 14:15:26 in 1.20s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 13:51:53 in 1.78s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 13:27:58 in 1.50s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 13:03:39 in 6.48s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 12:40:30 in 2.62s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 12:17:50 in 1.26s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 11:54:44 in 2.47s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 11:31:29 in 1.02s]: IP: 54.38.247.97 / Error: unparseable / HTTP status: 200
- [2024-07-03 11:08:10 in 4.09s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-07-03 10:45:01 in 0.55s]: IP: 54.38.247.97 / Error: unparseable / HTTP status: 200