scm-ms.xsns.jp — Mastodon
Details
down since 2025-03-20 05:39 (166.5 minutes ago)
- Uptime: 95.71%
- Users: 1 (0 active this month, 1 active last six months)
- Posts: 0
- Posts per user: 0.00
- Peers: 3
- Version: mastodon 4.2.13
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats
No successful contact during the given timeframe.
Crawling Info
First contact: 2024-06-29 (8.7 months ago)
Last successful contact: 2025-03-19 (9.3 hours ago)
Latest attempt: 2025-03-20 (9.7 minutes ago)
Contact: 17920 successful, 3519 failed.
Average fetch time: 1.73s
Next attempt scheduled for 5.3 minutes from now.
Found through hallole.eu (up)
IP address: 162.43.46.64
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2025-03-20 06:26:13 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-19 13:28:10 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-19 12:53:16 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-19 09:40:22 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-19 07:11:16 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-19 04:37:41 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-18 23:30:15 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-18 12:53:01 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-18 10:12:45 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- [2025-03-18 07:24:52 in 0.00s]: IP: 162.43.46.64 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2025-03-19 10:21:42 in 0.12s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-19 01:22:10 in 0.12s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-19 00:11:22 in 0.54s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-18 17:45:56 in 0.68s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-18 04:28:39 in 0.16s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-17 15:10:19 in 0.12s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-17 13:43:57 in 0.12s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-16 17:00:48 in 0.12s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-16 12:40:07 in 0.12s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-16 03:39:02 in 0.12s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- /api/v1/instance/peers ₍⇗₎
- [2025-03-19 23:08:31 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-19 14:59:00 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-19 06:32:25 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-18 21:23:25 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-18 10:49:45 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-18 01:05:53 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-17 15:10:19 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-17 06:44:03 in 0.53s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-16 22:11:08 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- [2025-03-16 14:07:46 in 0.12s]: IP: 162.43.46.64 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2025-03-20 08:15:55 in 0.47s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 07:57:04 in 0.61s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 07:34:38 in 0.49s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 07:18:34 in 0.47s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 07:01:47 in 0.49s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 06:43:45 in 0.59s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 06:06:00 in 0.62s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 05:39:10 in 0.74s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 04:32:13 in 2.77s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
- [2025-03-20 03:45:12 in 0.64s]: IP: 162.43.46.64 / Error: http / HTTP status: 502
Federation Info
Peers: 3
Federation restrictions
Unsalted hashes of "scm-ms.xsns.jp"
- MD5: 4e23ce394674d7e4b71f788b4d4311c2
- SHA1: c7b5f17dcc253aa7d10e8761063c50ace5f9bab3
- SHA256: bb5a4ea9a4c09156aba4fe66c9ba8b495d44188b65b4f75fb81725848e9fa2b0