events.mbbit.de — Kassel Events
Change this to a proper description of your instance
Details
up since 2024-06-08 06:55 (25.2 days ago)
- Uptime: 31.78%
- Users: 1
- Posts: 7
- Posts per user: 7.00
- Peers: 0
- Version: Mobilizon 3.0.0-dirty
- 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-11-10 (19.7 months ago)
Last successful contact: 2024-07-03 (3.1 minutes ago)
Contact: 4382 successful, 2190 failed.
Average fetch time: 1.68s
Next attempt scheduled for 11.9 minutes from now.
Found through talkabout.cf (nxdomain)
IP address: 212.227.213.84 (and 2 others: friendica.mbbit.de (up), social.mbbit.de (up))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-03 11:35:05 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 11:19:06 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 10:13:00 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 09:25:29 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 08:37:18 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 05:19:05 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 03:01:25 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 02:25:28 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 01:37:16 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- [2024-07-03 01:05:42 in 0.00s]: IP: 212.227.213.84 / Error: http / HTTP status: -1
- /.well-known/nodeinfo/2.1 ₍⇗₎
- [2024-07-03 11:51:07 in 1.05s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 11:00:22 in 2.36s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 10:44:22 in 0.91s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 10:28:42 in 1.34s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 09:57:03 in 1.94s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 09:41:24 in 0.80s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 09:09:17 in 0.86s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 08:53:21 in 1.02s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 08:16:49 in 0.78s]: IP: 212.227.213.84 / OK / HTTP status: 200
- [2024-07-03 07:50:11 in 4.03s]: IP: 212.227.213.84 / OK / HTTP status: 200
- /api/v1/instance ₍⇗₎
- [2024-07-03 04:07:25 in 0.67s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-03 03:17:45 in 0.34s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-02 14:22:22 in 0.16s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-02 12:25:15 in 0.16s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-02 05:45:04 in 0.22s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 14:40:29 in 0.18s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 13:56:27 in 0.16s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 13:23:12 in 0.15s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 08:19:20 in 0.21s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 05:24:42 in 0.97s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- /api/v1/instance/peers ₍⇗₎
- [2024-07-03 07:50:11 in 0.58s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-02 23:39:55 in 0.68s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-02 15:27:26 in 0.27s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-02 07:03:41 in 0.29s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 22:45:35 in 0.16s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 12:43:04 in 0.16s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-07-01 04:36:56 in 0.57s]: IP: 212.227.213.84 / Error: http / HTTP status: 400
- [2024-06-30 19:10:51 in 0.18s]: IP: 212.227.213.84 / Error: http / HTTP status: 400