remerge.net — remerge
Details
up since 2024-07-05 22:16 (13.0 hours ago)
- Uptime: 89.33%
- Users: 9
- Posts: 67
- Posts per user: 7.44
- Peers: 163
- Version: pleroma 2.4.1-11-g4327f0d0-v2-4-1-webfinger-fetch-initial
- Source code: https://git.pleroma.social/pleroma/pleroma
- Registrations: Closed
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-30 10:27 — 2024-07-06 11:04
users: 9 (0.00/day)
min/max/avg/stddev: 9 / 9 / 9.00 / 0.00
⋯ ⋯posts: 67 (0.00/day)
min/max/avg/stddev: 67 / 67 / 67.00 / 0.00
⋯ ⋯peers: 163 (0.00/day)
min/max/avg/stddev: 163 / 163 / 163.00 / 0.00
⋯ ⋯response_time: 5.906 (0.01/day)
min/max/avg/stddev: 2 / 17 / 9.24 / 5.56
Crawling Info
First contact: 2021-10-25 (32.4 months ago)
Last successful contact: 2024-07-06 (14.3 minutes ago)
Contact: 55414 successful, 10987 failed.
Average fetch time: 9.24s
Next attempt scheduled for 21.8 minutes from now.
Found through p.oshiteku.app (down)
IP address: 139.162.86.75 (and 4 others: ap-fed-test.remerge.net (down), peertube.remerge.net (down), pleroma.remerge.net (up), ap-relay.remerge.net (up))
Staff
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-06 06:13:27 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-06 00:31:00 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 21:43:42 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 20:04:49 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 19:31:38 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 18:58:32 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 15:32:23 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 12:38:18 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 01:17:28 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- [2024-07-05 00:11:59 in 0.00s]: IP: 139.162.86.75 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-06 11:04:11 in 0.33s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 10:24:55 in 0.83s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 09:44:10 in 0.43s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 09:05:06 in 0.37s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 08:29:59 in 0.37s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 07:55:49 in 0.35s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 07:21:33 in 0.35s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 05:38:31 in 0.36s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 05:02:04 in 2.46s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 04:26:13 in 0.86s]: IP: 139.162.86.75 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-06 09:44:10 in 0.41s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-05 22:49:49 in 0.32s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-04 21:57:58 in 0.30s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-04 11:03:54 in 0.30s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-03 22:57:35 in 0.28s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-03 12:33:21 in 0.31s]: IP: 139.162.86.75 / OK / HTTP status: 200
- /nodeinfo/2.1.json ₍⇗₎
- [2024-07-06 11:04:11 in 1.29s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 10:24:55 in 4.48s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 09:44:10 in 1.37s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 09:05:06 in 2.87s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 08:29:59 in 1.42s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 07:55:49 in 1.38s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 07:21:33 in 1.27s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 06:47:38 in 0.80s]: IP: 139.162.86.75 / Error: unparseable / HTTP status: 200
- [2024-07-06 05:38:31 in 1.32s]: IP: 139.162.86.75 / OK / HTTP status: 200
- [2024-07-06 05:02:04 in 5.17s]: IP: 139.162.86.75 / OK / HTTP status: 200