well it's working fine for me so I'm guessing I'm fine?

Your username made me laugh my fucking ass off.

what? ^w^;

why

^this

2nd

There is nothing wrong with baby furs. If you don't agree with them then why don't you just leave him alone and be on your way. Making negative comments about him isn't going to make your disagreement with baby furs credible. Its making him the victim and putting you in the place of a perpetrator. Grow up and stop your blind hatred. To tell you the truth I don't exactly agree with baby furs either but, I respect my friends who are because its the inside of the fur that counts. Baby fursonas are a tool for artful expression. All furs are that way in some form or another.

Honestly there really isn't any way of knowing whether or not the person was being offensive or hates babyfurs I was just asking why, they could have been laughing for a completely different reason which is why I didn't assume anything.
Also what does not agreeing with babyfurs mean, exactly I don't understand.

...You know, I also laughed at the name, but not because I hate baby furs, it was because the name was so generic or whatever, kinda like someone would have username of "animelovercoolfun". I'm not sure if that was why VivianFox laughed or not, but what I can see is that it was more like harmless fun than hate.

Yeah that's basically what I was thinking as a possibility too. I don't like to assume things about people it's a little paranoid.

I don't see how the comment was inherently negative.

Wow^

Hey, it could have been negative, or it could have been a good laughter. No way of knowing, and it's stupid to automatically assume one way or the other.

No not you I like what you said.
I just think that it's funny how really small stuff like this can become so big here.
I didn't think it was negative either.

I'm a babyfur and I found it funny. It doesn't make it inherently negative if its just a laugh, it could just be funny. Now if he'd said something along the lines of "your nick made me laugh you perverted piece of scum" then yes... that's pretty unacceptable behavior, but i've seen some funny icons and names and told them. it's not meant to be taken negatively, it's just to recognize their creativity (or occasionally lack-there-of)

Well there was a possibility of it being offensive so I stood up for him. I wasn't going to sit by and let someone get hurt knowing there was that possibility.

cool! thanks for telling us about this! finally its going be fixied.

Hm, now we wait for this outage then.

Brace yourselves

Outage is coming

*Ned Starkin'*

-drops glasses-

Oh, my sweet online child, what do you know about fear? Fear is for the outages, when the error messages fall a hundred feet deep. Fear is for the site redesigns, when the domain name hides for years, and children are born and live and die all in the glow of computer screens. That is the time for fear, my fellow furry, when the porn addicts move through the fetish sites... Thousands of years ago, there came a DOS attack that lasted a generation. Furries froze to death in their mothers' basements, same as the hobos in their cardboard boxes, and women smothered their babies so they could click the refresh button every minute, and wept, and felt their tears freeze on their cheeks.

...also, if you keep Ned Starking for too long, you'll probably get beheaded.

SPOILER ALERT

(also thumbs up)

'as usualy'

xP

I was about to say that, too.

Lol, props for the Aliens reference. :3

Woot! Hope to see it coming back up to full functionality again. \o/

Hopefully this fixes the recurring 504 errors I'm getting on my phone.

am I the only one that thought that said 'outrage'? :P

I read it that way too XD

yep, don't mind me, I'm just silly that way :P

Bad thind. I read it that way twice XD

that's ok, it's all Fender's fault :D

lmao Yep XD

So is this going to "fix" the uploading issues, SO MANY FOLKS ARE WRITING about?

That's the thing with such errors which don't occur to eevryone.. it's hard to track them down and even harder to tell whether what you try will work, lol.

Okey dokey then :3

Lol

*raises paw* Seconded. I've been having uploading issues ever since I first joined. >.<;

Apparently, ppl are still experiencing it.

That's our FA!

I haven't had a single issue with fa. but I hope this resolves things for everyone else.

Sometimes it takes a while for FA to load up, but hopefully things will be fixed.

I remember when hearing the word "OUTAGE" meant something from an entire day to a week...

Kudos and many props to the FA team for keeping these periods of no service to a bare minimum. Your tech and methods have improved! :)

Long as that month-long outage never happens again, it'll all be kosher, methinks c:

And also if those promised updates come within the year! xD

OH MY GOD AN OUTAGE

EVERYONE RUN FOR THE HILLS

WHAT WILL I EVER DO FOR TEN MINUTES!??!?!?!?!?!?!?!?

Hahaha xD

HAHA your icon just made this far more hilarious then it should have XD

I'll do your mom. :3

NOT THE OUTAGES.
I can't go five minutes without FA!

I know you guys will find the issue and correct is c:
Goodluck though, random hard to find bugs are never fun.

Correct it*

So, you don't want ANY control samples at all?

*nods* Interestingly, I can connect to FA fine, but traces to both furaffinity.net and facdn.net time out at my own router, which is strange.

Your router probably blocks ping requests.

Who do I send it to? The first time I sent traces, I noted this account, and spaced that it ignores the notes. I don't want that mistake again.

here's where I always have issues: https://www.furaffinity.net/view/10908512/

on four different ISP's, seven different computers and devices, on both mac, pc, androd tablets and ipad devices. it is always the same poiint that is unreachable.

by the way little side note: it has actually got worse since the reset. before I was getting about 15 - 30% packet loss to that same IP now it's about 50 - 60%.

I really really hope this fixes the problem.. because I want to upload over here again!

I dont mind outages, but can Fender say something to me. Cause I like Fender ^ ^

yay ^ ^

senpai noticed you!

thank you for having the CORRECT information to get the data...

" 1) Click Start > Run and type in "CMD". Alternatively, in Windows 7 or late you can hit Windows+R, then type in "CMD"."

Windows+R has worked since Windows 95, at least. However, at least now you guys are actually providing proper traceroute instructions.

Will any relevant response be made to any of the many comments that have been stating the problem to be something other than what it's been represented as being (which is apparently impossible and misleading techno-speak in the opinion of several seemingly knowledgeable people)?

Just a few:

https://www.furaffinity.net/journal...../#cid:34291211
http://www.furaffinity.net/journal/...../#cid:34338101
http://www.furaffinity.net/journal/...../#cid:34352615
http://www.furaffinity.net/journal/...../#cid:34368362

The only one of those to get a response just said "taking it up with them!" So how'd that go? Assuming "them" is whoever said it was a DNS issue, what did "them" say when you mentioned a whole bunch of folks agreeing that's a load of nonsense?

What's the point in anybody bothering with tracert when you've not given a serious response to people telling you what the problem is? The consensus also seems very strong that whoever gave the original explanation about it being DNS has no idea what they're talking about. So maybe an update on that note, letting people know that you're not ignoring this community's VAST resources of competent and professional tech-minded users more than willing to help, in favor of someone who is, by intention or ignorance, spouting bullshit.

Nobody is trying to make you feel bad or look bad. This community has always been spilling over with people wanting nothing more than to help. But they tend to be ignored rather vehemently, and it's not slander or defamation when people point out how something makes the site look bad in the hopes the site will stop doing it.

If none of that is to be addressed, then what's the point of these update journals at all?

http://www.furaffinity.net/journal/...../#cid:34368362

Derped on last link, sorry.

Responses of this nature given to the individuals who seem to have experience in this area could result in more helpful feedback from them. With more informed eyes on the problem, a solution may come quicker, and give you something more useful to take back to the host. Several people seem fairly confident that what they can see does not support the theory of a DNS issue being the cause of the performance problems.

I don't know shit about this stuff, personally. The people who do seem to feel they can help you pinpoint the issue. Respond to them, listen to them, let them help.

That's a valid point, and we will be giving feedback where we can.

As for feedback, this kinda feels like you have OSPF or somesuch between your router and InfoRelay's router. I would expect that both your router and theirs may be emitting error messages on this subject. It would be best to check to make sure settings required on your end have not changed.

I can be of assistance if you need it, I will require troubleshooting data tho (logs, captures, etc).

I sent about 20 tracert logs to the host last night, but if they don't get back tonight, I may just send 'em your way. We are blocking UDP on some ports, but we did notice a consistent pattern. When people can access the site successfully the tracert goes right from IR's router to our own, no issues. When they fail the traces hit IR's router, have 6-12 time outs... but never hit us. We never get the data, then it times out. Same person pings again, it's fine.

We've got high traffic going to the site, and only a small subset are affected. No internal errors on our side, no packet loss, no issues. It's not consistent, so I feel like there's a routing issue somewhere. cr2.iad2.inforelay.net seems to be the constant for 99% of people.

SUCCESSFUL TRACES
11 38 ms 39 ms 44 ms cr2.iad2.inforelay.net [67.208.89.118]
12 46 ms 39 ms 36 ms 66.231.180.84
13 42 ms 39 ms 46 ms www.furaffinity.net [70.33.186.196]

FAILING TRACES
15 95 ms 80 ms 99 ms cr2.iad2.inforelay.net [67.208.89.118]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.

Actually... I just realized something. Going back through my email, IR did a bunch of upgrades/maintenance on June 15. It was at multiple facilities, but this all started about that time. That's the ONLY thing that changed, and we never had any issues like this before.

It may also be worth asking users which ISP they are with. I've seen it multiple times with specific ISPs having trouble forwarding through a relay.

Browsing through the comments there is a general theme with certain ISPs, 'Brighthouse' pops up as being one to look at as I've seen a ton of users reporting they are unable to connect with them.

- Luna

Also as an add-on I've noticed that all people experiencing the issue (the people who have posted tracert publicly) are relaying through the relay at cr2.iad2.inforelay.net [67.208.89.118].

I'm relaying through cr1.iad2.inforelay.net [66.231.176.246] and havn't had any issues.

May be worth looking at that relay as well.

- Luna

Yep, and that's what we've been looking at.

Coincidently following some links above, I just experienced a wibble.

And I would concur with some other users, the problem appears to be 66.231.180.84

root@debian:~# traceroute -I www.furaffinity.net
traceroute to www.furaffinity.net (70.33.186.196), 30 hops max, 60 byte packets
1 bebox.config (192.168.1.254) 24.051 ms 23.679 ms 23.146 ms
2 * * *
3 10.1.2.5 (10.1.2.5) 32.543 ms * *
4 * * *
5 * * *
6 * * *
7 * e4-4.r1.am.hwng.net (209.197.0.229) 37.985 ms 38.303 ms
8 2-3.r1.dc.hwng.net (69.16.190.25) 114.632 ms 120.452 ms 112.236 ms
9 209.197.18.26 (209.197.18.26) 112.182 ms 119.511 ms 118.658 ms
10 216.151.186.242 (216.151.186.242) 115.239 ms 114.859 ms 116.363 ms
11 * * *
12 * * *
13 * * *
14 66.231.180.84 (66.231.180.84) 118.531 ms * *
15 * * *
16 * * *
17 * * *
18 66.231.180.84 (66.231.180.84) 120.987 ms * *
19 * * *
20 * * *
21 * * *
22 * 66.231.180.84 (66.231.180.84) 114.595 ms *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *


And now the site is working again, via that same device:

root@debian:~# traceroute -I www.furaffinity.net
traceroute to www.furaffinity.net (70.33.186.196), 30 hops max, 60 byte packets
1 bebox.config (192.168.1.254) 48.010 ms 47.455 ms 46.899 ms
2 * * *
3 10.1.2.5 (10.1.2.5) 30.879 ms * *
4 * * *
5 * * *
6 * 1-2.r1.lo.hwng.net (195.66.224.227) 39.259 ms *
7 * * e4-4.r1.am.hwng.net (209.197.0.229) 33.815 ms
8 2-3.r1.dc.hwng.net (69.16.190.25) 121.513 ms 121.132 ms 111.383 ms
9 209.197.18.26 (209.197.18.26) 113.576 ms 112.342 ms 113.046 ms
10 216.151.186.242 (216.151.186.242) 113.412 ms 136.193 ms 114.400 ms
11 cr1.iad2.inforelay.net (66.231.176.246) 111.302 ms 111.924 ms 117.680 ms
12 66.231.180.84 (66.231.180.84) 111.695 ms 111.763 ms 111.198 ms
13 www.furaffinity.net (70.33.186.196) 113.240 ms 114.171 ms 113.442 ms

It certainly does appear to be a wonky load balancer and worthy of some deep scrutiny.

Who is your ISP?

bethere.co.uk, although they've recently been bought by Sky of all evils (was owned by O2 / Telefonica) - not sure if any infrastructure changes have been made yet so I don't really know where my packets go.

I'm looking into that IP.

Consider also a simple switch problem - I've seen similar weirdness before now when a tired or overheating switch starts dropping packets all over the floor while appearing to still be alive and well. Often overlooked, but no less probable.

Similarly a failing interface / cabling on other network kit. I'd be expecting to see high interface error rates in such a situation.

These are not the type of switches to overheat and drop packets. Cisco switch fabric is designed to recover from conditions where packets may be dropped because of hardware faults, its a big quivering mess of watchdog timers and heartbeat lines.

~ That guy who works for a former (Cisco left the market) competitor to Cisco.

I don't know what kit FA runs, or what monitoring they do. Maybe it's something Cisco, but I wouldn't expect it to be too high-end. They're not exactly a carrier-grade kinda business.

I've seen Cisco switches fail in bizarre ways (most recently 37xx and 35xx). It can and does happen. Regardless, it would be bad practice to assume something like a switch (or any other kit) couldn't possibly fail just because it's expensive and claims to survive anything, and equally bad to assume because something seemsto be doing its job (especially something seemingly mundane as switching packets) it's therefore working properly. Besides, if it could never fuck up, it would never come with expensive support contracts :)

Obviously I'm not saying it is that - but a good engineer should be looking over all aspects of a failing complex system. Especially after more than a week of strangeness and who-knows-how-many traceroutes.

(Of course it irritates me too when some network admins themselves have a "NOPE NOPE NOPE!" attitude to any suggestion that their stuff might be faulty! My previous employer was terrible for that. I suppose passing the buck tends to be a pervasive attitude within IT, I don't know why it pisses me off the way it does.)

Consider this:

Traceroute will send a number of packets for each hop, if a switch is intermittently failing, it will drop some of those packets and not all of them, if it is completely failing, nothing will pass. In this case the failure is simultaneously both total for one group and not impacting for another, so its unlikely that its the switch on the port level, it may be an issue on the fabric level, but a quick check of the switch for responsiveness of the management interface and lack of fabric errors[1] would eliminate that as a possibility. The other aspect is that given this tier of switch (EN, edge, non-PoE, 1u, etc), in normal datacenter conditions (~70F) and all fans failed it still should not be at a temperature where it can overheat (>100F).

If the console is responsive, its highly unlikely that fabric issues would go undetected, and examining the port statistics would eliminate the ports in question from being possible causes. My point being that these switches don't simply overheat, they take a bit of effort to overheat, and then they do things which should make it plainly obvious that something is really, really wrong. Monitoring the switches and understanding what your are monitoring is essential to finding these faults, if you are not monitoring them then you are doing it wrong.

The second part of my point is that the ICMP packets are being returned with "Destination administratively prohibited" which indicates something other than a switch issue. So we ought to figure out why the horse is sick before looking for leaks in the barn roof.

1. It would likely be issues with disaggregation if it was the case.

Linux master race.

you realize that, well no, people could easily use your, no wait they could do that anyways. Nvm :/

i was going to say people could use the IP of your server to perform malicious things than I realized Script Kiddies already know this junk :/

Everything is still working fine for me.

If I had Mad Photoshop Skillz™, I'd get a picture of the "this is an outrage" guy and place him next to a computer screen showing a 504 error with the caption "THIS IS AN OUTAGE!"

But, I don't have those skills.

So what happens if they cant see FA to see this?

Well, considering it's been up for the last hour, at least someone was aware of it. Also, I believe it's been posted to the FAF, and that doesn't go down at the same time if I am correct in my thinking. c:

kk thanks just some of my freinds having the problem of FA just not loading at all.

I'll bake a few cookies using a text app on my phone, see if I can do something about this constant FA slowdown.

well done <3

That matches to your avatar amazingly! o.O

*snickers*

I got downtime while trying to load this journal... as well as commenting on it

WHOO YEAH
FINNA GET SHIT DONE

Hopefully this will fix the issue. will have to check when i get home from work cause fa works fine over 1xrtt(2g)data on my cellphone. If it working again I will have to find Fender and kiss him cause I'l be a happy tiger again.

last night i sent what info i was able to get from tracert when fa was down for me when it was up, also the tracert data from the 1xrtt(2g) connection that was worrking fine, hoping it woulg give enough info on the rotuing difference of a working connection vs an intermittent one.

also appologizes if my last post on the previous journal if it sound like i was being a smart a$$, just was upset my favorite website wasnt playing friendly

Would this fix the issue of my gallery folder being missing on my new account? Or is this a totally different problem?

A different problem, though that one is also getting looked at.

Scratch that still crashing

And didn't fix it, though it did stay out for less time that time.. and pages are loading faster between crashes. Noting.

I was wondering what happened. Pages are loading a bit slower after I could get connected again.

From what I have read online in the past FA outages were often for atleast a day but glad this one happened while I was too busy to check FA.

Still having issues. and none of my internet devices can copy/paste.

It's still not fixed, good try though!

Yeah. Issue not resolved.

Where is inforelay.net?

inforelay.net is FA's webhost. They deny the issue being on their end apparently.

Oh nevermind, that outage I just had was really freaking long.
I tried looking to see if perhaps Brighthouse was messing with adult websites or anything but was unable to find anything, so i'm stumped.

I have Brighthouse as well and have been having issues. Wonder if part of it is involved with their side..

bright house here as well. still having issues.

Having issues here too. Brighthouse being my ISP.

its more of TimeWarner Telecom (Brighthouse is part of that service) that seem to have issue, and also seem to be heavy on the people on the east coast having this problem

Sent a note. Issue is not resolved.

I haven't encountered any problems, but it's great of you guys to work so quickly!

Correction...Mac can also use the Network Utillity found in the Utillitys folder :p
Its about time you get your pants fixed. >.>

sent note. issue not fixed.

Had a thought the issues would remain.

yea, still having issues here too

and nothing have changed, still get crashes

Not working yet, sent note.

6 min outage? What about the week long problem that has not been solved? :P

Still having issues. Will send note.

Still having loading problems here, even taking the extra steps to clear the DNS and release/renew, just to make sure. Doing it once a day, but I have faith in you guys, you'll get it all sorted out and fixed. Also, wanted to say that all of the Washington1 IP addresses are working fine here, however, NOW I'm seeing the problem with cr2.iad2 getting 210 and 219ms pings. Never had this issue before until now. =O

Still hardly working I sent a note with what I found.

Hi, I'm here looking for the the fender fursuiter.

haha issue not resolved

what are you guys DOING

What are they doing?
Blaming users and demonstrating that apparently nobody there knows what their firewall/load balancer is or does. And both they and their provider know even less about DNS.

They're also pissing their users the fuck off rn

I can't even edit my page aajsajhsjsdfdlferfehr

http://isfaup.tk/bargraph.html <-- running graph of the last 48 hours (as of around 3:30 MST) of up/downtime as seen by my server. There's certainly a pattern! http://isfaup.tk/ also has a link to that document under the main title.

That seems to be how it's going for me. When it's up or down there, it's the same for me. Verry interesting pattern, that graph.
Thank you for that. It helps some knowing when I'm in the middle of the site's cycles of responsiveness or not.

Still broke:
C:\Users\hatch>tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 1 mas <1 ms <1 ms 192.168.0.1
3 22 ms 21 ms 24 ms hlrn-dsl-gw04.hlrn.qwest.net [207.225.112.4]
4 22 ms 21 ms 21 ms hlrn-agw1.inet.qwest.net [71.217.188.25]
5 55 ms 71 ms 55 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 56 ms 55 ms 55 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]

7 56 ms 55 ms 55 ms cr2-te-0-5-0-3.lay.savvis.net [206.28.97.249]
8 100 ms 100 ms 100 ms 206.28.96.229
9 104 ms 103 ms 102 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.7
0.196.98]
10 101 ms 100 ms 100 ms 204.70.206.137
11 100 ms 100 ms 100 ms dca1.inforelay.net [208.173.12.130]
12 100 ms 106 ms 100 ms cr2.iad3.inforelay.net [67.208.76.5]
13 100 ms 100 ms 100 ms cr2.iad2.inforelay.net [67.208.89.118]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * ^C
C:\Users\hatch>time
The current time is: 17:47:26.79

Here is a traceroute while it's working:

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 <1 ms <1 ms <1 ms 192.168.0.1
3 22 ms 23 ms 26 ms hlrn-dsl-gw04.hlrn.qwest.net [207.225.112.4]
4 21 ms 21 ms 21 ms hlrn-agw1.inet.qwest.net [71.217.188.25]
5 55 ms 55 ms 55 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 55 ms 55 ms 60 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 55 ms 56 ms 55 ms cr2-te-0-5-0-3.lay.savvis.net [206.28.97.249]
8 101 ms 100 ms 100 ms 206.28.96.229
9 104 ms 101 ms 102 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.7
0.196.98]
10 101 ms 100 ms 100 ms 204.70.206.137
11 100 ms 100 ms 100 ms dca1.inforelay.net [208.173.12.130]
12 109 ms 109 ms 100 ms cr2.iad3.inforelay.net [67.208.76.5]
13 101 ms 100 ms 131 ms cr2.iad2.inforelay.net [67.208.89.118]
14 100 ms 100 ms 100 ms 66.231.180.84 <<-- Who is this
15 101 ms 100 ms 100 ms www.furaffinity.net [70.33.186.196]

Trace complete.

STILL having problems, it timed out 7 times in my tracert. This is a joke.

When I saw the word outage, I thought of a Power Outage.

Oh relax, I dont think its anything FA can fix. The cyclic nature of it makes me think its a piece of the routing infrastructure that keeps rebooting endlessly

Ok bud

Vindication bud http://www.furaffinity.net/journal/4782358/

I was going to apologize, but I've been blocked, so, oh well. Its the internet, we move on

The routing infrastructure in question is 66.231.180.84. Which, according to ARIN, is an IP delegated to Ferrox Art LLC. Oh hey, that name looks familiar... just like the copyright at the bottom of every page on FA!

Thanks, why dont you tell someone who can do something about it?

I have as have others, they haven't fixed it.

sooo he had a "fender-bender"?

And here I got excited, yup still having issues..

Well, FurAffinity is an endless cycle of buying new servers and having an outages, so it didn't even come as surprise anymore. Seriously, what's wrong with this site? It always gets some neat hardware upgrades, yet it still has so many problems with outages and all the abandoned updates. Other websites like InkBunny or FurNation for some reason are doing much better despite having a worse hardware and a smaller crew of developers.

still having issues
ran a tracert when site was connecting and another when i was unable to connect
both traces ran up to the hop just before connecting to FA with 13 consecutive timeouts on the non-connecting trace

non-connecting
Tracing route to www.furaffinity.net [xxx]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms modem.Home [xxx]
2 29 ms 23 ms 24 ms xxxqwest.net [xxx]
3 23 ms 49 ms 25 ms xxx [xxx]
4 33 ms 33 ms 32 ms xxx [xxx]
5 39 ms 36 ms 34 ms 208.174.226.229
6 36 ms 35 ms 36 ms xxx [xxx]

7 58 ms 58 ms 58 ms xxx[xxx]
8 60 ms 59 ms 61 ms xxx [xxx]
9 58 ms 58 ms 58 ms 204.70.206.137
10 187 ms 207 ms 198 ms dca1.inforelay.net [xxx]
11 59 ms 58 ms 58 ms cr2.iad3.inforelay.net [xxx]
12 96 ms 202 ms 135 ms cr2.iad2.inforelay.net [xxx]
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * 58 ms www.furaffinity.net [xxx]
Trace complete.

and the connecting trace
Tracing route to www.furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms modem.Home [xxx]
2 23 ms 23 ms 23 ms xxx [xxx]
3 23 ms 50 ms 23 ms xxx [xxx]
4 33 ms 33 ms 33 ms xxx [xxx]
5 33 ms 33 ms 33 ms 208.174.226.229
6 37 ms 36 ms 36 ms xxx [xxx]

7 65 ms 59 ms 58 ms xxx[xxx]
8 60 ms 61 ms 60 ms xxx [xxx]
9 59 ms 58 ms 59 ms 204.70.206.137
10 59 ms 58 ms 59 ms dca1.inforelay.net [xxx]
11 59 ms 58 ms 59 ms cr2.iad3.inforelay.net [xxx]
12 58 ms 59 ms 247 ms cr2.iad2.inforelay.net [xxx]
13 59 ms 58 ms 59 ms 66.231.180.84
14 59 ms 58 ms 58 ms www.furaffinity.net [xxx]

Trace complete.

Still having the same issues here but now they are much longer! I think the problem had gotten worse, sending another tracert your way.

Still having timing out issues. Sent a note a few minutes ago.

its nice to be back finally :P

i have had bad connectivity with my servers in arlington VA using comcast business class
they say they are working on it ... im not sure where the problem lays or what service you guys have but thats whats going on for me
but here in maryland my FA connectivity is perfectly fine ... a little slow but no connectivity issues ... and i use the site allot

From all the tracerts ive run the issue constant result in a problem between ferrox and inforelay. so simple logic would sugest either inforelay is not routing all conections to ferrox, or ferrox is rejecting some connections.

and yes i know thats not an overly technical explanation lol. and ive had tracert running from 2 pcs at the same time to see if there was an ip upstream that was dying severing the conection but both pcs time out at the same point even when the tracerts are started at different times.

Still getting connection issues, but they're not as frequent.

I'm still seeing whatever the problem is.

C:\>tracert 70.33.186.196

Tracing route to www.furaffinity.net [70.33.186.196]
over a maximum of 30 hops:


3 17 ms 19 ms 19 ms ten0-1-0-7.orld17-ser1.bhn.net [72.31.194.152]
4 18 ms 15 ms 18 ms ten0-2-0-7.orld48-car1.bhn.net [72.31.192.136]
5 36 ms 30 ms 38 ms ten0-10-0-5.orld71-car1.bhn.net [71.44.61.40]
6 22 ms 35 ms 34 ms ten0-13-0-0.tamp20-CAR1.bhn.net [71.44.1.208]
7 71 ms 28 ms 25 ms hun0-1-0-0-tamp20-cbr1.bhn.net [72.31.117.158]
8 24 ms 21 ms 23 ms 4.68.70.149
9 55 ms 56 ms 61 ms ae-5-5.ebr1.Miami1.Level3.net [4.69.148.213]
10 60 ms 57 ms 58 ms ae-1-100.ebr2.Miami1.Level3.net [4.69.151.254]
11 64 ms 69 ms 54 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
12 60 ms 59 ms 56 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]

13 50 ms 49 ms 53 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

14 60 ms 69 ms 69 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.1
42]
15 67 ms 225 ms 234 ms ae-42-90.car2.Washington1.Level3.net [4.69.149.1
96]
16 57 ms 53 ms 50 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
17 72 ms 60 ms 57 ms cr2.iad3.inforelay.net [70.33.180.254]
18 61 ms 63 ms 53 ms cr2.iad2.inforelay.net [67.208.89.118]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * 54 ms www.furaffinity.net [70.33.186.196]

Trace complete.

Still locking up at 67.208.89.118

Still timing out. I sent the Tracert results to you.

The tracert program keeps closing the millisecond it completes, so I can't properly save all of the information. x_x

open notepad and paste this into it;

tracert furaffinity.net >> trace.txt

Save it as "trace.BAT", probably to your desktop, then run/open it. It'll close when done, like you've experienced, however, there's now a "trace.txt" document on your desktop (or where ever you saved the .bat file too); this has the trace results in it for you to copy. :)

Or better yet, just run 'cmd' first which should give you a nice console window. Then run 'tracert' in that. You should be able to highlight it and copy the text like any other window.

No, apparently not fixed.

Still broken, see the tracert below:

Not working

C:\Users\Rizu>tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.1.1
2 9 ms 11 ms 26 ms 10.122.160.1
3 12 ms 13 ms 10 ms ten0-7-0-0.orld25-ser2.bhn.net [97.69.192.180]
4 13 ms 13 ms 11 ms ten0-0-0-2.orld31-car2.bhn.net [71.44.61.66]
5 22 ms 23 ms 23 ms ten0-6-0-1.orld71-car2.bhn.net [97.69.194.146]
6 21 ms 22 ms 24 ms ten0-8-0-0.tamp20-CAR2.bhn.net [71.44.1.214]
7 21 ms 22 ms 15 ms 72.31.208.2
8 16 ms 17 ms 17 ms 4.68.70.149
9 42 ms 41 ms 48 ms ae-5-5.ebr1.Miami1.Level3.net [4.69.148.213]
10 42 ms 40 ms 61 ms ae-1-100.ebr2.Miami1.Level3.net [4.69.151.254]
11 46 ms 42 ms 42 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
12 41 ms 43 ms 41 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]

13 41 ms 41 ms 41 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

14 82 ms 54 ms 42 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.1
38]
15 42 ms 41 ms 42 ms ae-32-80.car2.Washington1.Level3.net [4.69.149.1
32]
16 73 ms 53 ms 50 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
17 53 ms 49 ms 48 ms cr2.iad3.inforelay.net [70.33.180.254]
18 143 ms 48 ms 47 ms cr2.iad2.inforelay.net [67.208.89.118]
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * ^C

Working


C:\Users\Rizu>tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 19 ms 9 ms 9 ms 10.122.160.1
3 9 ms 9 ms 9 ms ten0-7-0-0.orld25-ser2.bhn.net [97.69.192.180]
4 15 ms 13 ms 11 ms ten0-0-0-2.orld31-car2.bhn.net [71.44.61.66]
5 20 ms 23 ms 23 ms ten0-6-0-1.orld71-car2.bhn.net [97.69.194.146]
6 21 ms 35 ms 23 ms ten0-8-0-0.tamp20-CAR2.bhn.net [71.44.1.214]
7 17 ms 22 ms 31 ms 72.31.208.2
8 16 ms 15 ms 15 ms 4.68.70.149
9 42 ms 41 ms 42 ms ae-5-5.ebr1.Miami1.Level3.net [4.69.148.213]
10 45 ms 49 ms 49 ms ae-1-100.ebr2.Miami1.Level3.net [4.69.151.254]
11 41 ms 40 ms 51 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
12 41 ms 43 ms 41 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]

13 42 ms 42 ms 40 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

14 46 ms 45 ms 41 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.1
38]
15 44 ms 204 ms 164 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4
]
16 47 ms 48 ms 48 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
17 48 ms 47 ms 47 ms cr2.iad3.inforelay.net [70.33.180.254]
18 54 ms 47 ms 47 ms cr2.iad2.inforelay.net [67.208.89.118]
19 47 ms 47 ms 46 ms 66.231.180.84 (has this device been investigated?!)
20 47 ms 46 ms 47 ms www.furaffinity.net [70.33.186.196]

Trace complete.

Trace Routes accomplished from two different hotel wifi’s in Socorro NM.

Comparison performed between Traces on 17 June and 24 June indicates identical routing from the same Best Western hotel on both days. Differences between Best Western and Holiday Inn (across the parking lot) are marked with an ***.

Note, the same node (66.231.180.84) fails to respond during network outages in every case.

~~~~~~~~~~~~~~~~~~~~~~~~~

**Holiday Inn WiFi Connection, Socorro NM **


Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 5 ms 2 ms 1 ms 192.168.100.1
2 4 ms 5 ms 2 ms 75.160.53.254 ***
3 36 ms 34 ms 34 ms 67.42.200.230
4 39 ms 59 ms 40 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 62 ms 57 ms 57 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 * 59 ms 72 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 60 ms 59 ms 58 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 141 ms 112 ms 113 ms cr1-ten-0-13-1-0.dck.savvis.net [204.70.197.25] ***
9 1068 ms * 114 ms msr1-tengig-0-0-0-0.washington.savvis.net [204.70.196.94] ***
10 136 ms 112 ms 112 ms 204.70.206.77 ***
11 275 ms 137 ms 125 ms dca1.inforelay.net [208.173.12.130]
12 113 ms 146 ms 137 ms cr2.iad3.inforelay.net [67.208.76.5]
13 113 ms 118 ms 116 ms cr2.iad2.inforelay.net [67.208.89.118]
14 156 ms 182 ms 113 ms 66.231.180.84 <<< This node fails during outages
15 111 ms 115 ms 112 ms www.furaffinity.net [70.33.186.196]

Trace complete.


Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 2 ms 1 ms 3 ms 192.168.100.1
2 6 ms 2 ms 9 ms 75.160.53.254 ***
3 37 ms 33 ms 33 ms 67.42.200.230
4 40 ms 49 ms 35 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 58 ms 58 ms 58 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 57 ms * 67 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 72 ms 136 ms 59 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 * 132 ms 115 ms cr1-ten-0-13-1-0.dck.savvis.net [204.70.197.25] ***
9 114 ms 122 ms 122 ms msr1-tengig-0-0-0-0.washington.savvis.net [204.70.196.94] ***
10 111 ms 114 ms 112 ms 204.70.206.77 ***
11 127 ms 114 ms 112 ms dca1.inforelay.net [208.173.12.130]
12 115 ms 111 ms 113 ms cr2.iad3.inforelay.net [67.208.76.5]
13 115 ms 114 ms 112 ms cr2.iad2.inforelay.net [67.208.89.118]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.100.1
2 5 ms 1 ms 1 ms 75.160.53.254 ***
3 34 ms 34 ms 34 ms 67.42.200.230
4 37 ms 36 ms 42 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 61 ms 59 ms 60 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 61 ms 58 ms 58 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 66 ms 61 ms * cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 117 ms 112 ms 117 ms cr1-ten-0-13-1-0.dck.savvis.net [204.70.197.25] ***
9 116 ms 114 ms 114 ms msr1-tengig-0-0-0-0.washington.savvis.net [204.70.196.94] ***
10 112 ms 112 ms 114 ms 204.70.206.77 ***
11 121 ms 115 ms 111 ms dca1.inforelay.net [208.173.12.130]
12 111 ms 110 ms 111 ms cr2.iad3.inforelay.net [67.208.76.5]
13 111 ms 114 ms 135 ms cr2.iad2.inforelay.net [67.208.89.118]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 131 ms 124 ms 125 ms www.furaffinity.net [70.33.186.196]

Trace complete.

** Shifted to Best Western Hotel WiFi, Socorro NM **


Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 3 ms 1 ms 1 ms 192.168.100.1
2 3 ms 3 ms 2 ms 71.39.32.230 ***
3 33 ms 33 ms 34 ms 67.42.200.230
4 36 ms 38 ms 32 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 58 ms 58 ms 57 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 58 ms 75 ms 58 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 57 ms 56 ms 60 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 113 ms 144 ms 129 ms cr2-tengig-0-15-0-0.washington.savvis.net [204.70.196.102] ***
9 113 ms 115 ms 113 ms msr1-tengig-0-3-0-0.washington.savvis.net [204.70.196.98] ***
10 111 ms 112 ms 116 ms 204.70.206.137 ***
11 114 ms 109 ms 117 ms dca1.inforelay.net [208.173.12.130]
12 114 ms 112 ms 110 ms cr2.iad3.inforelay.net [67.208.76.5]
13 111 ms 110 ms 111 ms cr2.iad2.inforelay.net [67.208.89.118]
14 113 ms 111 ms 125 ms 66.231.180. 84 <<< This node fails during outages
15 115 ms 116 ms 116 ms www.furaffinity.net [70.33.186.196]

Trace complete.

C:\Users\es388a>tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.100.1
2 2 ms 1 ms 1 ms 71.39.32.230 ***
3 34 ms 33 ms 32 ms 67.42.200.230
4 34 ms 35 ms 38 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 57 ms 58 ms 79 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 61 ms 56 ms 59 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 64 ms 56 ms 56 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 * 115 ms 113 ms cr2-tengig-0-15-0-0.washington.savvis.net [204.70.196.102] ***
9 118 ms 152 ms 122 ms msr1-tengig-0-3-0-0.washington.savvis.net [204.70.196.98] ***
10 111 ms 114 ms 117 ms 204.70.206.137 ***
11 127 ms 116 ms 122 ms dca1.inforelay.net [208.173.12.130]
12 142 ms 118 ms 112 ms cr2.iad3.inforelay.net [67.208.76.5]
13 112 ms 123 ms 113 ms cr2.iad2.inforelay.net [67.208.89.118]
14 110 ms 112 ms 110 ms 66.231.180. 84 <<< This node fails during outages
15 111 ms 135 ms 113 ms www.furaffinity.net [70.33.186.196]

Trace complete.


Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.100.1
2 2 ms 2 ms 2 ms 71.39.32.230 ***
3 35 ms 40 ms 41 ms 67.42.200.230
4 35 ms 36 ms 44 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 61 ms 58 ms 135 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 72 ms 61 ms 84 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 96 ms 115 ms 98 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 115 ms 140 ms 114 ms cr2-tengig-0-15-0-0.washington.savvis.net [204.70.196.102] ***
9 128 ms 116 ms 114 ms msr1-tengig-0-3-0-0.washington.savvis.net [204.70.196.98] ***
10 130 ms 111 ms 115 ms 204.70.206.137 ***
11 117 ms 111 ms 113 ms dca1.inforelay.net [208.173.12.130]
12 110 ms 115 ms 145 ms cr2.iad3.inforelay.net [67.208.76.5]
13 132 ms 113 ms 114 ms cr2.iad2.inforelay.net [67.208.89.118]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.100.1
2 3 ms 2 ms 3 ms 71.39.32.230 ***
3 40 ms 34 ms 57 ms 67.42.200.230
4 71 ms 50 ms 37 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 59 ms 94 ms 61 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 62 ms 61 ms 104 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 91 ms 75 ms 56 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 113 ms 112 ms 112 ms cr2-tengig-0-15-0-0.washington.savvis.net [204.70.196.102] ***
9 114 ms 116 ms 154 ms msr1-tengig-0-3-0-0.washington.savvis.net [204.70.196.98] ***
10 113 ms 144 ms 110 ms 204.70.206.137 ***
11 153 ms 213 ms 142 ms dca1.inforelay.net [208.173.12.130]
12 131 ms 148 ms 135 ms cr2.iad3.inforelay.net [67.208.76.5]
13 110 ms 113 ms 117 ms cr2.iad2.inforelay.net [67.208.89.118]
14 115 ms 136 ms 137 ms 66.231.180. 84 <<< This node fails during outages
15 114 ms 160 ms 136 ms www.furaffinity.net [70.33.186.196]

Trace complete.


Tracing route to furaffinity.net [70.33.186.196] over a maximum of 30 hops:

1 12 ms 2 ms 2 ms 192.168.100.1
2 2 ms 2 ms 2 ms 71.39.32.230 ***
3 76 ms 36 ms 38 ms 67.42.200.230
4 54 ms 45 ms 39 ms albq-agw1.inet.qwest.net [71.222.249.41]
5 65 ms 63 ms 68 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 58 ms * 58 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
7 78 ms 64 ms 62 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
8 114 ms 142 ms 115 ms cr2-tengig-0-15-0-0.washington.savvis.net [204.70.196.102] ***
9 116 ms 116 ms 118 ms msr1-tengig-0-3-0-0.washington.savvis.net [204.70.196.98] ***
10 117 ms 116 ms 114 ms 204.70.206.137 ***
11 116 ms 118 ms 115 ms dca1.inforelay.net [208.173.12.130]
12 114 ms 111 ms 117 ms cr2.iad3.inforelay.net [67.208.76.5]
13 115 ms 114 ms 115 ms cr2.iad2.inforelay.net [67.208.89.118]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * 113 ms www.furaffinity.net [70.33.186.196]

Hope i dont jinx myself here, but im not having any FA issues :L
Good luck FA stuff ;3;

Still acting up on my end. Note sent with tracert info.

Still acting on my connection. Wireless it craps out a lot, but on a wired connection it works more or less fine.

It's getting worse. gg

Haven't encountered any issues beyond gifs in my gallery being hard to click, not the end of the world. Thanks for the update and good luck with the finding the source of the problems! :>

Mine's still broke.

SIGH.

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Users\Morticia>tracert www.furaffinity.net

Tracing route to www.furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 119 ms 3 ms 4 ms 10.5.2.1
2 * * * Request timed out.
3 13 ms 14 ms 14 ms ae5-658.edge3.NewYork1.Level3.net [4.28.75.121]

4 19 ms 23 ms 20 ms vlan90.csw4.NewYork1.Level3.net [4.69.155.254]
5 18 ms 19 ms 18 ms ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]

6 18 ms 20 ms 18 ms 4.69.201.46
7 55 ms 19 ms 19 ms 4.69.201.93
8 26 ms 22 ms 18 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
46]
9 19 ms 19 ms 20 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4
]
10 22 ms 20 ms 20 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
11 24 ms 19 ms 21 ms cr2.iad3.inforelay.net [70.33.180.254]
12 19 ms 20 ms 21 ms cr2.iad2.inforelay.net [67.208.89.118]
13 20 ms 23 ms 22 ms 66.231.180.84
14 20 ms 27 ms 23 ms www.furaffinity.net [70.33.186.196]

Trace complete.

Still cutting in and out on both wired and wireless connections. Ping tests fail and no data packets are sent; it's like it going off and on every 5 to 10 minutes. Why the hell is this happening?

bash$ tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 4 ms 9 ms 9 ms 0x.no [215.0.0.2]
2 48 ms 49 ms 49 ms tcso-dsl-gw27.tcso.qwest.net [75.160.240.27]
3 48 ms 49 ms 39 ms tcso-agw1.inet.qwest.net [75.160.241.209]
4 58 ms 59 ms 89 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
5 58 ms 59 ms 59 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
6 58 ms 59 ms 59 ms cr1-tengig-0-5-0-0.lay.savvis.net [204.70.198.5]
7 168 ms 139 ms 119 ms cr2-tengig-0-15-0-0.Washington.savvis.net [204.70.196.102]
8 118 ms 119 ms 149 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.70.196.98]
9 118 ms 119 ms 119 ms er1-gig-3-0-1.dck.savvis.net [204.70.203.6]
10 118 ms 119 ms 149 ms dca1.inforelay.net [208.173.12.130]
11 119 ms 119 ms 119 ms cr2.iad3.inforelay.net [67.208.76.5]
12 118 ms 119 ms 119 ms cr2.iad2.inforelay.net [67.208.89.118]
13 * * * Request timed out.
14 * * * Request timed out.
15 122 ms 119 ms 119 ms www.furaffinity.net [70.33.186.196]

Trace complete.
bash$ tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 2 ms 9 ms 9 ms 0x.no [215.0.0.2]
2 48 ms 49 ms 49 ms tcso-dsl-gw27.tcso.qwest.net [75.160.240.27]
3 48 ms 48 ms 49 ms tcso-agw1.inet.qwest.net [75.160.241.209]
4 67 ms 59 ms 59 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
5 58 ms 99 ms 59 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]
6 57 ms 59 ms 59 ms cr1-tengig-0-5-0-0.lay.savvis.net [204.70.198.5]
7 129 ms 119 ms 119 ms cr2-tengig-0-15-0-0.Washington.savvis.net [204.70.196.102]
8 119 ms 119 ms 129 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.70.196.98]
9 118 ms 119 ms 119 ms er1-gig-3-0-1.dck.savvis.net [204.70.203.6]
10 118 ms 119 ms 119 ms dca1.inforelay.net [208.173.12.130]
11 118 ms 119 ms 119 ms cr2.iad3.inforelay.net [67.208.76.5]
12 118 ms 119 ms 119 ms cr2.iad2.inforelay.net [67.208.89.118]
13 118 ms 129 ms 119 ms 66.231.180.84
14 118 ms 119 ms 119 ms www.furaffinity.net [70.33.186.196]

Trace complete.



I started the first when it wasn't working.
66.231.180.84 -THIS POINT RIGHT HERE ISN'T WORKING CORRECTLY, THIS IS THE POINT OF FAILURE.
This has been the failure point since the problem started.
Use MY host, and constantly run a ping on it, kacey.0x.no. When/if the ping times out, do a traceroute back.

bash$ nmap -O -PN 66.231.180.84

Starting Nmap 5.21 ( http://nmap.org ) at 2013-06-25 00:15 US Mountain Standard
Time
Nmap scan report for 66.231.180.84
Host is up (0.12s latency).
Not shown: 994 closed ports
PORT STATE SERVICE
22/tcp filtered ssh
23/tcp filtered telnet
25/tcp filtered smtp
80/tcp filtered http
443/tcp filtered https
1720/tcp filtered H.323/Q.931
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Device type: router|switch
Running: Cisco IOS 12.X
OS details: Cisco 2821, 6506, or 7206VXR router (IOS 12.2), Cisco 3750 switch (IOS 12.2), Cisco Catalyst 2960 or 3600 switch

OS detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 8.17 seconds


LISTEN TO THE PEOPLE TELLING YOU WHAT IS WRONG. IT ISN'T DNS, IT IS ROUTING. WE HAVE PINPOINTED THE FAILURE AND WE GET NO RESPONSE OR ACKNOWLEDGEMENT. YOU ASKED FOR HELP AND YOU BLOW ALL OF US OFF WHO ARE TRYING TO HELP YOU.

http://whois.domaintools.com/66.231.180.84
http://geoip.flagfox.net/?ip=66.231.....=66.231.180.84
http://en.wikifur.com/wiki/Ferrox_%28software%29
http://en.wikifur.com/wiki/Dragoneer
You can't bullshit me that it's not on your side. I do believe all the evidence points to your ownership of the system at fault here.

so much this

^ yep. this

Yay, welcome back up! I also briefly mis-read the title as Mini-Outrage which was the only reason I clicked on this.

its an outrage for us affected ._.

Seems to be working in five minut spurts only to have it cut out and works again five minutes later. This is getting weird. Both on wired and wireless connections, and I'm on a apartment complex network, so I can't mess with the router or model settings (the admin is an IT "specialist") Maybe your host just likes to troll or something.

C:\users\the_randomizer tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms 192.168.1.1
2 <1 ms <1 ms <1 ms 66.7.119.1
3 5 ms <1 ms <1 ms 10.8.201.37
4 2 ms <1 ms <1 ms eth_3-3_prv02-rt02.veracitynetworks.com[97.75.190.166]
5 1 ms <1 ms 1 ms 97.75.191.66
6 1 ms 2 ms 6 ms 97.75.191.54
7 130 ms 7 ms 3 ms te=9-3.car1.SaltLakeCity1.Level3.net [4.53.40.105]
8 53 ms 53 ms 53 ms ae-11-11.car2.SaltLakeCity.Level3.net [4.69.133.122]
9 52 ms 54 ms 53 ms ae-5-5.ebr1.Denter1.Level3.net [4.69.133.126]
10 52 ms 52 ms 52 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.151.182]
11 52 ms 52 ms 52 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.133.132.62]
12 52 ms 52 ms 53 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.133.132.114]
13 52 ms 52 ms 52 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145]
14 53 ms 53 ms 53 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
15 52 ms 52 ms 53 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
16 52 ms 52 ms 53 ms ae-32-82.car2.Washington1.Level3.net [4.69.149.132]
17 54 ms 54 ms 54 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.58]
18 58 ms 57 ms 57 ms cr2.iad3.inforelay.net [70.33.180.254]
19 57 ms 57 ms 57 ms cr2.iad3.inforelay.net [67.208.89.118]
20 56 ms 56 ms 56 ms 66.231.180.84
21 56 ms 56 ms 56 ms www.furaffinity.net [70.33.186.196]

Trace complete

A bunch of people pointed out in the other journals that the 66.231.180.84 IP belongs to Ferrox Art LLC and is some sort of weird firewall/routing thingy that's messing up.

Mines been shitty since last November.

Mine's still broke as well :(

still does it but do I GOT to do that thingy cause I wanna reamain..."down low"

theyre too lazy to do that :p i told them twice now to do it, they outright ignore it... >.>

Now about that new FA UI...

ARE WE THERE YET?

they needed 2 years for the ALPHA - yes i dont consider it beta. give it another 2 for something usable. xD

Totally pressed the reset button. So the problem isisn't on fA's end. Reset button fixes everything.

If you're talking about the router's reset button basically all of us have tried that so no, it isn't that, maybe that's what was going on for you but that is not what is causing everyone else's issue here.

>_> Naa not talkin bout that. fA pressed the reset button because in their world it fixes everything. I'm in the UK and have had no issues connecting. Like peoples are saying.

x.x my phone mistyped my original its should have been "isnt" . Enough people have screamed at them about what the problem is =/ but that isnt good enough for them.

I've only been on FA for a year now and it definitely seems like they have some trouble listening for sure

You have no idea....the scariest thing I have enountered is the Unencyclopedia Dramatica page once you get past the nasty image. It doesnt troll, it actually just states whats happend on fA... Afterall we were promised (for the millionth time) a new user interface but that hasnt appeared either =/
Its a shame people are begging and desperite to help out with coding and running but they wont let anyone.
By the way :3 if you are running firefox, get yourself the "tilt" addon for firefox and see how amazing fA looks in 3d....tables...TABLES EVERYWHERE!!!

Oh yeah, well for the most part unencyclopedia dramatica was run by a completely biased, angry, aggressively prejudice group of people and I don't really think anyone should take what they write in there too much to heart. While part of what happened was true, a lot of it was grossly blown out of proportion.

Thanks! But unfortunately I am not able to see 3D anything
I can only see in 2D so I don't even have real-life depth perception, I tried to see the 3DS thing and it doesn't look any different to me, it just looks blurry and hurts my eyes haha...

You can see it, they call it 3d because it lets you see a web page from different angles and all its tables stacked ontop of each other.
I agree that alot of UD is like that but its creepy how un angry the fA page is, otehr furry pages are but it brings forth a lot of stuff that gets swept under the carpet like the most recent admins that left..

Well I'll try it and see what you mean then.

Yeah I'm not saying things they were stating were untrue or anything. There was even a recent issue with someone else on the site, I don't really approve of all that goes on but honestly you can find problems like that on any site, they just haven't been so horribly leaked as here. I just stay as far away from it as possible myself.

Nope...a reset button enver fixes everything, especially not in a server farm - it actually can make things worse o-o
Also, cute avvie :3

But fA logic.... D= The big red reset button!!!

Oh wait, now i got it!! xD ahahah! LIKE. *hug* ^^ (hope you dont mind random hugs o-o)

*hugs back* don't worry I'm a hugger lol.

Here's how it looks when it's working (granted you guys have seen enough of these):

Tracing route to www.furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 24 ms 23 ms 24 ms phnx-dsl-gw68.phnx.qwest.net [67.40.227.68]
3 123 ms 126 ms 87 ms phnx-agw1.inet.qwest.net [75.160.238.25]
4 35 ms 35 ms 34 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
5 34 ms 34 ms 34 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]

6 34 ms 34 ms 34 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
7 102 ms 102 ms 102 ms cr2-tengig-0-15-0-0.Washington.savvis.net [204.7
0.196.102]
8 108 ms 107 ms 107 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.7
0.196.98]
9 102 ms 102 ms 102 ms 204.70.206.77
10 102 ms 102 ms 102 ms dca1.inforelay.net [208.173.12.130]
11 101 ms 101 ms 101 ms cr2.iad3.inforelay.net [67.208.76.5]
12 197 ms 206 ms 200 ms cr2.iad2.inforelay.net [67.208.89.118]
13 103 ms 102 ms 102 ms 66.231.180.84
14 103 ms 102 ms 102 ms www.furaffinity.net [70.33.186.196]

Trace complete.


And here's how it looks otherwise:

Tracing route to www.furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 24 ms 23 ms 24 ms phnx-dsl-gw68.phnx.qwest.net [67.40.227.68]
3 123 ms 126 ms 87 ms phnx-agw1.inet.qwest.net [75.160.238.25]
4 35 ms 35 ms 34 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
5 34 ms 34 ms 34 ms 63-235-40-86.dia.static.qwest.net [63.235.40.86]

6 34 ms 34 ms 34 ms cr1-te-0-5-0-3.lay.savvis.net [206.28.97.245]
7 102 ms 102 ms 102 ms cr2-tengig-0-15-0-0.Washington.savvis.net [204.7
0.196.102]
8 108 ms 107 ms 107 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.7
0.196.98]
9 102 ms 102 ms 102 ms 204.70.206.77
10 102 ms 102 ms 102 ms dca1.inforelay.net [208.173.12.130]
11 101 ms 101 ms 101 ms cr2.iad3.inforelay.net [67.208.76.5]
12 197 ms 206 ms 200 ms cr2.iad2.inforelay.net [67.208.89.118]
13 103 ms 102 ms 102 ms 66.231.180.84
14 103 ms 102 ms 102 ms www.furaffinity.net [70.33.186.196]

Trace complete.

By the way, the reason for the first hop being strange is because I've got a weird router setup. That has nothing to do with the issues since I'm pretty sure other people don't have the same shitty Actiontec pile that Qwest/Centurylink provide unless they lived here around 2010.

Mines is still acting up! One moment its fine then all of a sudden it says:

Oops! Google Chrome could not connect to www.furaffinity.net
Suggestions:
Access a cached copy of www.­furaffinity.­net/­user/­blackxuo/­
Try reloading: www.­furaffinity.­net/­user/­blackxuo/­
Search on Google:

. Blah blah. -_-
And it seems I am not the only one still having issues. I have no idea what's going on but I really hope this gets resolved soon...

im still having time outs on anything i do took me 30 mins to get to this journal. :/ im computer stupid so i cant do what ever it is you want in the journal i can list what i was doing when i got the time outs

first i clicked on comments and journals took 10 mins to get to it with 3 time out errors

second i tryed submissions constant time out errors still cant view them

third i tryed to even load my own page took 40 mins with 5 time out errors

fourth i tryed to load this page and took 30 mins with 4 time out errors.

Still having conetivity issues if this keeps up won't be able to use FA anymore sadly ..

This asininity on their end has got to stop

I'm still having intermittent issues as well. While I could see it being a problem on my ISP's side (CenturyLink) the location of the packet loss is much closer to your end then mine. It doesn't appear to be DNS related, as the IP I'm getting is the same. Here's the failing traceroute:

root@router:~# traceroute -I furaffinity.net
traceroute to furaffinity.net (70.33.186.196), 30 hops max, 60 byte packets
1 hlrn-dsl-gw05.hlrn.qwest.net (207.225.112.5) 21.025 ms 21.212 ms 21.517 ms
2 hlrn-agw1.inet.qwest.net (71.217.188.33) 34.015 ms 34.009 ms 34.002 ms
3 lap-brdr-03.inet.qwest.net (67.14.22.78) 55.947 ms 55.940 ms 56.450 ms
4 63-235-40-86.dia.static.qwest.net (63.235.40.86) 56.180 ms 56.420 ms 56.655 ms
5 cr1-te-0-5-0-3.lay.savvis.net (206.28.97.245) 57.223 ms 57.426 ms 57.419 ms
6 cr1-ten-0-13-1-0.dck.savvis.net (204.70.197.25) 101.659 ms 99.334 ms 99.226 ms
7 msr1-tengig-0-0-0-0.Washington.savvis.net (204.70.196.94) 101.649 ms 101.603 ms 101.566 ms
8 er1-gig-3-0-1.dck.savvis.net (204.70.203.6) 100.280 ms 99.808 ms 99.769 ms
9 dca1.inforelay.net (208.173.12.130) 100.282 ms 100.479 ms 100.082 ms
10 cr2.iad3.inforelay.net (67.208.76.5) 100.755 ms 100.282 ms 100.261 ms
11 cr2.iad2.inforelay.net (67.208.89.118) 100.229 ms 100.054 ms 99.891 ms
12 * * *
13 * * *
14 * * *
15 * * *


The problem host for everyone seems to be 66.231.180.84. Whose machine that is though, I have no idea.

For reference, here's a working traceroute:

root@router:~# traceroute -I furaffinity.net
traceroute to furaffinity.net (70.33.186.196), 30 hops max, 60 byte packets
1 hlrn-dsl-gw05.hlrn.qwest.net (207.225.112.5) 20.926 ms 21.155 ms 21.086 ms
2 hlrn-agw1.inet.qwest.net (71.217.188.33) 21.069 ms 21.508 ms 21.513 ms
3 lap-brdr-03.inet.qwest.net (67.14.22.78) 56.248 ms 56.242 ms 56.244 ms
4 63-235-40-86.dia.static.qwest.net (63.235.40.86) 56.551 ms 56.544 ms 56.536 ms
5 cr1-te-0-5-0-3.lay.savvis.net (206.28.97.245) 57.179 ms 57.185 ms 57.409 ms
6 cr1-ten-0-13-1-0.dck.savvis.net (204.70.197.25) 101.713 ms 99.667 ms 99.630 ms
7 msr1-tengig-0-0-0-0.Washington.savvis.net (204.70.196.94) 101.860 ms 101.446 ms 101.413 ms
8 er1-gig-3-0-1.dck.savvis.net (204.70.203.6) 100.064 ms 99.564 ms 99.756 ms
9 dca1.inforelay.net (208.173.12.130) 100.205 ms 99.963 ms 100.443 ms
10 cr2.iad3.inforelay.net (67.208.76.5) 100.420 ms 99.971 ms 100.194 ms
11 cr2.iad2.inforelay.net (67.208.89.118) 107.163 ms 101.201 ms 99.904 ms
12 66.231.180.84 (66.231.180.84) 100.618 ms 100.152 ms 99.993 ms
13 www.furaffinity.net (70.33.186.196) 99.718 ms 99.547 ms 99.692 ms

It does feel a little bit like a flapping path (up for 5 minutes, down for 5 minutes, repeat). I am seeing occasional error pages with a tan background and red text, but it never loads fully. Unfortunately the one time I had text I forgot to take a screenshot. :P

Btw, both FA itself and 66.231.180.84 (as well as the two hops in front of it) are all in Inforelay IP blocks. The problem definitely seems to be on your providers side, unless that second to last hop is your load balancer.

And how is this to be resolved? The site works fine on my parent's connection. We need better hosts who aren't being jerks about IP blocking crap.

Someone on their side will need to look at it. If it was an IP block I shouldn't be able to access the site at all, ever. Since it's bouncing up and down that suggests something is either picking the wrong path intermittently, or there's a load balancer trying to balance to a non-existant IP. It could of course still be something even weirder that's wrong (bad cable, failing switch, etc).

Also, one more note: Right before the site goes down I see a couple ICMP type 3 code 13 returns (Communication administratively prohibited) from 66.231.180.84. Then it starts dropping traffic entirely.

I hope they can fix this so it no longer is so sporadic. It's making it near-impossible for me to submit picture....stupid host servers

Still having problems. Had problems when posting this.

C:\Users\PC>tracert furaffinity.net

Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 3 ms 148 ms 2 ms 192.168.6.1
2 2 ms 5 ms 1 ms 66.7.119.1
3 2 ms 2 ms 3 ms 10.8.201.37
4 5 ms 2 ms 2 ms eth_3-3_prv02-rt02.veracitynetworks.com [97.75.190.166]
5 3 ms 4 ms 13 ms 97.75.191.66
6 3 ms 3 ms 3 ms 97.75.191.54
7 3 ms 4 ms 3 ms te-9-3.car1.SaltLakeCity1.Level3.net [4.53.40.105]
8 56 ms 55 ms 54 ms ae-11-11.car2.SaltLakeCity1.Level3.net [4.69.133.122]
9 54 ms 55 ms 54 ms ae-5-5.ebr1.Denver1.Level3.net [4.69.133.126]
10 54 ms 56 ms 60 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.151.182]
11 55 ms 55 ms 54 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
12 54 ms 54 ms 55 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
13 53 ms 55 ms 53 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145]
14 55 ms 55 ms 54 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
15 54 ms 54 ms 55 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
16 54 ms 55 ms 54 ms ae-32-80.car2.Washington1.Level3.net [4.69.149.132]
17 143 ms 95 ms 145 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.58]
18 58 ms 61 ms 59 ms cr2.iad3.inforelay.net [70.33.180.254]
19 166 ms 205 ms 132 ms cr2.iad2.inforelay.net [67.208.89.118]
20 68 ms 57 ms 58 ms 66.231.180.84
21 ^C

While down, from an Earthlink connection:

1 ms 1 ms 1 ms 192.168.1.1
8 ms 8 ms 8 ms user-11fa401.dsl.mindspring.com [66.245.16.1]
8 ms 8 ms 9 ms cor02-vl-10.ca-sanfranc0.ne.earthlink.net [209.165.103.65]
8 ms 8 ms 8 ms bor01-ge-6-1.ca-sanfranc0.ne.earthlink.net [209.165.103.17]
9 ms 8 ms 8 ms ge-6-4.car2.SanFrancisco1.Level3.net [4.71.44.1]
0 ms 9 ms 10 ms ae-2-4.bar2.SanFrancisco1.Level3.net [4.69.133.158]
3 ms 82 ms 83 ms ae-6-6.ebr2.SanJose1.Level3.net [4.69.140.154]
2 ms 82 ms 83 ms ae-82-82.csw3.SanJose1.Level3.net [4.69.153.26]
3 ms 83 ms 83 ms ae-81-81.ebr1.SanJose1.Level3.net [4.69.153.9]
3 ms 83 ms 82 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
3 ms 83 ms 83 ms ae-46-46.ebr2.NewYork2.Level3.net [4.69.201.30]
9 ms 83 ms 83 ms ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253]
3 ms 83 ms 83 ms 4.69.201.89
3 ms 83 ms 83 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
9 ms 129 ms 96 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4]
4 ms 85 ms 83 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.58]
4 ms 84 ms 84 ms cr2.iad3.inforelay.net [70.33.180.254]
4 ms 84 ms 84 ms cr2.iad2.inforelay.net [67.208.89.118]
* * * Request timed out.
* * * Request timed out.
* * * Request timed out.

while up:
1 ms 192.168.1.1
8 ms user-11fa401.dsl.mindspring.com [66.245.16.1]
8 ms cor02-vl-10.ca-sanfranc0.ne.earthlink.net [209.165.103.65]
9 ms bor01-ge-6-1.ca-sanfranc0.ne.earthlink.net [209.165.103.17]
9 ms ge-6-4.car2.SanFrancisco1.Level3.net [4.71.44.1]
9 ms ae-2-4.bar2.SanFrancisco1.Level3.net [4.69.133.158]
82 ms ae-6-6.ebr2.SanJose1.Level3.net [4.69.140.154]
82 ms ae-82-82.csw3.SanJose1.Level3.net [4.69.153.26]
83 ms ae-81-81.ebr1.SanJose1.Level3.net [4.69.153.9]
83 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
83 ms ae-46-46.ebr2.NewYork2.Level3.net [4.69.201.30]
83 ms ae-1-100.ebr1.NewYork2.Level3.net [4.69.135.253]
83 ms 4.69.201.89
91 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.146]
94 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4]
83 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.58]
84 ms cr2.iad3.inforelay.net [70.33.180.254]
58 ms cr2.iad2.inforelay.net [67.208.89.118]
84 ms 66.231.180.84
83 ms www.furaffinity.net [70.33.186.196]

Leave it to higher ups for not giving a flying f**k about its users

I am still having sporadic connection issues, though it is a bit faster then it was before. I'm not to sure about trying some of the suggestions at the top, since I'm usually careful with my computer.

All you're doing is running connection tests from the command prompt. You're not doing anything dangerous.

But I'll still keep watching for any changes.

im still having this issue its been over a week now for me and on more then one computer and different browsers
i hope your staff gets it figured out id hate to leave fa because this problem with the servers continues :(
95% of the time i cant use the site

It's on and off every 5-10 minutes, and they'd damn well better fix this

i know id hate to have to abandon the site cause they cant fix a server problem

nearly 2 weeks now still canmt connect half the time on my cellphone connection with Verizon or my home with Brighthouse. this is really kind of out of hand. *gives you a book on How not to be a crappy host or choose crappy providers*

They can't help it, their IT department doesn't have the balls to do anything right

Seriously, don't use a host that sucks balls. Use a host that isn't run by idiots, please.

Tracing route to www.furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 113 ms 51 ms 78 ms ten9-0-1.bham10-ser1.bhn.net [72.31.206.159]
4 107 ms 121 ms 113 ms ten8-0-0.bham01-ser3.bhn.net [72.31.206.140]
5 163 ms 89 ms 137 ms 72-31-206-219.net.bhntampa.com [72.31.206.219]
6 132 ms 167 ms 111 ms ten0-9-0-4.orld71-cbr3.bhn.net [72.31.220.16]
7 150 ms 160 ms 124 ms 4.68.70.153
8 170 ms 139 ms 159 ms ae-8-8.ebr1.Atlanta2.Level3.net [4.69.137.150]
9 112 ms 169 ms 164 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]

10 126 ms 151 ms 177 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

11 178 ms 145 ms 141 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
12 179 ms 154 ms 183 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4
]
13 378 ms 202 ms 206 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
14 166 ms 141 ms 177 ms cr2.iad3.inforelay.net [70.33.180.254]
15 163 ms 162 ms 152 ms cr2.iad2.inforelay.net [67.208.89.118]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

For hell's sake this is getting out of hand. I can only post my trace info so many times, but it kicks in for five minutes then cuts out for five minutes. Hire an effing competent IT team and maybe this issue would be fixed by now.

Either your load balancing service sucks balls or level3 which I also think sucks donkey cock.

I dare say inforelay.net is shit. Even their main site doesn't load quickly.

Time to go shopping for a proper data center collocation.

Yes, either use a better host or well, stop using a crappy host. Inforelay.net needs to sod off

Northern Virginia... Nice same shitty dc that amazon ec2 uses and fails every 3 months?

Dear furafinity: If artists could have folder option to organise art, that be great
Also for disabling shouts option in your profile, that be really great too

Okay, the downtime seems to be getting shorter. It still cuts out, but not as long this time.