FA+
Shop
[UPDATED] Thursday Connectivity Update (06/27/13)
12 years ago
🏳️🌈💖Enjoy the site? Please consider supporting us via the links below!💖🏳️🌈
⭐ FA+ ⭐ SHOP ⭐ KO-FI ⭐
Journal Start
After testing and monitoring, we are confident enough to state that the issue has been resolved. We are still working with our host to isolate the exact cause of the problem, and will be doing continued testing over the next few days on replicating issue with the router.
In the mean time, we'd like to extend our thanks to everyone who submit tracelogs and reports. The overwhelming response (over 1,000+ notes! We had trouble keeping up!) was vital to helping us research the problem.
We'd also like to extend a special thank you to
kurin for creating http://isfaup.tk. The site helped us monitor the outage from a user's perspective when we could not see it first hand. Thanks to this, Kurin helped us narrow down the possibilities and helped get this resolved.
We had our host shut down the routing from from their secondary router (cr2.iad2.inforelay.net). The router is no longer active for FA, and should force people to route through the primary router (cr1.iad2.furaffinity.net) to connect to the site.
Please let us know if this helps with any connection issuess you may still be having.
In the mean time, we'd like to extend our thanks to everyone who submit tracelogs and reports. The overwhelming response (over 1,000+ notes! We had trouble keeping up!) was vital to helping us research the problem.
We'd also like to extend a special thank you to
kurin for creating http://isfaup.tk. The site helped us monitor the outage from a user's perspective when we could not see it first hand. Thanks to this, Kurin helped us narrow down the possibilities and helped get this resolved.We had our host shut down the routing from from their secondary router (cr2.iad2.inforelay.net). The router is no longer active for FA, and should force people to route through the primary router (cr1.iad2.furaffinity.net) to connect to the site.
Please let us know if this helps with any connection issuess you may still be having.
that'll be 1tb of porn please. nothing pony though. XD
Just putting this here. Kurin made a graph to track when FA was up/down for people on cr1.iad2.inforelay.net. You can see the very moment our host shut down the router. It goes from sporadic up/time time to solid up.
This. I like seeing this. This makes me happy. And incredibly angry, too. Mostly for the fact we've been telling our host it's not us, but them, and it's taken this long to resolve. But, we ARE working on it, and we'll continue to keep you informed.
I can't thank everybody who's given feedback/suggestions on this as there have been hundreds upon hundreds of comments and over 1,000 notes and a LOT of information to scour over.
However, SO FAR, over a 15 minute period, I've not had a single issue. I will make another comment here in about an hour or two to let you know it's still working, otherwise I'll be posting as Daneasaur on the FA forums.
The entire thing has been frustrating.
I do believe we have found the issue!
But yes, as of yesterday I can finally consistently connect to the site for the first time in 6 days... I waited a day to say that just in case it started acting up again.
Thanks.
Now.. to clear out those 1331 submissions I haven't been able to touch the past week or so. :|
http://isfaup.tk/bargraph.html
Also, I still do use cr2.iad2.inforelay.net in my route.
...
6 41 ms 41 ms 41 ms er2-xe-11-3-0.SanJoseEquinix.savvis.net [204.70.198.146]
7 42 ms 43 ms 42 ms cr2-tenge-0-5-0-2.sanfrancisco.savvis.net [204.70.200.198]
8 102 ms 103 ms 114 ms cr1-ten-0-13-1-0.dck.savvis.net [204.70.197.25]
9 105 ms 107 ms 107 ms msr1-tengig-0-0-0-0.Washington.savvis.net [204.70.196.94]
10 103 ms 103 ms 103 ms 204.70.206.137
11 103 ms 102 ms 102 ms dca1.inforelay.net [208.173.12.130]
12 104 ms 104 ms 104 ms cr2.iad3.inforelay.net [67.208.76.5]
13 103 ms 104 ms 103 ms cr2.iad2.inforelay.net [67.208.89.118]
14 104 ms 104 ms 114 ms cr1.iad2.inforelay.net [66.231.181.5]
15 103 ms 103 ms 104 ms 66.231.180.84
16 103 ms 104 ms 102 ms www.furaffinity.net [70.33.186.196]
The biggest one on my route is 2-3.r1.dc.hwng.net (69.16.190.25) 149.995 ms
Thank you so much, Fender.
Hooray!
Ping statistics for 70.33.186.196:
Packets: Sent = 9457, Received = 9443, Lost = 14 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 219ms, Average = 59ms
1. Why weren't they routed through the primary router in the first place?
2. Shouldn't the secondary router only exist to handle excessive loads, or to simply support the primary router when dealing with many requests? Why was it being treated as the primary router for them?
3. Why did this even impact them to begin with? Don't both routers share similar hardware and setup?
4. With the bottleneck known as the "secondary router" offline, are there any plans to fix the issues before bringing it back up? Will the cause of the problems be investigated next?
2) Basically, it does load balancing, putting X amount on one, Y amount on other. Helps balance things out... in theory.
3) Both routers are the same spec, same configuration. We don't know why the secondary went down and neither do they. We're still working with them closely. We're going to try rebringing up the second router tomorrow and see what happens.
4) We're working on bringing it back up tomorrow after they have a chance to look at it, and make sure it's set to secondary.
Now that's we've isolated the issue without question it makes it easlier for them to know where to look, or try to find out why.
Had some problems lingering this morning, but the last hour or so i've been online i've had no more problems.
wooo!
Now I can post giant god monsters once again!
Glad that this extremely long hassle has an end, heh.
Though I haven't been affected at all.
Pingdom doesn't help when only so many users are affected. If the pings don't go through the same route as as the users having trouble it doesn't help. =/
As I stated there, it seems to be working fine for me now.
If at any time tonight it fails, I'll update the post. Thankies! :)
In other words they wouldn't have the excuse to rake in as much donations.
I'll go ahead and point you to this journal http://www.furaffinity.net/journal/4389184/ where you all managed to get a shit load of hardware and a thousand dollars in two days.
Besides, it's not like this is even up to date.
course thats what I said last time and it broke again a day later XD
Now back to more drunken FA browsing. And maybe making more music. haha
Now if you'll excuse me, I have 985 pictures I need to go look at.
Then again...could take about 10 minutes or so to compile the data for the user...
after doing what users said since the beginning it magically works?
funny, isnt it?
The secondary router was trying to act as a second primary, causing a conflict between the two systems. This was not the general suggestion as to the source of the connectivity problems.