mobilizon.bstly.de — Mobilizon
Mobilizon instance of Bastelei e. V.
Details
up since 2024-09-24 10:49 (41.5 days ago)
- Uptime: 99.02%
- Users: 4
- Posts: 0
- Posts per user: 0.00
- Peers: 0
- Version: Mobilizon 4.0.0
- Source code: https://framagit.org/framasoft/mobilizon
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2022-05-13 (29.8 months ago)
Last successful contact: 2024-11-04 (151.0 seconds ago)
Contact: 16204 successful, 8312 failed.
Average fetch time: 2.76s
Next attempt scheduled for 14.7 minutes from now.
Found through mastodon.oi7.de (down)
IP address: 202.61.247.32 (and 4 others: nc.bstly.de (down), mastodon.bstly.de (up), pod.bstly.de (up), tube.bstly.de (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-04 21:15:41 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 20:09:26 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 14:43:28 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 13:32:53 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 13:16:47 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 13:00:39 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 12:28:23 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 08:59:14 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 08:10:52 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- [2024-11-04 07:54:57 in 0.00s]: IP: 202.61.247.32 / Error: http / HTTP status: -1
- /.well-known/nodeinfo/2.1 ₍⇗₎
- [2024-11-04 22:05:20 in 1.20s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 21:48:04 in 1.17s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 21:31:33 in 1.18s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 20:58:53 in 1.21s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 20:43:03 in 0.64s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 20:26:48 in 1.44s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 19:43:43 in 1.16s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 19:14:13 in 3.19s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 18:51:55 in 2.13s]: IP: 202.61.247.32 / OK / HTTP status: 200
- [2024-11-04 18:35:05 in 0.96s]: IP: 202.61.247.32 / OK / HTTP status: 200
- /api/v1/instance ₍⇗₎
- [2024-11-04 21:31:33 in 0.17s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-04 20:43:03 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-04 11:46:46 in 0.39s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-04 09:15:25 in 0.32s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-04 05:05:54 in 0.18s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-03 15:34:20 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-03 01:14:54 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-02 18:24:00 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-02 14:51:21 in 0.42s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-02 14:05:49 in 0.17s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- /api/v1/instance/peers ₍⇗₎
- [2024-11-04 21:31:33 in 0.17s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-04 12:09:42 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-04 02:47:22 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-03 17:59:26 in 0.17s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-03 09:44:22 in 0.36s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-03 00:42:35 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-02 16:27:22 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400
- [2024-11-02 05:36:17 in 0.16s]: IP: 202.61.247.32 / Error: http / HTTP status: 400