gettoyapping.phite.ro — GetToYapping
We're using an e-waste, on-premises, efficient server which runs on solar power during the day. That said, we have uptime monitoring systems and backups in place to compete with larger instances in robustness. Feel right at home :)
Bot owners (the first sentence applies to humans as well):
You are welcome to migrate here! Don't forget to adjust your privacy settings after registering, and see here for API authentication info. In the signup reason, include:
- what your bot does,
- where it's migrating from (if applicable),
- who owns it.
Moreover, both humans and bots must include a word that can be found in the rules in the signup request. SMTP is not set up, so you won't receive a confirmation email after registering. We'll confirm it for you.
Not affiliated with botsin.space in any way; bandwidth, domain and reverse proxy generously provided by @alex
Details
up since 2024-12-02 15:00 (83.6 days ago)
- Uptime: 99.32%
- Users: 3
- Posts: 520
- Posts per user: 173.33
- Peers: 4671
- Version: gotosocial 0.18.0+git-c9de6c9
- Source code: https://github.com/superseriousbusiness/gotosocial
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2025-02-22 17:48 — 2025-02-24 03:28
users: 3 (0.00/day)
min/max/avg/stddev: 3 / 3 / 3.00 / 0.00
⋯ ⋯posts: 520 (4.74/day)
min/max/avg/stddev: 514 / 520 / 517.50 / 1.89
peers: 4671 (6.32/day)
min/max/avg/stddev: 4663 / 4671 / 4667.67 / 2.69
response_time: 5.516 (1.29/day)
min/max/avg/stddev: 2 / 42 / 10.54 / 14.35
Crawling Info
First contact: 2024-11-16 (3.3 months ago)
Last successful contact: 2025-02-24 (63.5 minutes ago)
Contact: 1624 successful, 544 failed.
Average fetch time: 10.54s
Next attempt scheduled for 9.9 minutes ago.
Found through social.translunar.academy (up)
IP address: 86.124.65.187 (and 5 others: phite.ro (down), woe.ivy.my.id (down), isnet.phite.ro (up), shonk.phite.ro (down), is.phite.ro (up))
Responses
- /api/v1/instance ₍⇗₎
- [2025-02-24 03:28:35 in 0.64s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-24 00:11:56 in 0.25s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 21:28:44 in 0.48s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 18:57:47 in 0.40s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 16:16:08 in 0.35s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 13:39:58 in 0.27s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 11:02:09 in 0.28s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 08:16:04 in 0.25s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-22 17:48:07 in 0.32s]: IP: 86.124.65.187 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-23 21:28:44 in 0.41s]: IP: 86.124.65.187 / Error: http / HTTP status: 401
- [2025-02-23 08:16:04 in 0.25s]: IP: 86.124.65.187 / Error: http / HTTP status: 401
- /nodeinfo/2.1 ₍⇗₎
- [2025-02-24 03:28:35 in 1.91s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-24 00:11:56 in 1.05s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 21:28:44 in 22.58s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 18:57:47 in 2.12s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 16:16:08 in 2.21s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 13:39:58 in 1.12s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 11:02:09 in 1.09s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-23 08:16:04 in 1.03s]: IP: 86.124.65.187 / OK / HTTP status: 200
- [2025-02-22 17:48:07 in 1.43s]: IP: 86.124.65.187 / OK / HTTP status: 200