Sked Social dashboard
Login Disruption Under Investigation
Our monitoring indicates that our service has been fully resolved. Please contact support if you keep experiencing any issues logging in or accessing the Sked Social dashboard.
We apologise for any inconvenience.
Amazon Web Services has reported that they have identified and fixed the problem, however some of their services are still recovering.
We are in touch with our upstream provider and have seen some users be able to login to Sked now, however some still report issues while the provider is recovering. We can confirm that publishing content was not affected during this outage.
We will provide an update once everything is fully resolved, which we expect to be imminent.
Here’s the latest update from AWS. https://health.aws.amazon.com/health/status
“We are seeing significant signs of recovery. Most requests should now be succeeding. We continue to work through a backlog of queued requests. We will continue to provide additional information”
Their team is actively addressing the issue, and we remain optimistic that a resolution will come soon. We’re closely monitoring the situation and will keep you updated as soon as it’s resolved. Thank you for your patience!
The issue seems to be part of a larger service disruption affecting AWS (Amazon Web Services), which you can monitor at https://health.aws.amazon.com/health/status. AWS is a cloud infrastructure provider used by thousands of companies worldwide to host websites, run applications, store data, etc. As a result, issues with AWS can have wide-reaching impacts across many platforms and services.
Based on our monitoring, posts are still being published as expected. However, users are currently unable to access the Sked dashboard.
Our team is actively monitoring the situation and staying in close contact with the necessary parties. We’ll continue to provide updates as soon as we receive more information. Thank you for your patience.
We’re currently investigating an issue that is preventing some users from logging into their accounts. Those impacted may encounter the following error message:
“The server did not receive a timely response from an upstream server…”
Initial investigations indicate that the issue is linked to our third-party billing system, which appears to be experiencing a disruption that is affecting login authentication.
Our engineering team has already escalated the matter and submitted a support ticket with the third-party provider. We’re actively working with them to resolve the issue as quickly as possible.
We understand how disruptive this can be and sincerely apologize for the inconvenience. Updates will be provided as soon as we have more information. Thank you for your patience and understanding.