Bot status like looks
Welcome to the demo status page. Get email notifications whenever Discord creates or updates an incident. Get webhook notifications whenever Discord creates an incident, updates an incident, or changes a component status. The URL we should send the webhooks to. We'll send you email if your endpoint fails.
Visit our support site. Uptime over the past 90 days. Operational 90 days ago. System Metrics Month Week Day. Past Incidents May 6 May 5 Bot status like looks 4 May 3 May 2 May 1 Apr 30 Apr 29 Apr 28 Apr 27 Apr 26 Apr 25 Apr 24 Resolved - We believe service to be fully recovered.
We are aware of the root cause, and have been able to gather additional telemetry to aide our investigation in fixing this issue. Monitoring - Service is recovering now.
Investigating - We are aware of connection issues and are investigating. Apr 23 Resolved - The root cause here was that one of our guild bot status like looks crashed unexpectedly and the automated recovery hit a bug we were fixing last week but haven't deployed the fix for yet. This issue stalled the recovery, leading to the extended degradation of service bot status like looks saw here.
We will expedite deploying a bot status like looks for the recovery issue and will continue last week's investigation into the root cause that is leading a few of our systems to infrequently get into an escalating memory allocation spiral, ultimately leading to running out of memory.
Monitoring - We've identified the problem a crashed server and have brought it back online. We are investigating now. Apr 22
Features Pricing Support Sign bot status like looks Log in. Standup Bot appears to be up and functioning normally. It's been 26 days since the last service interruption. Submit a support request Follow us on Twitter. Tuesday, Apr 10 Monday, Apr 09 Or some standups just stopped working altogether. We bot status like looks found and fixed the issue finally. THere were standups "getting stuck" dude to surprise outages for our servers. We've added the appropriate restart mechanism and are glad to say we haven't heard of this issue for the last few days.
Thursday, Mar 22 Our database server is having connection due t o where it is physically located. Some standups are not starting on time because bot status like looks this.
Monday, Jan 08 Channels that are archived are no longer shown in this screen as it was creating some confusion to see them in the curren list of channels. We had another outage due to our queueing server filling up fast because of a lot of standups.
It was not a bug luckily. It was another spike in usage that we didn't catch again. Our developers assured us we have another alert for that type of usage spike and will not cause our servers to melt again from that.
Monday, Dec 04 Queueing server monitor memory threshold was met extremely quick due to more new customers that have come on with a spike. There are still a few standups experiencing problems starting. We are looking into the root cause right now to make sure they were restarted correctly. Monday, Nov 27 Deployed to several new servers to help with scaling bot status like looks. Some standups have been restarted automatically. Tuesday, Nov 21 More customers have signup and we're now experiencing issues with standups starting at 9AM and 10AM EST we're adding more servers as we speak to handle this new growth.
Tuesday, Nov 14 We've had 2 teams write in about standups not starting at their correct time. We're investingating why this is happening to a these few teams currently. Monday, Nov 06 Our internet service provider had a massive outage that we had no control over.
Standups should be restarting automatically. Sunday, Sep 24 After working with Slack, we've fixed the issue and also provided a better error message for another bot status like looks we found that was causing confusion with that same message. The new error message now has the correct procedure should someone try to execute an invalid command. Wednesday, Sep 20 Please re-sign in" error when attempting to start their standups.
We're currently working with Slack to fix this. Thursday, Jun 15 It looks like Amazon. Our platform runs on their Servers. So when they're down, we're down for now. Wednesday, May 10 One of our servers that handles starting all the standups ran out of memory and we did not have an alert set for that.
We've upgraded the memory. All standups have been running today. We bot status like looks currently looking into this. Wednesday, Mar 01 Issue when tryhing to start standupbot in channels is caused by a bug weve found and are fixing bot status like looks. It has to do with properly memoizing an expensive function call to Slack, will be deployed at end of day once all standups bot status like looks completed!
Tuesday, Feb 21 Fixed quite a few Email and standups not starting correctly issues. We had a work-queue that was not being "cleared" out bot status like looks time and was filling up and hitting max storage capacity which was preventing emails and standups from being started. Saturday, Feb 18 We had some memory issues with one of our servers so that should rectify most, if not all, of the standup issues! Also, our whole team will be able to get back to regularly scheduled support times!
Standups are not being started for a few customers. We have found the area where the problem is occuring and now attempting to completely understand why the issue is happening so we can properly implement the fix before the next standups run.