mastodon.teppotastic.co.uk — Mastodon
Details
up since 2023-08-27 10:17 (8.7 months ago)
- Uptime: 99.80%
- Users: 2 (1 active this month, 2 active last six months)
- Posts: 1
- Posts per user: 0.50
- Peers: 1460
- Version: mastodon 4.2.8
- Registrations: Invite
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-05-03 08:39 — 2024-05-17 07:46
users: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯posts: 1 (0.00/day)
min/max/avg/stddev: 1 / 1 / 1.00 / 0.00
⋯ ⋯peers: 1460 (1.82/day)
min/max/avg/stddev: 1431 / 1460 / 1448.84 / 8.24
response_time: 11.037 (-10.54/day)
min/max/avg/stddev: 1 / 178 / 18.44 / 38.45
Crawling Info
First contact: 2023-01-22 (15.8 months ago)
Last successful contact: 2024-05-17 (45.8 minutes ago)
Contact: 20037 successful, 343 failed.
Average fetch time: 18.44s
Next attempt scheduled for 26.1 seconds from now.
Found through infosec.exchange (up)
IP address: 54.38.247.97 (and 929 others, including: sitc.masto.host (down), i.phill.gg (down), tl.timeattack.zone (down), mastodon.sawdustistan.org (up), masto.hitorino.tv (up), mastodon.heiperlan.de (down), social.grotz.me (down), tavern.calebhearth.com (down), social.kistler.dev (down), social.meawchill.xyz (down))
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-17 06:00:53 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-17 05:09:05 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-17 00:13:33 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 21:44:12 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 18:51:29 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 17:06:46 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 09:31:48 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-16 06:53:30 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-15 23:54:52 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- [2024-05-15 19:13:56 in 0.00s]: IP: 54.38.247.97 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-17 07:46:18 in 1.12s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 04:21:42 in 2.43s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 03:33:23 in 0.17s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 02:43:38 in 0.87s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 01:53:14 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 23:24:51 in 0.48s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 22:36:29 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 20:47:18 in 1.11s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 19:48:29 in 3.37s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 17:58:06 in 1.00s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-16 23:24:51 in 0.48s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-15 20:45:13 in 1.16s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-15 00:31:52 in 0.18s]: IP: 54.38.247.97 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-17 07:46:18 in 9.91s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 06:54:54 in 0.71s]: IP: 54.38.247.97 / Error: unparseable / HTTP status: 200
- [2024-05-17 04:21:42 in 7.04s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 03:33:23 in 1.29s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 02:43:38 in 8.71s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 01:53:14 in 1.62s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-17 01:02:40 in 0.66s]: IP: 54.38.247.97 / Error: unparseable / HTTP status: 200
- [2024-05-16 23:24:51 in 9.13s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 22:36:29 in 1.32s]: IP: 54.38.247.97 / OK / HTTP status: 200
- [2024-05-16 20:47:18 in 11.75s]: IP: 54.38.247.97 / OK / HTTP status: 200