social.tulsa.ok.us — Tulsa Social
Details
up since 2024-06-10 15:05 (21.0 days ago)
- Uptime: 99.84%
- Users: 86 (17 active this month, 29 active last six months)
- Posts: 51239
- Posts per user: 595.80
- Peers: 20855
- Version: mastodon 4.2.9
- Registrations: Open
[View Timeline] (← Broken) | [View Timeline Media]
Stats 2024-06-17 14:01 — 2024-07-01 13:45
users: 86 (0.03/day)
min/max/avg/stddev: 78 / 86 / 85.94 / 0.69
posts: 51239 (30.87/day)
min/max/avg/stddev: 42495 / 51257 / 51010.90 / 750.87
peers: 20855 (10.18/day)
min/max/avg/stddev: 17972 / 20855 / 20755.49 / 246.20
response_time: 1.457 (-0.00/day)
min/max/avg/stddev: 0 / 63 / 3.83 / 4.88
Crawling Info
First contact: 2021-02-06 (3.4 years ago)
Last successful contact: 2024-07-01 (11.6 minutes ago)
Contact: 95407 successful, 10116 failed.
Average fetch time: 3.83s
Next attempt scheduled for 8.1 minutes from now.
Found through freespeechextremist.com (down)
IP address: 176.31.213.231 (and 157 others, including: chicken.rodeo (down), relay.plush.city (down), claris.cf (up), dobremiejsce.robmydobrze.pl (down), lotus-eyes.net (down), mastodon.art (up), mysound.directory (down), quigleys.org (down), blumpus.com (up), oour.org (up))
Staff
![](https://cdn.masto.host/socialtulsaokus/accounts/avatars/000/000/001/original/d0ee9b376688d86f.png)
Tulsa Social is a regional, general-interest instance for Green Country and surrounding areas.
For abuse complaints, please use the abuse reporting feature for fastest handling.
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-07-01 07:59:57 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-01 07:15:38 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-07-01 06:53:09 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-07-01 05:26:54 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-01 00:55:09 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-07-01 00:12:49 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-06-30 22:41:56 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-30 21:33:14 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- [2024-06-30 20:02:44 in 0.00s]: IP: 176.31.213.231 / Error: http / HTTP status: -1
- [2024-06-30 18:33:42 in 0.00s]: IP: 178.33.220.142 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-07-01 13:45:58 in 0.18s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 13:24:39 in 0.20s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-01 13:03:30 in 0.22s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 12:42:31 in 0.66s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 12:00:21 in 0.70s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 11:39:23 in 0.26s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-01 11:18:20 in 1.24s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 10:57:59 in 0.20s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-01 10:37:46 in 0.61s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 10:17:27 in 0.20s]: IP: 178.33.220.142 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-07-01 08:47:52 in 0.17s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-06-30 23:28:05 in 0.17s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-06-30 10:43:12 in 0.17s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-29 22:06:33 in 0.16s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-06-29 13:27:03 in 0.78s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-06-29 02:37:42 in 0.20s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-06-28 15:17:05 in 0.16s]: IP: 176.31.213.231 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-07-01 13:45:58 in 1.26s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 13:24:39 in 1.26s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-01 13:03:30 in 1.11s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 12:42:31 in 2.64s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 12:21:20 in 3.55s]: IP: 178.33.220.142 / Error: unparseable / HTTP status: 200
- [2024-07-01 12:00:21 in 3.50s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 11:39:23 in 3.51s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-01 11:18:20 in 5.71s]: IP: 176.31.213.231 / OK / HTTP status: 200
- [2024-07-01 10:57:59 in 1.09s]: IP: 178.33.220.142 / OK / HTTP status: 200
- [2024-07-01 10:37:46 in 7.28s]: IP: 176.31.213.231 / OK / HTTP status: 200