thevipvipers.space — The VIP Vipers
Details
up since 2024-06-09 20:18 (26.0 days ago)
- Uptime: 99.81%
- Users: 19 (7 active this month, 16 active last six months)
- Posts: 9021
- Posts per user: 474.79
- Peers: 15446
- Version: mastodon 4.2.10
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-22 04:12 — 2024-07-05 20:14
users: 19 (0.00/day)
min/max/avg/stddev: 19 / 19 / 19.00 / 0.00
⋯ ⋯posts: 9021 (2.83/day)
min/max/avg/stddev: 8206 / 9021 / 8973.05 / 144.64
peers: 15446 (12.01/day)
min/max/avg/stddev: 11991 / 15446 / 15308.51 / 623.95
response_time: 2.331 (0.01/day)
min/max/avg/stddev: 0 / 35 / 4.15 / 4.31
Crawling Info
First contact: 2022-04-26 (26.3 months ago)
Last successful contact: 2024-07-05 (37.7 minutes ago)
Latest attempt: 2024-07-05 (15.7 minutes ago)
Contact: 48276 successful, 5701 failed.
Average fetch time: 4.15s
Next attempt scheduled for 5.1 minutes from now.
Found through pleroma.soykaf.com (up)
IP address: 178.33.220.142 (and 377 others, including: www.masto.pt (down), qwerq33.social (down), hackdezorg.nl (down), professio.ifwo.eu (down), autonomous.zone (up), oour.org (up), femme.energy (down), claris.cf (up), benhutchings.com (down), pizzahut.systems (down))
Staff
![](https://cdn.masto.host/thevipvipersspace/accounts/avatars/108/195/238/166/083/721/original/192d39bf36f10229.png)
Host of #RSPickNMix on @RadioSEGA and @VipersVGMture on the KNGI Network. Also a (somewhat active) RadioSEGA Admin!
@Bisylizzie is pretty neat! ♥️ | he/him
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 20:14:08 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-05 17:40:40 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-05 13:20:04 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-05 12:37:04 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-05 10:05:41 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-05 05:44:57 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-05 05:22:56 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-04 22:51:09 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-04 15:03:10 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-04 14:40:07 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 19:52:04 in 0.42s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 19:30:19 in 0.18s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 18:47:24 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 18:25:21 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 18:02:13 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 17:18:52 in 0.26s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 16:57:00 in 0.61s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 16:14:20 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 15:52:15 in 0.30s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 15:31:05 in 0.39s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 07:53:51 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-04 23:34:50 in 0.31s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-04 13:54:36 in 0.18s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-04 05:12:09 in 0.60s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-03 20:51:04 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-03 12:07:42 in 0.25s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-03 02:48:31 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-05 19:52:04 in 2.39s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 19:30:19 in 0.94s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 19:08:41 in 0.81s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-07-05 18:47:24 in 0.98s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 18:25:21 in 1.07s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 18:02:13 in 1.25s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 17:18:52 in 1.24s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 16:57:00 in 3.39s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-05 16:35:51 in 0.78s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-07-05 16:14:20 in 1.22s]: IP: 178.33.220.142 / OK / HTTP status: 200