meet.vestfold.dev — Meet Vestfold dev
Meetings, hangouts, pub-crawls. discussions or revolution - plan it here!
Details
up since 2024-11-13 23:11 (26.9 hours ago)
- Uptime: 98.06%
- Users: 8
- Posts: 4
- Posts per user: 0.50
- Peers: 0
- Version: Mobilizon 4.1.0
- 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: 2024-08-21 (85.8 days ago)
Last successful contact: 2024-11-15 (14.6 minutes ago)
Contact: 5531 successful, 2299 failed.
Average fetch time: 3.17s
Next attempt scheduled for 5.2 minutes from now.
Found through chatfreu.de (up)
IP address: 116.202.11.35 (and 2 others: plud.re (up), lm.eke.li (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-11-15 00:22:05 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-15 00:06:35 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 23:43:51 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 23:28:02 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 21:46:27 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 21:30:40 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 20:26:50 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 18:40:52 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 17:36:53 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- [2024-11-14 15:08:16 in 0.00s]: IP: 116.202.11.35 / Error: http / HTTP status: -1
- /.well-known/nodeinfo/2.1 ₍⇗₎
- [2024-11-15 01:49:28 in 1.15s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-15 01:27:12 in 1.43s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-15 01:01:38 in 2.73s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-15 00:38:36 in 2.46s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-14 23:11:40 in 0.66s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-14 22:51:34 in 1.73s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-14 22:34:02 in 1.66s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-14 22:18:08 in 1.15s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-14 22:02:21 in 0.72s]: IP: 116.202.11.35 / OK / HTTP status: 200
- [2024-11-14 21:14:36 in 1.16s]: IP: 116.202.11.35 / OK / HTTP status: 200
- /api/v1/instance ₍⇗₎
- [2024-11-14 20:42:46 in 0.16s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-14 13:48:19 in 0.16s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-14 11:35:24 in 0.17s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-13 17:55:57 in 0.16s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-13 15:22:37 in 0.30s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-13 10:55:33 in 0.24s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-12 23:41:25 in 0.57s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-12 13:05:53 in 0.82s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-12 03:36:10 in 0.16s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-12 02:09:21 in 0.26s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- /api/v1/instance/peers ₍⇗₎
- [2024-11-14 19:46:35 in 0.33s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-14 10:18:53 in 0.17s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-14 01:47:37 in 0.35s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-13 15:38:47 in 0.16s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-13 07:34:15 in 0.17s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-12 21:36:49 in 0.70s]: IP: 116.202.11.35 / Error: http / HTTP status: 400
- [2024-11-12 13:05:53 in 0.91s]: IP: 116.202.11.35 / Error: http / HTTP status: 400