friendica.mbbit.de — Friendica Social Network
Details
up since 2024-07-03 13:04 (57.8 hours ago)
- Uptime: 87.37%
- Users: 0
- Posts: 0
- Peers: 0
- Version: friendica 2023.12-1542
- Registrations: Approval Required
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-21 23:12 — 2024-07-05 22:43
peers: 0 (0.00/day)
min/max/avg/stddev: 0 / 5456 / 2602.21 / 2711.46
response_time: 2.217 (0.01/day)
min/max/avg/stddev: 0 / 15 / 3.93 / 3.09
Crawling Info
First contact: 2022-11-02 (20.1 months ago)
Last successful contact: 2024-07-05 (8.1 minutes ago)
Contact: 27599 successful, 1694 failed.
Average fetch time: 3.93s
Next attempt scheduled for 11.7 minutes from now.
Found through sekretaerbaer.de (up)
IP address: 212.227.213.84 (and 2 others: events.mbbit.de (up), social.mbbit.de (up))
Staff
marek@friendica.mbbit.de
Promovierter Informatiker mit einer Leidenschaft für Nachtleben.
Derselbe wie der hier:
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-05 20:37:16 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-05 15:16:13 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-05 10:34:40 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-05 04:28:33 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-05 03:24:32 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-04 20:31:26 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-04 20:10:14 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-04 15:00:07 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-04 13:51:05 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-04 08:50:20 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-05 22:43:13 in 0.17s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 22:22:06 in 0.31s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 22:00:55 in 0.17s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 21:40:07 in 0.18s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 21:19:05 in 0.18s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 20:58:08 in 0.22s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 20:16:13 in 0.18s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 19:55:19 in 0.17s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 19:33:58 in 0.17s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 19:12:07 in 0.16s]: IP: 212.227.213.84 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-05 21:40:07 in 0.36s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 13:04:16 in 0.38s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 01:37:18 in 0.39s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-04 17:13:49 in 0.38s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-04 07:41:24 in 0.37s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 22:50:12 in 0.35s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 14:15:05 in 0.32s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 05:33:48 in 0.34s]: IP: 212.227.213.84 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-05 22:43:13 in 0.81s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 22:22:06 in 1.54s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 22:00:55 in 0.97s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 21:40:07 in 0.79s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 21:19:05 in 0.84s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 20:58:08 in 1.22s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 20:16:13 in 1.02s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 19:55:19 in 1.22s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 19:33:58 in 1.27s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-05 19:12:07 in 0.85s]: IP: 212.227.213.84 / OK / HTTP status: 200
Federation Info
Peers: 0