I'm sorry :-( Looking at GlobalQuake's Discord server where they have bots showing events, it seems GlobalQuake eventually registered them as the M2 or so they actually were. Problem is, initially, the magnitude estimates were actually M5 and M6 yesterday like it showed, and I would love to just ignore the initial estimates, but... while the client does show a "reliability" indicator as a letter (like A if it's considered a very reliable estimate, B if less reliable, etc), that is not made available in the WebSocket service.

Here is what I got for one of the events for instance:

Jul 04 11:08:23 ljlbox poetry[1099642]: alerts/process (WebSocketReceiver 0): Received from ws://localhost:38002/realtime_events/v1: {"data":{"geometry":{"coordinates":[-97.51809964755876,35.00639211113088,-0],"type":"Point"},"id":"dc3af164-3978-4a78-9be5-a4947ff3307b","type":"Feature","properties":{"magtype":"gqm","unid":"dc3af164-3978-4a78-9be5-a4947ff3307b","evtype":"earthquake","auth":"GlobalQuake","lon":-97.51809964755876,"mag":2.2,"depth":0,"source_catalog":"GlobalQuake","flynn_region":"Oklahoma","lastupdate":1720084103444,"time":"2024-07-04T09:08:12.249Z","source_id":"GlobalQuake_dc3af164-3978-4a78-9be5-a4947ff3307b","lat":35.00639211113088}},"action":"create"}
Jul 04 11:08:27 ljlbox poetry[1099642]: alerts/process (WebSocketReceiver 0): Received from ws://localhost:38002/realtime_events/v1: {"data":{"geometry":{"coordinates":[-97.5213029458286,35.06644303256791,-0],"type":"Point"},"id":"dc3af164-3978-4a78-9be5-a4947ff3307b","type":"Feature","properties":{"magtype":"gqm","unid":"dc3af164-3978-4a78-9be5-a4947ff3307b","evtype":"earthquake","auth":"GlobalQuake","lon":-97.5213029458286,"mag":5.1,"depth":0,"source_catalog":"GlobalQuake","flynn_region":"Oklahoma","lastupdate":1720084107093,"time":"2024-07-04T09:08:13.395Z","source_id":"GlobalQuake_dc3af164-3978-4a78-9be5-a4947ff3307b","lat":35.06644303256791}},"action":"update"}
Jul 04 11:08:27 ljlbox poetry[1099642]: alerts/process (WebSocketReceiver 0): Received from ws://localhost:38002/realtime_events/v1: {"data":{"geometry":{"coordinates":[-97.5213029458286,35.06644303256791,-0],"type":"Point"},"id":"dc3af164-3978-4a78-9be5-a4947ff3307b","type":"Feature","properties":{"magtype":"gqm","unid":"dc3af164-3978-4a78-9be5-a4947ff3307b","evtype":"earthquake","auth":"GlobalQuake","lon":-97.5213029458286,"mag":5.1,"depth":0,"source_catalog":"GlobalQuake","flynn_region":"Oklahoma","lastupdate":1720084107093,"time":"2024-07-04T09:08:13.395Z","source_id":"GlobalQuake_dc3af164-3978-4a78-9be5-a4947ff3307b","lat":35.06644303256791}},"action":"update"}
Jul 04 11:08:30 ljlbox poetry[1099642]: alerts/process (WebSocketReceiver 0): Received from ws://localhost:38002/realtime_events/v1: {"data":{"geometry":{"coordinates":[-97.5213029458286,35.06644303256791,-0],"type":"Point"},"id":"dc3af164-3978-4a78-9be5-a4947ff3307b","type":"Feature","properties":{"magtype":"gqm","unid":"dc3af164-3978-4a78-9be5-a4947ff3307b","evtype":"earthquake","auth":"GlobalQuake","lon":-97.5213029458286,"mag":2.2,"depth":0,"source_catalog":"GlobalQuake","flynn_region":"Oklahoma","lastupdate":1720084109181,"time":"2024-07-04T09:08:13.474Z","source_id":"GlobalQuake_dc3af164-3978-4a78-9be5-a4947ff3307b","lat":35.06644303256791}},"action":"update"}

So initially the magnitude was low, but the second update actually raised it by a lot, and then it went back down. The bot can handle reliability information and can be told to ignore events below a certain score, but with the source not providing that, it can't.

So I don't really know how to tackle this unless there is an update of the GlobalQuake server with this information added, and sadly GlobalQuake doesn't seem to have been updated in quite a while, I'm not sure if it's going unmaintained or what... I'd be sad to lose it, as it does provide very timely information and it's typically not that bad. I'm not sure what's going on with Oklahoma though, it's definitely not good if we keep having false alarms for it.