fedi.niszogen.com
fedi.niszogen.com
Details
up since 2024-06-08 15:48 (22.9 days ago)
- Uptime: 62.78%
- Users: 1 (1 active this month, 1 active last six months)
- Posts: 49
- Posts per user: 49.00
- Peers: 0
- Version: snac 2.56-dev
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-23 16:21 — 2024-07-01 13:38
users: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ —posts: 49 (0.07/day)
min/max/avg/stddev: 48 / 49 / 48.33 / 0.47
peers: 0 (0.00/day)
min/max/avg/stddev: 0 / 0 / 0.00 / 0.00
⋯ —response_time: 3.183 (-4.24/day)
min/max/avg/stddev: 3 / 61 / 22.50 / 27.37
Crawling Info
First contact: 2024-01-23 (5.2 months ago)
Last successful contact: 2024-07-01 (4.3 hours ago)
Latest attempt: 2024-07-01 (13.3 minutes ago)
Contact: 4928 successful, 2285 failed.
Average fetch time: 22.50s
Next attempt scheduled for 35.4 minutes from now.
Found through social.trom.tf (up)
IP address: 104.21.58.142 (and 2 others: social.niszogen.com (down), mstdn.nere9.help (up))
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 13:38:31 in 1.05s]: IP: 104.21.58.142 / Error: http / HTTP status: 403
- [2024-07-01 12:48:37 in 2.25s]: IP: 104.21.58.142 / Error: http / HTTP status: 403
- [2024-07-01 12:00:18 in 1.92s]: IP: 172.67.160.91 / Error: http / HTTP status: 403
- [2024-07-01 11:11:37 in 1.84s]: IP: 172.67.160.91 / Error: http / HTTP status: 403
- [2024-07-01 10:23:18 in 1.85s]: IP: 104.21.58.142 / Error: http / HTTP status: 403
- [2024-07-01 08:38:15 in 1.08s]: IP: 172.67.160.91 / Error: http / HTTP status: 403
- [2024-07-01 07:46:29 in 0.00s]: IP: 104.21.58.142 / Error: http / HTTP status: -1
- [2024-07-01 02:57:09 in 0.00s]: IP: 104.21.58.142 / Error: http / HTTP status: -1
- [2024-07-01 02:08:50 in 2.28s]: IP: 172.67.160.91 / Error: http / HTTP status: 403
- [2024-07-01 01:21:03 in 1.38s]: IP: 172.67.160.91 / Error: http / HTTP status: 403
- /api/v1/instance ₍⇗₎
- [2024-07-01 09:32:34 in 0.21s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-07-01 06:57:06 in 0.18s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-07-01 06:08:32 in 0.20s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-07-01 05:20:18 in 0.20s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-07-01 04:32:01 in 0.19s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-07-01 03:44:07 in 0.18s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-07-01 00:34:11 in 0.19s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-06-30 23:46:25 in 0.19s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-06-30 22:57:28 in 0.19s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-06-30 22:07:01 in 0.19s]: IP: 172.67.160.91 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 06:57:06 in 0.18s]: IP: 172.67.160.91 / Error: http / HTTP status: 404
- [2024-06-30 06:46:43 in 0.19s]: IP: 172.67.160.91 / Error: http / HTTP status: 404
- [2024-06-29 08:18:46 in 0.18s]: IP: 172.67.160.91 / Error: http / HTTP status: 404
- /nodeinfo_2_0 ₍⇗₎
- [2024-07-01 09:32:34 in 0.71s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-07-01 06:57:06 in 0.57s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-07-01 06:08:32 in 0.67s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-07-01 05:20:18 in 0.66s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-07-01 04:32:00 in 0.56s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-07-01 03:44:07 in 0.61s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-07-01 00:34:11 in 0.60s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-06-30 23:46:25 in 0.59s]: IP: 172.67.160.91 / OK / HTTP status: 200
- [2024-06-30 22:57:28 in 0.65s]: IP: 104.21.58.142 / OK / HTTP status: 200
- [2024-06-30 22:07:01 in 0.57s]: IP: 172.67.160.91 / OK / HTTP status: 200