evangelisches.online — die Funkwhale-Instanz des Dekanat Cham
Details
up since 2024-11-27 06:03 (89.6 days ago)
- Uptime: 99.94%
- Users: 3 (0 active this month, 0 active last six months)
- Posts: 0
- Peers: 0
- Version: funkwhale 1.4.0.dev0+59687b2f
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2021-04-09 (3.9 years ago)
Last successful contact: 2025-02-24 (32.6 minutes ago)
Contact: 26483 successful, 18659 failed.
Average fetch time: 2.99s
Next attempt scheduled for 10.9 minutes ago.
Found through social.fedcast.ch (nxdomain)
IP address: 92.60.37.108 (and 22 others, including: podcast.kom-in.de (down), podcasts.homes (down), cyprus.mastodontech.de (down), quasselkopf.de (up), kirche.peertube-host.de (down), peertube.mobilsicher.de (down), kirche.funkwhale-host.de (down), video.rs-einrich.de (up), video.campusgemeinde.de (down), climate.dance (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-02-24 16:43:10 in 0.00s]: IP: 92.60.37.108 / Error: http / HTTP status: -1
- [2025-02-24 15:22:00 in 0.00s]: IP: 92.60.37.108 / Error: http / HTTP status: -1
- [2025-02-24 14:40:36 in 0.00s]: IP: 92.60.37.108 / Error: http / HTTP status: -1
- [2025-02-24 03:03:37 in 0.00s]: IP: 92.60.37.108 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-02-24 18:10:19 in 0.14s]: IP: 92.60.37.108 / Error: http / HTTP status: 301
- [2025-02-24 16:00:40 in 0.15s]: IP: 92.60.37.108 / Error: http / HTTP status: 301
- [2025-02-24 05:07:57 in 0.14s]: IP: 92.60.37.108 / Error: http / HTTP status: 301
- [2025-02-23 19:27:36 in 0.14s]: IP: 92.60.37.108 / Error: http / HTTP status: 301
- [2025-02-23 13:37:49 in 0.41s]: IP: 92.60.37.108 / Error: http / HTTP status: 301
- [2025-02-22 15:05:20 in 0.39s]: IP: 92.60.37.108 / Error: http / HTTP status: 301
- /api/v1/instance/nodeinfo/2.0 ₍⇗₎
- [2025-02-24 19:54:24 in 0.95s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 18:57:45 in 1.60s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 18:10:19 in 0.74s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 17:25:47 in 1.13s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 16:00:40 in 0.89s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 13:57:42 in 0.79s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 13:13:12 in 0.86s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 12:30:59 in 0.78s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 11:43:47 in 0.89s]: IP: 92.60.37.108 / OK / HTTP status: 200
- [2025-02-24 10:48:52 in 0.96s]: IP: 92.60.37.108 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2025-02-24 09:49:49 in 0.20s]: IP: 92.60.37.108 / Error: http / HTTP status: 404
- [2025-02-23 16:35:47 in 0.19s]: IP: 92.60.37.108 / Error: http / HTTP status: 404