Has API response time degraded?

[Doug Bartlett]

I have an autocross timing & scoring application that uses the MSReg APIs to query the list of events to find a list of upcoming autocross events for a specified organization.  This has worked very well with a 5 second timeout for almost 2 years.  However recently it appears to take nearly longer (~6-7 seconds) to receive the reply from the API get at:

/rest/calendars/organization/<msrOrgId>.json?start=<date>

Is there a known reason for the slow API response?  This creates a very noticeable lag in my application performance when creating a new AX timing database.  Previously the response delay was nearly imperceptible (< 2 seconds).

[Doug Bartlett]

It appears that the problem I am observing here has nothing to do with MSReg.  There is something happening on Debian Linux running in a Parallels VM that is causing network connections to initiate VERY slowly, independent of the destination.  Even pings fail to respond for about 6 -7 seconds, yet the response time on all pings to api.motorsportreg.com is sub 50mS and no pings are lost...  I also ran Wireshark to trace all packets between here and api.motorsportreg.com and once the connection starts, the entire transaction completes in well under 1 second.

I suspect the issue began after a recent Debian Bookworm upgrade.  :-(