mobilizon.aquilenet.fr
Intance Mobilizon d'Aquilenet, fournisseur d'accès Internet associatif, membre fondateur de la FFDN.
Aquilenet est basé à Bordeaux. Rencontre tous les mardi soirs 20 rue Tourat à Bordeaux
Details
up since 2024-06-09 18:02 (3.8 months ago)
- Uptime: 99.62%
- Users: 34
- Posts: 26
- Posts per user: 0.76
- Peers: 0
- Version: Mobilizon 3.0.4
- Source code: https://framagit.org/framasoft/mobilizon
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2021-02-06 (3.7 years ago)
Last successful contact: 2024-10-04 (13.2 minutes ago)
Contact: 18553 successful, 12252 failed.
Average fetch time: 2.78s
Next attempt scheduled for 4.2 minutes from now.
Found through hostux.social (up)
IP address: 185.233.103.18
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-10-04 16:46:36 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 16:30:44 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 14:27:59 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 14:12:28 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 13:55:46 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 10:47:08 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 09:46:17 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 09:14:46 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 08:59:05 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- [2024-10-04 08:11:44 in 0.00s]: IP: 185.233.103.18 / Error: http / HTTP status: -1
- /.well-known/nodeinfo/2.1 ₍⇗₎
- [2024-10-04 21:25:03 in 0.84s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 21:02:01 in 1.40s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 20:38:48 in 1.35s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 20:13:34 in 1.84s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 19:48:45 in 1.85s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 19:28:39 in 1.30s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 19:08:14 in 1.06s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 18:44:23 in 2.01s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 18:23:11 in 1.23s]: IP: 185.233.103.18 / OK / HTTP status: 200
- [2024-10-04 18:03:24 in 0.86s]: IP: 185.233.103.18 / OK / HTTP status: 200
- /api/v1/instance ₍⇗₎
- [2024-10-04 19:48:45 in 0.16s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-04 02:18:54 in 0.43s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-03 05:45:58 in 0.18s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-02 21:45:32 in 0.16s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-02 09:57:24 in 0.30s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-02 02:15:57 in 0.16s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-02 01:30:03 in 0.16s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-02 00:00:46 in 0.56s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-01 21:52:58 in 0.15s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- /api/v1/instance/peers ₍⇗₎
- [2024-10-04 18:23:11 in 0.15s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-04 10:02:09 in 0.25s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-03 23:49:55 in 0.15s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-03 15:41:40 in 0.16s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-03 03:23:33 in 0.16s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-02 16:45:30 in 0.16s]: IP: 185.233.103.18 / Error: http / HTTP status: 400
- [2024-10-02 07:01:39 in 0.60s]: IP: 185.233.103.18 / Error: http / HTTP status: 400