# Poor Glide support SOP **URL:** \ **Category:** Report a Bug\ **Created:** [October 14, 2024, 2:49pm UTC](https://community.glideapps.com/t/poor-glide-support-sop/77082 "2024-10-14T14:49:14Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\ **Post date:** [October 14, 2024, 10:09pm UTC](https://community.glideapps.com/t/poor-glide-support-sop/77082/5 "2024-10-14T22:09:01Z")
> [@Miroslav\_Madaric](#): > > put the focus on incident itself aside, do concentrate yourself to support procedures improvement! It will make the resolution of future incidents more effective! Ryan’s post where he explains what Glide is doing following the incident : > [@October 14th availability incident analysis](https://community.glideapps.com/t/october-14-availability-incident-analysis/77083/8): > > Here’s a [link to our official incident status and postmortem](https://status.glideapps.com/incidents/238771), where we will be following up with more details over the coming days. However, just to keep everybody on this thread up to date, I want to summarize a few things. Technical First of all, regarding the technical nature of this particular incident, it was the result of a database-level upgrade that we had planned for some time and had successfully executed in staging but hit an error when doing so in production. The upgrade involved m… --- _[View the full topic](https://community.glideapps.com/t/poor-glide-support-sop/77082)._