hubzil.la — Yet another instance
Details
up since 2024-06-28 02:54 (7.8 days ago)
- Uptime: 99.63%
- Users: 0
- Posts: 0
- Peers: 0
- Version: friendica 2024.03-1557
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-22 16:32 — 2024-07-05 23:00
peers: 0 (0.00/day)
min/max/avg/stddev: 0 / 4899 / 2294.71 / 2433.93
response_time: 4.254 (-0.57/day)
min/max/avg/stddev: 2 / 112 / 33.51 / 31.72
Crawling Info
First contact: 2021-10-21 (32.5 months ago)
Last successful contact: 2024-07-05 (5.3 minutes ago)
Contact: 6301 successful, 1488 failed.
Average fetch time: 33.51s
Next attempt scheduled for 47.9 minutes from now.
Found through fediver.se (nxdomain)
IP address: 77.37.174.66 (and bot.fediver.se.)
Staff
Такой, мужчина с бородой
Резидент Бирюлёво
IT-гедонист
Что-то упустили, наверстаем потом
Там, где не пройти - пролетим орлом
На пенсии меня будут звать - Старик Похабыч
Email: andrey@esin.email (Key ID: 64c6a73345ccc419)
Github: https://github.com/esin
Админ fediver.se и hubzil.la
tfr
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 18:26:44 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 17:28:59 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 14:39:34 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 13:42:45 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 10:08:21 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 07:25:32 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 06:30:34 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 04:39:33 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 01:54:22 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- [2024-07-05 00:58:22 in 0.00s]: IP: 77.37.174.66 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 23:00:58 in 0.30s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 22:06:41 in 0.30s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 21:12:05 in 0.29s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 20:18:07 in 0.29s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 19:24:09 in 0.29s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 16:33:59 in 0.24s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 15:37:36 in 0.30s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 12:48:44 in 0.28s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 11:55:45 in 0.29s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 11:02:22 in 0.30s]: IP: 77.37.174.66 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-04 16:46:42 in 0.32s]: IP: 77.37.174.66 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-05 23:00:58 in 1.28s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 22:06:41 in 1.26s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 21:12:05 in 1.08s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 20:18:07 in 1.08s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 19:24:09 in 1.07s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 16:33:59 in 1.03s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 15:37:36 in 1.61s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 12:48:44 in 1.08s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 11:55:45 in 1.03s]: IP: 77.37.174.66 / OK / HTTP status: 200
- [2024-07-05 11:02:22 in 1.28s]: IP: 77.37.174.66 / OK / HTTP status: 200
Federation Info
Peers: 0