Spanning the last few weeks, Ning Networks across both our 2.0 and 3.0 platforms have experienced sporadic access and connectivity issues. These issues have had two causes:
1. High Loads on Specific Server Clusters: During specific networks’ peak loads, the cluster of servers housing those networks can be unable to process new customer requests in a timely manner, resulting in timeouts or 500 errors. These networks have been identified, and we’re working with those Network Creators to better manage resources during these peak loads. We are also implementing system changes on our back-end to reduce the likelihood of this occurring in the future.
2. Scheduled Back-end Maintenance: As a result of some Network Creators running into issues connecting to their networks or any other Ning Network or Ning.com while traffic was being routed through one of our primary internet service providers (ISPs), we switched providers to ensure access for all of our Network Creators. Back-end maintenance scheduled to switch from one service provider to another resulted in the outage seen on May 13. While our on-call team restored service, some lingering, albeit intermittent, connectivity issues remained for some Network Creators. Currently, you may see these issues manifest on your network as uploaded images not saving, members being unable to sign in, posts or changes not saving, slow loading, or delayed or missing notifications/messages.
Once these issues are resolved, we’ll continue to closely monitor the system to ensure there aren’t any further connection issues. During our next back-end maintenance window, we will implement additional configuration enhancements to ensure peak platform performance. Should any of this back-end maintenance work have user-facing effects, we will notify you of the maintenance window, scheduled during low traffic hours, as we have done in the past.
We understand how important platform performance and uptime are for you and your members, and we apologize for the impact and scope of the disruption of service the past few weeks. Our engineers have been working tirelessly to resolve these issues, and we appreciate your continued patience as they continue to do so.
We’ll be updating here as we have new information to share and hope to have everything completely resolved soon.
Update 5/26: Our engineers have resolved the larger network issues due to the ISP switch, so you’ll now be able to add images/files, sign in to, save changes and posts on your network. Outgoing messages and notifications are no longer held up or delayed. Our team has also resolved the separate issue of intermittent 500 errors. We’ll continue to make back-end improvements to prevent similar service disruptions in the future. If you’re still seeing any error messages on your network, please don’t hesitate to submit a ticket from your Dashboard or here.
You need to be a member of Ning Creators Social Network to add comments!
Replies
The Jamroom archiver works perfectly and provided you have an up to date backup the whole process of emigrating to Jamroom will take you anywhere between 10 minutes and half an hour :)
True - That's why there are alternatives. The CMS market wouldn't work if they were all the same :-)
Must take issue with that - there are plenty of ex-Ningsters now on Jamroom (and other platforms I believe) that have imported all of their Ning content and their new sites are live and thriving.
Your son-in-law is right. The Ning archive files are riddled with malformed code and missing formatting etc. But I've been importing Ning sites from the archive for over 18 months now and think I've now found all the bugs that might occur in them and have coded the importer tool to detect and work around them all. All archive files now import to Jamroom without issue.
Thanks - Paul
Let me tell you guys something. I've been on ning since I was 12..currently 20 years old. I pretty much grew up on here. What I will tell you guys is this. The internet is changing and it's doing so very fast. The longer you guys wait on Ning to get up and do something you'll be far behind. The platform i behind already and you guys are still waiting on 3.0. lol 3 YEARS we've been waiting. Do you guys remember how fast the internet changes within 3 years. 3.0 is already out of date before it even started. So i suggest you guys move on too. Just back here because found out i can take some users content via JSON. Anyways good luck guys. Just find a new platform that actually cares.
Awesome comment! You had me cracking up. This comment should be framed.
Our site has been off-line all day with the ERROR 500 errors. Calling support was a joke; the won't even open a support ticket, they just say "we know there's a problem" and hang up. Opening a support ticket using the http://hc.ning.com/contact/networkdown/index.php is a useless exercise, as the tickets no long show up on the dashboard in the ADMIN console and when you call NING Support and give them the ticket number, they say it "doesn't exist" or "they can't access the system at this time." It's like watching a car-wreck on slow-motion. What a tragic waste of a platform.
Got a NON-surprising 500 error when attempting to reach my own profile on my own Ning site... (The site's available but, my own profile REQUIRES refreshing the page ... feels a bit like 1996...)
Still getting 500 error when attempting to connect with my website. June 1st.
Got a NON-surprising 500 error when attempting to reach my own profile on my own Ning site... (The site's available but, my own profile REQUIRES refreshing the page ... feels a bit like 1996...)
We're getting 500 errors again. What a mess.
-
1
-
2
-
3
-
4
-
5
of 9 Next