status.nanoyagi.com — NanoYagi Status
Pleroma: An efficient and flexible fediverse server
Details
up since 2024-06-23 07:28 (8.3 days ago)
- Uptime: 93.69%
- Users: 2 (0 active this month, 0 active last six months)
- Posts: 0
- Posts per user: 0.00
- Peers: 80
- Version: pleroma 2.6.0
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2023-07-25 (11.2 months ago)
Last successful contact: 2024-07-01 (23.0 minutes ago)
Contact: 12214 successful, 1300 failed.
Average fetch time: 4.99s
Next attempt scheduled for 66.2 seconds from now.
Found through social.fedinet.de (down)
IP address: 136.50.100.44
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 12:57:56 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-07-01 07:41:00 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-07-01 00:15:02 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-06-30 23:26:01 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-06-30 18:03:56 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-06-30 16:51:01 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-06-30 14:29:39 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-06-30 11:39:30 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-06-30 07:21:40 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- [2024-06-30 05:23:57 in 0.00s]: IP: 136.50.100.44 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 13:33:28 in 0.67s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 13:14:20 in 0.39s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 12:41:35 in 0.09s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 12:25:14 in 0.04s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 12:02:50 in 0.63s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 11:46:44 in 0.09s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 11:30:01 in 0.10s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 11:13:27 in 0.10s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 10:51:42 in 0.47s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 10:33:54 in 0.09s]: IP: 136.50.100.44 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 05:58:44 in 0.97s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-06-30 17:34:23 in 0.62s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-06-30 04:18:35 in 0.08s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-06-29 18:31:27 in 0.50s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-06-29 10:23:56 in 0.09s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-06-29 02:15:01 in 0.05s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-06-28 17:11:50 in 0.09s]: IP: 136.50.100.44 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-07-01 13:33:28 in 2.66s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 13:14:20 in 2.37s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 12:41:35 in 0.33s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 12:25:14 in 0.20s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 12:02:50 in 2.53s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 11:46:44 in 0.57s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 11:30:01 in 0.33s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 11:13:27 in 0.51s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 10:51:42 in 2.02s]: IP: 136.50.100.44 / OK / HTTP status: 200
- [2024-07-01 10:33:54 in 0.40s]: IP: 136.50.100.44 / OK / HTTP status: 200