Forum has been sluggish lately

[peteski]

It has been happening for the last few days. Today I even got "can't connect to the database" error for several minutes. @John @tom mann , you might want to check into this. Is it a server issue or some AI bot is bogging the forum down?

[Mark5]

I'm experiencing the sluggishness today. It's been intermittent.

[C855B]

Same here. Past few days.

[peteski]

The sluggishness continues today so far (but maybe  not quite as bad as yesterday).

[John]

Network Latency

traceroute

3   100.41.22.228  21.154ms  21.101ms  17.406ms
  4   *  *  *
  5   *  *  *
  6   154.54.83.201  179.155ms  87.428ms  77.047ms
  7   154.54.162.165  46.388ms  42.411ms  54.431ms
  8   154.54.7.129  33.183ms  48.780ms  153.865ms
  9   154.54.166.73  59.561ms  40.415ms  39.537ms
 10   154.54.95.109  51.722ms  *  *
 11   154.54.86.165  57.615ms  58.361ms  57.680ms
 12   154.54.173.62  60.527ms  51.081ms  56.476ms
 13   154.54.172.250  59.855ms  59.652ms  58.235ms
 14   38.142.162.42  60.358ms  58.701ms  58.599ms
 15   *  *  *
 16   162.244.254.211  61.039ms  57.302ms  58.812ms

Ping

PING 162.244.254.211 (162.244.254.211) 56(84) bytes of data.
64 bytes from 162.244.254.211: icmp_seq=1 ttl=55 time=73.4 ms
64 bytes from 162.244.254.211: icmp_seq=2 ttl=55 time=53.5 ms
64 bytes from 162.244.254.211: icmp_seq=3 ttl=55 time=73.9 ms
64 bytes from 162.244.254.211: icmp_seq=4 ttl=55 time=61.9 ms
64 bytes from 162.244.254.211: icmp_seq=5 ttl=55 time=56.5 ms
64 bytes from 162.244.254.211: icmp_seq=6 ttl=55 time=62.9 ms
64 bytes from 162.244.254.211: icmp_seq=7 ttl=55 time=59.9 ms
64 bytes from 162.244.254.211: icmp_seq=8 ttl=55 time=61.9 ms
64 bytes from 162.244.254.211: icmp_seq=9 ttl=55 time=56.7 ms
64 bytes from 162.244.254.211: icmp_seq=10 ttl=55 time=59.2 ms
64 bytes from 162.244.254.211: icmp_seq=11 ttl=55 time=68.8 ms
64 bytes from 162.244.254.211: icmp_seq=12 ttl=55 time=53.7 ms
64 bytes from 162.244.254.211: icmp_seq=13 ttl=55 time=65.1 ms
64 bytes from 162.244.254.211: icmp_seq=14 ttl=55 time=61.3 ms
64 bytes from 162.244.254.211: icmp_seq=15 ttl=55 time=56.0 ms
64 bytes from 162.244.254.211: icmp_seq=16 ttl=55 time=57.8 ms
64 bytes from 162.244.254.211: icmp_seq=17 ttl=55 time=60.3 ms

[C855B]

...
  6   154.54.83.201  179.155ms  87.428ms  77.047ms
  7   154.54.162.165  46.388ms  42.411ms  54.431ms
  8   154.54.7.129  33.183ms  48.780ms  153.865ms
  9   154.54.166.73  59.561ms  40.415ms  39.537ms
 10   154.54.95.109  51.722ms  *  *
 11   154.54.86.165  57.615ms  58.361ms  57.680ms
 12   154.54.173.62  60.527ms  51.081ms  56.476ms
 13   154.54.172.250  59.855ms  59.652ms  58.235ms
...

That sure is an awful lot of time bouncing around in the same subnet.

[C855B]

Something is going on. Some clicks are taking more than a minute to turn around.

[wcfn100]

Could be the 70 "guest" accounts that have been cycling through the forum all day.

Jason

[C855B]

Some sort of DDOS attack? Who'd we pi$$ off? 

[C855B]

Just another datum to consider - that 154.54.x.x subnet John found belongs to Cogent, Inc., an "Internet vulnerabilities" filter. It's apparently something similar to Cloudflare. Whether this service, probably imposed by the hosting company we're on, is materially impacting performance is something for the experts (not I!) to determine.

[peteski]

Currently the response seems back to normal, even with 38 guests browsing the forum.

[ridinshotgun]

There has been chatter that AWS has been having issues related to what is going on in the Persian Gulf currently along with issues of hacktivists backing enemy states hitting various web services related to other hosting services.

Several sites I frequent just in the past few days were having not only hosting issues but also issues with a larger payment processing provider that were being hit.