rpvortex.online — RP Vortex (II)
Details
up since 2024-12-01 20:14 (84.0 days ago)
- Uptime: 93.64%
- Users: 493 (431 active this month, 477 active last six months)
- Posts: 23857
- Posts per user: 48.39
- Peers: 3838
- Version: mastodon 4.3.3
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 15:58 — 2025-02-23 18:35
users: 493 (0.00/day)
min/max/avg/stddev: 493 / 493 / 493.00 / 0.00
⋯ —posts: 23857 (15.06/day)
min/max/avg/stddev: 23842 / 23857 / 23850.00 / 6.16
peers: 3838 (1.00/day)
min/max/avg/stddev: 3837 / 3838 / 3837.67 / 0.47
response_time: 4.161 (-0.28/day)
min/max/avg/stddev: 1 / 4 / 3.40 / 1.28
Crawling Info
First contact: 2021-02-06 (4.0 years ago)
Last successful contact: 2025-02-23 (72.7 minutes ago)
Contact: 104510 successful, 11985 failed.
Average fetch time: 3.40s
Next attempt scheduled for 46.0 minutes ago.
Found through freespeechextremist.com (down)
IP address: 178.33.220.142 (and 320 others, including: relay.plush.city (down), artisan.chat (down), fietser.social (up), sigmoid.social (up), mapstodon.space (up), bbq.golf (up), hackdezorg.nl (down), femme.energy (down), benhutchings.com (down), sciencemastodon.com (up))
Staff

Still figuring this out. Standby…
Admin for the RP Vortex instance. Any questions, I’m here 😉👍

In the beginning, there was the idea. It was abused. Get off my lawn.
(administrator of RPVortex.online)
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-02-23 13:19:08 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-02-23 18:35:01 in 0.19s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 15:52:54 in 0.50s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 10:38:13 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 07:45:51 in 0.23s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-22 15:58:42 in 0.35s]: IP: 176.31.213.231 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-23 18:35:01 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-02-23 18:35:01 in 1.03s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-23 15:52:54 in 2.24s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 10:38:13 in 0.98s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2025-02-23 07:45:51 in 1.90s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2025-02-22 15:58:41 in 2.43s]: IP: 176.31.213.231 / OK / HTTP status: 200