twitterexiles.social — Twitter Exiles
Details
up since 2023-08-27 11:53 (8.2 months ago)
- Uptime: 99.77%
- Users: 4 (1 active this month, 3 active last six months)
- Posts: 2
- Posts per user: 0.50
- Peers: 4127
- Version: mastodon 4.3.0-alpha.3+glitch
- Registrations: Open
Stats 2024-04-19 19:56 — 2024-05-03 01:49
users: 4 (0.00/day)
min/max/avg/stddev: 4 / 4 / 4.00 / 0.00
⋯ ⋯posts: 2 (0.00/day)
min/max/avg/stddev: 2 / 2 / 2.00 / 0.00
⋯ ⋯peers: 4127 (2.25/day)
min/max/avg/stddev: 4096 / 4127 / 4112.55 / 9.35
response_time: 26.524 (-1.67/day)
min/max/avg/stddev: 1 / 181 / 34.89 / 43.14
Crawling Info
First contact: 2022-11-18 (17.5 months ago)
Last successful contact: 2024-05-03 (39.6 seconds ago)
Contact: 24454 successful, 231 failed.
Average fetch time: 34.89s
Next attempt scheduled for 52.8 minutes from now.
Found through kudabiverse.com (down)
IP address: 51.75.122.114 (and 72 others, including: bickr.net (down), slime.computer (up), social.bairwell.com (down), brands.town (up), smashingly.gay (down), grafana.social (up), blackqueer.life (up), fandom.garden (up), cyberpunk.lol (up), theculture.quest (down))
Staff
Michael Seeley: Photos of stuff (rockets preferred). @WeReportSpace co-founder; @NatGeo contributor; President, @Health_First Foundation. Follows&RTs≠endorse.
Responses
- /.well-known/nodeinfo ₍⇗₎
- [2024-05-02 17:46:11 in 0.00s]: IP: 91.132.147.113 / Error: http / HTTP status: -1
- [2024-04-30 09:37:40 in 0.00s]: IP: 91.132.147.113 / Error: http / HTTP status: -1
- /api/v1/instance ₍⇗₎
- [2024-05-03 01:49:48 in 0.20s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-03 00:56:00 in 0.42s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-03 00:02:10 in 0.21s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 23:08:06 in 0.77s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-02 22:13:47 in 0.75s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-02 21:19:35 in 0.25s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 20:25:40 in 0.19s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-02 19:32:26 in 0.46s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 18:39:16 in 0.28s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 16:52:53 in 0.20s]: IP: 51.75.122.114 / OK / HTTP status: 200
- /api/v1/instance/peers ₍⇗₎
- [2024-05-02 20:25:40 in 0.33s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-02 12:23:27 in 0.38s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 02:32:26 in 0.30s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-01 17:21:36 in 0.37s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-01 08:59:32 in 0.31s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-04-30 13:17:08 in 1.76s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-04-30 01:32:07 in 0.37s]: IP: 51.75.122.114 / OK / HTTP status: 200
- /nodeinfo/2.0 ₍⇗₎
- [2024-05-03 01:49:48 in 0.92s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-03 00:56:00 in 1.90s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-03 00:02:10 in 0.83s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 23:08:06 in 3.85s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-02 22:13:47 in 3.16s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-02 21:19:35 in 1.05s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 20:25:40 in 1.09s]: IP: 51.75.122.114 / OK / HTTP status: 200
- [2024-05-02 19:32:26 in 5.50s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 18:39:16 in 0.92s]: IP: 91.132.147.113 / OK / HTTP status: 200
- [2024-05-02 16:52:53 in 0.87s]: IP: 51.75.122.114 / OK / HTTP status: 200