What is with the whole thing when I browse someone's gallery, click an image and then when I get press backwards it shows a warning thing... does that have to do with FA or firefox? Because it happened once before looong ago. But have been since for years until now!

Document Expired
This document is no longer available.
The requested document is not available in Firefox's cache.

That's what it says

This, specifically, also happens when you connect to FA via https. In addition to what the below commenters said about POSTs versus GETs, I assume it is a security measure of some sort to not allow you to back up to a secure page that sent POST data. Web development is not my forte, however, so that's just speculation.

As a quick fix, you can always connect to FA via plain old http. Just go up to your address bar and take the "s" out of https://www.furaffinity[...]

Now granted, in the interest of full disclosure, that is changing your connection so that it is not encrypted (hidden) between your computer and FA's servers, and the data can be more easily intercepted and read by an interested third party. However, given the nature of the site, it's my personal opinion that a secure connection is overkill.

Shows a warning thing? Only time I can think of that happening is via the Search page.

It does also happen on the search page, but also on galleries..

That's because the gallery view is basically a search that only looks at that person's gallery.

It does it on galleries for me as well. Search and browse as well.

It's because FA's search page uses a HTTP "Post" request to handle the "go to next page of search results" request.

The HTTP spec says "use a POST request if the request will change data, use a GET request if it retrieves it", so most web browsers warn you if you use the back button to get to a page which was the result of a POST request. The idea being that you might accidentally create a second database record, put an online banking transaction through twice or something similarly catastrophic.

TL/DR: it's a quirk in the way FA handles search pages.

I know. I'm just saying is all. I don't think it's actually supposed to happen on galleries.

yeah, the back button doesn't work because it has nothing to go back to, you weren't actually on another page technically. say you were on http://blahblahblah/3, and you push back, it's gonna load http://blahblahblah/2, but it doesn't remember what was on page 2 because it' different now and it's like "omg what happened" but if you click the resend information button it works itself out

or, I could have no idea what I'm saying and this could be false

It's a bit faster now for me, but sometimes pages still take upwards of 2 minutes to load. Specifically loading the main notes page, and my faves/watchers/comments inbox. Other pages do as well, but not as often as those two.

Well, this won't help with the speed (that's another thing, and that's coming soon). This is to help with those who can't connect to the site reliably.

I would assume it does, as often it just craps out and won't load at all. I often just close the page, but times I have left it to load it craps out and I get a 500 error.

Well it's still the same when I look around and post comments, well a little slow but okay.

Once again, I'm going to point out the problem with you saying "please submit new traceroutes via note" when addressing site users who can't make comments, browse, post journals, or send notes using FA. You do see an inherent flaw in your logic, don't you?

The connectivity issues do not completely prevent people from getting on the site. We know it's rough, but we're trying to get it resolved.

The first journal about tracing, I tried for over 45 minutes to note my trace results before flipping a table and walking away.

Rough is a slight understatment. :P

I know it's frustrating, but we're working on it. The more evidence we have the better.

Aye aye, cap'n! *salutes*

Why not set up an email address for these fault reports, then close it down after things are resolved? Seems that'd neatly sidestep the problem of not being able to get to the site for long enough to send a note...

I agree, this sounds a lot easier for the users.

Exactly what I was gonna say x-x Seems like it'd be much easier

Our service is ''Clear'' I don't think its a very big name internet service...

Well I use it too!
It might be sprint being a jerk!

I think its one of the worst isp out there!

Clear4g is great, but only when your in a good area since it works like a cellphone... But to send out wireless connection to wi-fi devices.

I use Clear as well (Western US) and I have no problem. I've been hearing issues from people over on the east coast about connecting to certain sites (even Weather.com) on the Eastern seaboard, so location may be it as well (Don't need to add that to the traceroute, as that is included in that).

Well, someone weird happened when I tried the tracert on my Windows PC, even with the site working it times out on the second hop. Not sure if that really helps, but I'll get a traceroute from my linux pc sent in.

I wish the Admins of this site the best of luck in solving this problem.

I'm using Century Link as my ISP right now, and so far none of the troubleshooting efforts have completely resolved the issue. However, I have noticed that my time between lack of connection and connection has decreased somewhat. It definitely is still very touch and go.

Same thing for me. Heck, I don't even know if this reply will even post!

problems were on the isp's side, connections were fuzzy or down for many states.

they wont really explain what happened though, so that's all i know,

We have our suspisions about what happened, but we're not 100%. We're working with our host to try to narrow down the what/where/why.

well, the internet is very fragile, wouldn't doubt it would happen again.

I know Linux users can do traceroute without instructions but for sure, here's instructions for Linux(Ubuntu since it's the most popular distro) since they're missing.

1) Open the terminal by pressing Ctrl+Alt+T
2) Type sudo apt-get install traceroute and hit Enter in order to install traceroute(yes, it isn't installed by default)
3) Type traceroute www.furaffinity.net and hit Enter.
4) Copy/paste the results in a note to Fender.

I didn't post Linux instructions because I kind of expect people on Linux to know how to traceroute in the first place. =P

What about android uses? I'me sure I am not the only one that uses a android device once in a while to use this site.

This is one of the few times things have gone wrong and I'm actually unaffected. Other than a bit of lag here or there, I can connect to FA just fine. I'm not sure how much it helps to hear from people NOT having problems, but I'm on Comcast and I haven't seen anyone else say they're having trouble and are also on comcast, yet.

Also have Comcast and no issues.

[High five!]

i know that i'm using Verizon internet and both firefox and chrome, and haven't had any issues with it *knock on wood* totally not helpful for those who DO have outages, but just putting my two cents in for process of elimination or something

Its still giving me error 504 about 75% of the time...my computer is down right now so I'm using my Android phone with Dolphin browser if that helps at all...

504 error is unrelated. That's due to running out of resources and the system hiccups. Once the new servers go live in a few days that should take care of that problem instantly.

What about on mobile devices? For some reason, it now seems to be fine on my desktop, but has periods of derpload on my phone.

If you have a way to traceroute from your phone you can run those tools and send them to us, too. But most phones don't have that built in.

Rooted Android with a Terminal Emulator app:
Type in
1. su
2. traceroute
and copy and paste the results to Fender.

I don't root. XD Especially since my current phone is only three months old on a new contract.

I rooted my S3 a week after I got it, but to each their own!

There's a few traceroute apps in the google play store. I got the one by srcguardian and can verify that it works

I've a slightly different issue. Lately I've been getting an error saying that my file name is too long whenever I try to upload something. For example, I wanted to update both my Profile ID and Avatar, the images for such are the proper pixel dimensions. They wont upload. Secondly, I wanted to upload an updated fetish list (for this year) to my Scraps, again the same error message about the filename being too long. Is this issue due to the fact I'm accessing this site through a proxy?

How many characters are in the filename you're tryig to upload?

Answer:

24 characters for the rtf document (fetish list)

11 characters for the profile ID pic

9 characters for the new avatar


Additonal Info:

The dimensions for the avatar is: 186x217

The dimensions for the ID is:
386x224

The file size for the rtf document is: 35.0KB

Am I doing something wrong?

Can you send me a note with a link to your submission you're trying to update so I can investigate it later?

Will do, thank you :)

I've had issues where only when I try to submit a comment or something it will take forever to load... and then chrome says that page loadout failed or something :I let's hope things get better soon

I have no problems at all with FA since June 20 other than the slow as dial up speed at times, but I am used to that now from this site.

If you actually check prior posts, I've sent over literal stacks upon stacks of information. Stop making excuses and asking for pointless, useless, non-helpful information like what ISP and what food we're eating.

It's very clearly your firewall. It has been your firewall the whole time. The issue is your equipment or software and I've shown this time and time and time again. The problem is 66.231.180.84. I cannot say it any more clearly than that.

--- mtr run 1
4.|-- ge-6-20.car1.Cleveland1.L 0.0% 20 11.3 73.8 11.3 212.7 70.2
5.|-- ae-2-4.bar1.Cleveland1.Le 0.0% 20 11.3 28.8 10.4 57.6 15.2
6.|-- ae-6-6.ebr1.Washington1.L 0.0% 20 38.9 31.5 19.7 58.0 12.7
7.|-- ae-81-81.csw3.Washington1 0.0% 20 21.3 32.8 19.0 60.2 13.9
8.|-- ae-32-80.car2.Washington1 0.0% 20 20.6 105.3 18.7 256.6 89.9
9.|-- CWIE-LLC.car2.Washington1 0.0% 20 27.6 47.3 20.7 142.1 30.8
10.|-- cr2.iad3.inforelay.net 0.0% 20 20.7 41.8 20.7 203.1 41.7
11.|-- cr2.iad2.inforelay.net 0.0% 20 20.7 64.8 20.5 253.9 67.8
12.|-- ??? 100.0 20 0.0 0.0 0.0 0.0 0.0

--- mtr run 2
4.|-- ge-6-20.car1.Cleveland1.L 0.0% 20 158.5 66.4 11.8 176.5 51.2
5.|-- ae-2-4.bar1.Cleveland1.Le 0.0% 20 114.5 50.9 10.8 137.5 38.4
6.|-- ae-6-6.ebr1.Washington1.L 0.0% 20 96.8 71.2 19.2 191.2 54.0
7.|-- ae-81-81.csw3.Washington1 0.0% 20 58.3 77.9 18.1 163.8 54.6
8.|-- ae-32-80.car2.Washington1 0.0% 20 43.4 98.2 20.2 302.8 73.1
| `|-- 4.69.149.4
9.|-- CWIE-LLC.car2.Washington1 0.0% 20 120.2 77.9 20.4 153.9 54.6
10.|-- cr2.iad3.inforelay.net 0.0% 20 108.3 107.7 20.6 354.7 79.1
11.|-- cr2.iad2.inforelay.net 0.0% 20 77.3 120.1 20.7 244.8 57.2
12.|-- 66.231.180.84 0.0% 20 68.8 91.1 20.6 155.2 50.5
13.|-- https://www.furaffinity.net 5.0% 20 170.0 100.0 20.2 185.1 57.7

And we've been sending that information up to our hosts to troubleshoot. We're not making excuses, we're trying to find patterns to try to find out out WHY users are experiencing the issue.

Sorry if I may interrupt on here - but havent the recent traces you were probably squashed with shown the issue being InfoRelay or whatever that stuff is called like? I personally am getting a way different route than most people and thus have not any issue:

traceroute to furaffinity.net (70.33.186.196), 64 hops max, 72 byte packets
1 fritz.box (192.168.178.1) 2.398 ms 1.809 ms 2.243 ms
2 217.0.117.166 (217.0.117.166) 22.636 ms 55.251 ms 22.247 ms
3 87.186.196.130 (87.186.196.130) 40.392 ms 54.657 ms 38.784 ms
4 194.25.6.58 (194.25.6.58) 21.636 ms 45.305 ms 21.871 ms
5 194.25.211.134 (194.25.211.134) 25.486 ms 22.301 ms 22.100 ms
6 xe-10-3-2.was14.ip4.tinet.net (141.136.110.217) 110.375 ms 195.136 ms 140.809 ms
7 inforelay-gw.p4.tinet.net (216.221.158.246) 133.051 ms 210.771 ms 112.150 ms
8 cr2.iad1.inforelay.net (66.231.176.10) 143.968 ms 287.753 ms 207.544 ms
9 cr1.iad2.inforelay.net (66.231.176.246) 115.746 ms 136.592 ms 112.796 ms
10 66.231.180.84 (66.231.180.84) 125.802 ms 109.494 ms 110.651 ms
11 https://www.furaffinity.net (70.33.186.196) 133.992 ms 130.474 ms 136.789 ms

Most people got a pattern like cr{2|3}.iad{1|3}.inforelay.net. I assume its InfoRelay, which was strongly pointed out at the last journal.
...it smells like INfoRelay is just very slow in looking it up. It looks very much like some of the zonefiles are giving out issues - or in the worst cases your firewall is blocking out requests over that host - but I doubt that one honestly.
Prod InfoRelay, just a very honest suggestion.

That's because you're going through cr1.iad2.inforelay.net. Users on that router are not experiencing any issue. It seems to stem mostly from users solely coming in via cr2.iad2.inforelay.net.

Then go and smack that router and check the zonefiles and all that stuff?
In the worst case just redo it from the ground up if you have full control over it.

We do not have control over it.

Yeah, seeing the same thing here. Traceroute times out at the hop that would be 66.231.180.84 during the 'outages'.

I use Brighthouse on my PC and a combination of Brighthouse and AT&T on my tablet. It's been a crazy week.

I will get you traces from my mobile and home connections as I can.

still getting problems with BrightHouse here in florida

Same here and same location!

I literally haven't had any connection problems at all in a looong time.. its strange seeing so many people complain when it's working fine for me XD

ISP: Veracity (Utah only, we used to have Comcast at the apartment complex) To those having trouble copying/pasting CMD entries, you have to enable Quick Edit Mode for the Command Prompt in the properties. Highlight the text, press enter, then Control + V

C:\Users\PC>tracert furaffinity.net

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

1 4 ms 116 ms 2 ms 192.168.6.1
2 4 ms 8 ms 1 ms 66.7.119.1
3 5 ms 1 ms 1 ms 10.8.201.37
4 3 ms 2 ms 2 ms eth_3-3_prv02-rt02.veracitynetworks.com [97.75.190.166]
5 14 ms 4 ms 3 ms 97.75.191.66
6 6 ms 2 ms 4 ms 97.75.191.54
7 2542 ms 2 ms 3 ms te-9-3.car1.SaltLakeCity1.Level3.net [4.53.40.105]
8 55 ms 54 ms 57 ms ae-11-11.car2.SaltLakeCity1.Level3.net [4.69.133.122]
9 56 ms 54 ms 55 ms ae-5-5.ebr1.Denver1.Level3.net [4.69.133.126]
10 55 ms 58 ms 53 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.151.182]
11 58 ms 53 ms 67 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
12 55 ms 56 ms 54 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]
13 58 ms 53 ms 54 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145]
14 55 ms 56 ms 55 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221]
15 66 ms 55 ms 56 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154]
16 54 ms 56 ms 54 ms ae-32-80.car2.Washington1.Level3.net [4.69.149.132]
17 56 ms 58 ms 55 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.58]
18 58 ms 59 ms 58 ms cr2.iad3.inforelay.net [70.33.180.254]
19 60 ms 59 ms 58 ms cr2.iad2.inforelay.net [67.208.89.118]
20 59 ms 57 ms 57 ms 66.231.180.84
21 59 ms 59 ms 58 ms https://www.furaffinity.net [70.33.186.196]

Brighthouse/Time Warner

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 121 ms 159 ms 174 ms ten9-0-1.bham10-ser1.bhn.net [72.31.206.159]
4 149 ms 167 ms 151 ms ten8-0-0.bham01-ser3.bhn.net [72.31.206.140]
5 171 ms 191 ms 191 ms ten0-9-0-4-tamp20-cbr1.bhn.net [72.31.220.14]
6 93 ms * 163 ms 4.68.70.149
7 196 ms 202 ms 186 ms ae-5-5.ebr1.Miami1.Level3.net [4.69.148.213]
8 121 ms 152 ms 128 ms ae-1-100.ebr2.Miami1.Level3.net [4.69.151.254]
9 217 ms 207 ms 211 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
10 173 ms 204 ms 191 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]
11 231 ms 203 ms 172 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]
12 174 ms 248 ms 205 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.130]
13 176 ms 187 ms 238 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4]
14 186 ms 159 ms 187 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.58]
15 169 ms 214 ms 196 ms cr2.iad3.inforelay.net [70.33.180.254]
16 246 ms 391 ms 237 ms cr2.iad2.inforelay.net [67.208.89.118]
17 * * * Request timed out.
18 * * * Request timed out.

i'm not having any issues at all and you'd have to simplify traceroutes for me to understand.

My issue is more related to notes than just general browsing it seems.
I always always alwaaaaaays encounter problems when navigating to my notebox, itll take 30 seconds to 2minutes to load thenote inbox, and after that it fixes itself.
it happens when viewing images sometimes but about 90% of the time it's dealing with notes. which for a commission artist is a massive pain x_x

well here is my results it feel more choppy a my end also http://gyazo.com/17cabeea918faba28eef9622e0316af3
my network is 3 UK as i run off my HTC using a wifi hotspot as my router

I use Myqwest for my router and connection. I know its never given me trouble for FA until this last week.

Feel free to look at the note I sent yesterday (that went unopened) because I'm still having connectivity issues and my traceroute hasn't changed.

I use Level 3 Communications.

Mostly we have seen any delivery of Cogent through Verizon / MCI / Global crossing (yes, I know they are all the same) Has been shit. Cogent itself seems to be doing pretty good.

Note sent, but for me it is the same every time.
Times out at 66.231.180.84

Sent a note but forgot to include a service provider.
I'm on BrightHouse.

Sent in my Traceroute and ISP as a note. My ISP is CenturyLink (Was formally Qwest until the recent merger). Are many of the other users having problems Using CenturyLink?

me and ino have been having issues down here in the cities and we're connecting through centurylink as well

I half wondered if it was CenturyLink/Qwest as well. I cannot connect worth a crap. I used to be able to connect directly to their ip address, but that doesn't even really work for me anymore.

I sent the note with the trace route, this time I'm seeing 220ms pings at 4.59.156.5 CWIE-LLC.car2.Washington1.Level3.net

Well I don't have a problem with FA, I have a problem with our ISP trolling with us~


SBC Communications, Inc.
U-Verse V-DSL

This is the page I get a lot.

This webpage is not available
Google Chrome could not load the webpage because https://www.furaffinity.net took too long to respond. The website may be down, or you may be experiencing issues with your Internet connection.
Here are some suggestions:
Reload this webpage later.
Check your Internet connection. Restart any router, modem, or other network devices you may be using.
Add Google Chrome as a permitted program in your firewall's or antivirus software's settings. If it is already a permitted program, try deleting it from the list of permitted programs and adding it again.
If you use a proxy server, check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server, adjust your proxy settings: Go to the Chrome menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect the "Use a proxy server for your LAN" checkbox.
Error 7 (net::ERR_TIMED_OUT): The operation timed out.

My ISP is Brighthouse/Roadrunner High Speed

Still having the issues. Sent another note with the new tracert but it is the same as it has been the entire time, having issues with the 66.231.180.84 address.

use cableone for internet service att.net for email address

still having issues
sent note with tracert

isp is centurylink

Would not connect on Windows. Lost a few favorites. Used in an office. Was not my computer. Using my dads cell phone to write this. Loads very slowly on his iPhone.

Lost connectivity today for the first time ~ Using Century Link (don't use them they suck period oh my god)

I did just notice something worth mentioning, last time it stopped working for me, it started working again at exactly 5:00pm (-7 incase it really matters).

Well I'm not sure if the trace route thing needs to be run while the site can't be accessed/found by my computer's web browser ,example -> "oops! Google chrome couldn't find www.furaffinity.net/user/catboygamer/" <- end example. I'm not sure what the ISP company is, just what the name of the company that provides my internet. I think that the ISP is called different than the company name. but I'll send the info to Fender via a note like I'm supposed to once I get all of it.

correction on that what my google chrome says is "Oops! Google Chrome could not connect to www.furaffinity.net" with a list of suggestions "Suggestions:
Access a cached copy of www.­furaffinity.­net/­user/­catboygamer/­
Try reloading: www.­furaffinity.­net/­user/­catboygamer/­
Search on Google:"

right now for my end it runs alot better than last time... im not sure about the other users but, this incident is just freaking weird.

I'm tired of trying to help, and pointing out the problem like everyone else and then getting blatantly ignored.. good luck.

66.231.180.84 <- This IP.. your CISCO Router/Firewall (whatever it exactly is) is what's at fault. Also, here's something you may want/need to fix: Whitelist your own shit http://70.33.186.196/ ~ images don't load because the servers aren't talking due to whitelist/rules. But it's doubtful this info I'm giving you will be used, because everyone else who has said exactly this has been entirely ignored too. My ISP is Century Link. Also have this problem on AT&T Network, also have this problem on COX, also have this problem on COMCAST, and also have this problem on telenor (proxy).. to list some of the ISP's, I've used and had this fail from. I live in Tucson.

Not sure who my provider is; I'm on my cell phone through Straight Talk. The connectivity has been erratic...

Soooo I've sent two notes now and neither register being opened. Both had the info you requested in them. i'm assuming that just means you collected enough data already? hmmmm. Curious.

No, they just don't use it.. they've had countless people tell them exactly what the problem is, and they don't have anyone with more than two braincells who can figure out what to do.

^this. *nodnod* When will FA get that it's users are smart enough to know when they are being fed a line. Weasyl?

Sadly.. never..
http://www.furaffinity.net/journal/...../#cid:34413780

sigh* I left because the admins were playing disshonestly with me and others I saw. I came back because I realized this was where my biggest audience was, and then this. I hope they get it fixed, but I almost hope they don't, then another sight like Weasyl or So furry can have a go at this and hopefully learn from FA's mistakes (read: mismanagement)

Yeah, sadly it's just a bad move to completely leave FA due to the enormous userbase and clean simplicity of the site, as well as consistency. FA hasn't changed much in many years, its layout is still the same (good thing! UI overhaul/change is bad) but the crappy maintenance and administration hasn't improved enough to make any mention of, only a bit better with uptime, but given the current situation, I can only credit that to pure fluke.

The thing I dislike about some of the other sites is the clutter and overdone layout. FA does right by keeping it simple. Main profile, and then gallery/journal/scraps without overdone eye cancer or excessive navigation needed. I honestly think the prior site of YiffStar had a much better and simplistic layout that was clean and easy, like FA, in comparison to the new SoFurry. As for Weasyl, I have not actually made use of it or played around in it enough to give an informed opinion on how it compares. It's just hard to defeat something that has the largest userbase, especially if you have something radially different from what people are used to from the giant that everyone uses.

It takes my bf 30 minutes to load something on this site, and it's not on his side. :\

If I experience any more issues, I'll be sure to run a traceroute and send along my ISP name too.

I am using Time Warner from Erie, Pennsylvania, and everything has been working perfectly fine for me. Pages are loading pretty fast, ranging from nearly instant in the early mornings, to taking about five seconds during peak times. Also, my roommate accesses FA through an Android phone, and says it has been working well for him.

I hope the problem can be found for those that are affected.

i have sent two notes and neither of them have been opened. Is anything gonna fix this connectivity issue?

Trace from my mobile connection: Verizon Wireless
Tracing route to furaffinity.net [70.33.186.196]
over a maximum of 30 hops:

1 3 ms 1 ms 2 ms 192.168.1.1
2 279 ms 40 ms 33 ms 180.sub-66-174-175.myvzw.com [66.174.175.180]
3 44 ms 32 ms 29 ms 82.sub-69-83-57.myvzw.com [69.83.57.82]
4 93 ms 45 ms 46 ms 113.sub-69-83-57.myvzw.com [69.83.57.113]
5 152 ms 35 ms 29 ms 162.sub-69-83-57.myvzw.com [69.83.57.162]
6 61 ms 114 ms 58 ms 36.sub-69-83-34.myvzw.com [69.83.34.36]
7 162 ms 83 ms 48 ms 65.sub-69-83-33.myvzw.com [69.83.33.65]
8 59 ms 67 ms 37 ms ae51.edge4.Atlanta2.Level3.net [4.30.236.29]
9 * * * Request timed out.
10 * * * Request timed out.

Wildblue it only happens with FA come and goes every 15 minutes

I was having that problem, FA crashing and stopping mid-load...
... then I deleted all FA cookies, relogged, and apparently is no longer failing XD;

Wel, I was wrong, took like 45 mins but the issues are back again |3

Hope this helps. It is from earlier today, 6-25-13.
*** Willysilver ***

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

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

1 6 ms 2 ms 2 ms qwestmodem.domain.actdsltmp [192.168.0.1]
2 43 ms 43 ms 44 ms 207.225.84.231
3 43 ms 43 ms 56 ms ptld-agw1.inet.qwest.net [207.225.86.49]
4 46 ms 49 ms 56 ms sea-brdr-02.inet.qwest.net [67.14.41.18]
5 47 ms 49 ms 50 ms 208.173.49.93
6 48 ms 55 ms 53 ms msr1-te-0-5-1-0.sea.savvis.net [206.28.98.174]
7 135 ms 103 ms 104 ms cr1-te-0-5-0-2.den.savvis.net [206.28.96.185]
8 112 ms 115 ms 111 ms cr2-tengig-0-7-0-0.chicago.savvis.net [204.70.19
6.246]
9 133 ms 133 ms 135 ms 206.28.96.161
10 135 ms 136 ms 137 ms msr1-tengig-0-3-0-0.Washington.savvis.net [204.7
0.196.98]
11 134 ms 131 ms 136 ms 204.70.206.77
12 132 ms 133 ms 136 ms dca1.inforelay.net [208.173.12.130]
13 134 ms 133 ms 132 ms cr2.iad3.inforelay.net [67.208.76.5]
14 226 ms 213 ms 209 ms cr2.iad2.inforelay.net [67.208.89.118]
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 * * 136 ms sfw.furaffinity.net [70.33.186.196]

Trace complete.

It is always after tracert 15. Always, mine too.

That's like saying that every destination is 15 intersections away from everyone's house.

think of the readout like google maps giving you turn by turn directions

Still having this issue via Phone.Using T-Mobile. Is there a way to Trace through the phone?

I sent a new note, PLEASE LOOK AT IT THIS TIME! My last one has yet to be looked at...

That's okay, mine probably hasn't been looked at either.

The one I sent a few years ago wasn't.

Here's the link for those who missed it, for my site for checking if FA is up:

http://isfaup.tk/


and to see if your uptime and mine match!

http://isfaup.tk/bargraph.html


Lemme know what you think.

Kurin's site matches my connectivity exactly.

Also, you might want to adjust the graph's time period to be the last 12 hours or something otherwise the graph will eventually become microscopic.

Will do!

I've included some information Fender had just given me in the main page, which seems to be a consistency between each person's traceroute.

http://isfaup.tk/

They match exactly, but what does this indicate?

They match exactly, but what does this indicate?

Bitchin' awesome! Now if only someone could put your program into a browser plugin/extension and set it to send graph results to an email address... and maybe optionally play a sound when FA is back up.

Now that I think of it, allow the user to enter geographical and ISP info. too to send off in the email reports.

Uh Oh, you got a couple divide by 0 errors developing on http://isfaup.tk/bargraph.html

Fixed the divide by zero errors! Thanks! Was caused by the fact that there were no up/down rises/falls. So made a case for that (I hadn't thought my code all the way through!)

It's been nearly two weeks, maybe more.

So what i do, when I am posting a reply, is, I have a tab open with the home page on it.

I have a tab open with the reply.

before I hit "Submit", I refresh the page with the home page on it.

If it refreshes okay, I am usually okay to post the reply.

If not, I wait a few minutes, and then the site works again.

I have Cable-One in AZ. Tracert submitted.

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

C:\Users\lito>tracert https://www.furaffinity.net

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

1 2 ms 1 ms 1 ms clearmodem [192.168.15.1]
2 * * * Request timed out.
3 107 ms 84 ms 79 ms 10.41.29.197
4 78 ms 78 ms 79 ms 66.233.161.161
5 114 ms 78 ms 100 ms xe-8-3-0.bar1.Tampa1.Level3.net [4.53.172.5]
6 148 ms 169 ms 114 ms ae-5-5.ebr1.Miami1.Level3.net [4.69.148.213]
7 97 ms 114 ms 119 ms ae-1-100.ebr2.Miami1.Level3.net [4.69.151.254]
8 157 ms 119 ms 143 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
9 121 ms 169 ms 104 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]

10 117 ms 114 ms 119 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

11 116 ms 114 ms 109 ms ae-91-91.csw4.Washington1.Level3.net [4.69.134.1
42]
12 156 ms 114 ms 114 ms ae-42-90.car2.Washington1.Level3.net [4.69.149.1
96]
13 117 ms 124 ms 194 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
14 132 ms 114 ms 128 ms cr2.iad3.inforelay.net [70.33.180.254]
15 125 ms 198 ms 178 ms cr2.iad2.inforelay.net [67.208.89.118]
16 119 ms 113 ms 114 ms 66.231.180.84
17 121 ms 119 ms 129 ms https://www.furaffinity.net [70.33.186.196]

Trace complete.

C:\Users\lito>

I don't always have issues with connecting but do have issues so time the site being a bit slow, other then that it is fine on my end.

I done a bit of reading and seen a comment where the problem started when the ISP sent the admins a note about a config change. Then all hell broke loose, but the ISP hasn't fixed it. ISP that encounter this would have immendelly rolledback the config change. The one comment from the admin about the ISP saying it was an DNS IP problem. Just about everybody called BS on that one and only comferms a theory about this. Take your favorite three letter USA agensity that forced some hardware onto the ISP. And of course, they messed up things for the ISP. I wish I was a crazy tin foil kook. But after seeing what is happing in the USA now, this may have in fact happend considering the BS that the ISP is telling the site admins.

The data gather to ban "Evil Assault Furries" has begun...

Still timing out on 67.208.89.118

qwest DSL in minneapolis mn

still doing it

Stupid connection! I triple posted....sorry!

I unfortunately can't take traceroutes with my phone, which is the only device I have issues on. When I'm connected via 4G on t-mobile I get 504 errors like 85% of the time, even if I have full bars and all other websites work fine =/

Still having problems. Down about 50% of the time on ~5minute intervals. Kurin's little website thing http://isfaup.tk/ is matching my experience exactly. My ISP is Centurylink, which has a packet path that goes through cr2.iad2.inforelay.net [67.208.089.118]. This seems to be the common denominator of everyone who's having problems.

Mine seems to be working again ^^

Mines not letting me or anyone else with a new account upload or change our avatars either

Mine keeps lagging so much every few successful loaded pages it kicks me to this "server cannot be contacted" type page and after a few reloads the process repeats again and again

In my entire time with FA it's never taken me more than 10 seconds to load a page, except back when there were issues, and it took 20 or 30 seconds. And i'm all the way up in Canada. According to the traceroute, i'm 11 hops, a skip, and a jump away from FA :p

BTW, its the NSA metadata tools that are slowing us down. They need it to pass a law banning evil "Assault Furries". 8-P

On Charter and have been connecting normal as ever, it's FA's Isp clearly.

I use Centry Link, and my tracet won;t copy and paste.

ctrl + c

ctrl + v

I did that on my own, and it still didn't work.

Usually works for me to copy the active window's entire contents.

I couldn't tell ya why it didn't work.

Enable Quick Edit Mode in the CMD properties, highlight and then ctrl v

Yeah, I'm pretty sure we're never getting that new UI.

Just wanted to say real quick, I'm up over in MI and I haven't really been having any problems besides a few times when I have connectivity issues, however re-loading the page gets me back up with no problem, nothing takes over a minute to get back on. I know it's probably not relevant, but just wanted to throw this up there.

I wish you guys all the luck in finding/fixing what's up!

I'm using a tablet so I can't get a proper trace result but no matter what device I use, FA still takes a long while to load though most of the time I fail to load a page. When I finally do, if I'm lucky I can browse maybe 2-5 pages before it takes a long time to load then just simply goes to the "Cannot load because it took to long for the servers to respond" or w/e.

All I can say at this moment is that I'm around Denver and I use the oh so f****** wonderful ISP, Century Link -.-

BLAH! That is all..

i tried to run that tracert thing and it would let me copy it

Drop them. They obviously can't fix their shitty load balancing or firewall proxy.

Those unable to copy and paste. Right click, and select mark. Drag and highlight with left mouse. Right click again. Paste where you need.

My FA goes away at random times.

I can't trace from my phone (at least to my knowledge) but I still only have the problem when I'm on a Brighthouse network. FA is fine on my Sprint network, home Knology wifi, and school wifi (unknown ISP), but the SECOND I connect to the Brighthouse connection at my boyfriend's OR neighbor's house, FA IMMEDIATELY begins throwing timeout errors. It does this several times an hour, but I have yet to have the problem on the aforementioned knology, home, or school networks.

Using CenturyLink in NM.
Connection went bad on June 15th and is still doing the on-again-off again shuffle.

I use Brighthouse haha.
Its not letting me to a traceroute for some reason. Its saying it can't connect to the IP or something.

Seems like you guys are doing pretty good with keeping these update journals coming. I'm impressed, and I hope it continues this way. Good job!

I have just given up and started running a proxy to my box at work to use FA. It does not take this long to fix routing. I know its my job IRL. >.<

the firewall at norms blocks this site...

my work content filter has this site categorized....(i'm the network admin)

I was so puzzled; for the past five days, I could access the site, but just not log in - I kept thinking "maybe the login stuff is the only part unreachable".

Then I finally realized: I WAS USING THE WRONG PASSWORD!

Dang... Had trouble even getting pages to load for the past two hours. Up and down so much.

http://isfaup.tk/bargraph.html Matches my experience. I use CenturyLink. I... ahem... access FA from another location that uses Optimum and there's NO connection problems there.

this is he first time its semi worked all day. I hope this gets fixed real soon, seriously....

bright house

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert https://www.furaffinity.net

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

1 <1 ms <1 ms <1 ms
2 * * * Request timed out.
3 8 ms 8 ms 6 ms 72-31-237-41.net.bhntampa.com [72.31.237.41]
4 18 ms 23 ms 11 ms ten0-10-0-4.tamp27-car1.bhn.net [72.31.209.106]

5 14 ms 11 ms 12 ms ten0-11-0-2.tamp20-car1.bhn.net [71.44.3.4]
6 10 ms 15 ms 16 ms hun0-1-0-0-tamp20-cbr1.bhn.net [72.31.117.158]
7 8 ms 8 ms 7 ms 4.68.70.149
8 35 ms 45 ms 36 ms ae-5-5.ebr1.Miami1.Level3.net [4.69.148.213]
9 37 ms 37 ms 39 ms ae-1-100.ebr2.Miami1.Level3.net [4.69.151.254]
10 41 ms 36 ms 37 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
11 38 ms 37 ms 36 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]

12 37 ms 43 ms 35 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

13 60 ms 36 ms 39 ms ae-61-61.csw1.Washington1.Level3.net [4.69.134.1
30]
14 130 ms 75 ms 42 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4
]
15 39 ms 40 ms 39 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
16 79 ms 39 ms 39 ms cr2.iad3.inforelay.net [70.33.180.254]
17 39 ms 39 ms 40 ms cr2.iad2.inforelay.net [67.208.89.118]
18 38 ms 41 ms 45 ms 66.231.180.84
19 40 ms 39 ms 38 ms https://www.furaffinity.net [70.33.186.196]

Trace complete.

C:\Documents and Settings\Administrator>

I can't even get to fa to run this test on my pc

Brighthouse

Florida

Windows 7

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

1 29 ms 28 ms 19 ms 173-169-32-1.res.bhn.net [173.169.32.1]
2 10 ms 8 ms 9 ms ten0-0-0-3.tamp81-ser1.bhn.net [65.32.36.234]
3 14 ms 11 ms 23 ms ten0-12-0-1.tamp20-car1.bhn.net [72.31.2.220]
4 17 ms 15 ms 23 ms hun0-1-0-0-tamp20-cbr1.bhn.net [72.31.117.158]
5 * 11 ms 8 ms 4.68.70.149
6 39 ms 39 ms 40 ms ae-5-5.ebr1.Miami1.Level3.net [4.69.148.213]
7 41 ms 49 ms 40 ms ae-1-100.ebr2.Miami1.Level3.net [4.69.151.254]
8 36 ms 39 ms 49 ms ae-2-2.ebr2.Atlanta2.Level3.net [4.69.140.142]
9 41 ms 41 ms 38 ms ae-73-73.ebr3.Atlanta2.Level3.net [4.69.148.253]

10 40 ms 38 ms 41 ms ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

11 39 ms 42 ms 37 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.138]
12 40 ms 38 ms 38 ms ae-32-80.car2.Washington1.Level3.net [4.69.149.132]
13 41 ms 42 ms 42 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.58]
14 43 ms 60 ms 42 ms cr2.iad3.inforelay.net [70.33.180.254]
15 76 ms 43 ms 49 ms cr2.iad2.inforelay.net [67.208.89.118]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * 38 ms https://www.furaffinity.net [70.33.186.196]

Trace complete.

Using a Comcast ISP, still can't upload anything.

I could be mistaken but FA hasn't crashed for me yet tonight ^_^ was having problems.

Cableone is my ISP

I thought at first it was just them being bonky, but then finally was able to connect to FA after, like, a full day or so, and saw this. Chaos! xD

Still spotty for me.

My ISP:
Exede

Message I Keep Getting (using Google Chrome):
The connection to https://www.furaffinity.net was interrupted.
Check your Internet connection.
Check any cables and reboot any routers, modems, or other network devices you may be using.
Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.
If you use a proxy server...
Check your proxy settings or contact your network administrator to make sure the proxy server is working. If you don't believe you should be using a proxy server: Go to the Chrome menu > Settings > Show advanced settings... > Change proxy settings... > LAN Settings and deselect "Use a proxy server for your LAN".
Error code: ERR_CONNECTION_RESET

Traceroute Info:
I can't get anything. It gets to about 17 or 18, then quits on me. -.- So I cannot supply much more. =X

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

C:\Users\Lori>tracert https://www.furaffinity.net

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

1 * * * Request timed out.
2 647 ms 675 ms 680 ms 10.73.101.1
3 658 ms 688 ms 671 ms 10.73.10.2
4 677 ms 719 ms 684 ms 10.73.255.249
5 664 ms 838 ms 661 ms te-1-4.car1.SaltLakeCity1.Level3.net [4.53.40.37
]
6 707 ms 720 ms 720 ms ae-11-11.car2.SaltLakeCity1.Level3.net [4.69.133
.122]
7 717 ms 717 ms 720 ms ae-5-5.ebr1.Denver1.Level3.net [4.69.133.126]
8 715 ms 719 ms 721 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.151.182]

9 717 ms 718 ms 720 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
10 716 ms 719 ms 1198 ms ae-1-100.ebr2.Chicago2.Level3.net [4.69.132.114]

11 718 ms 683 ms 679 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.14
5]
12 674 ms 677 ms 684 ms ae-5-5.ebr2.Washington1.Level3.net [4.69.143.221
]
13 719 ms 718 ms 720 ms ae-62-62.csw1.Washington1.Level3.net [4.69.134.1
46]
14 712 ms 759 ms 721 ms ae-12-60.car2.Washington1.Level3.net [4.69.149.4
]
15 720 ms 719 ms 718 ms CWIE-LLC.car2.Washington1.Level3.net [4.59.156.5
8]
16 718 ms 718 ms 718 ms cr2.iad3.inforelay.net [70.33.180.254]
17 716 ms 717 ms 722 ms cr2.iad2.inforelay.net [67.208.89.118]
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.

C:\Users\Lori>

i cant seem to highlight anything on that program for windows, and then it disappears. not sure how i'm supposed to give you the info if it does that.

if your windows, right click select all then enter. Enter copies it

right click does nothing. it's one of those windows where its only black with white/gray letters, so only keystrokes do anything, but that doesn't even do anything. and again, the window disappears after it gives up trying to trace the last isp/hop or whatever.

Open the command prompt (cmd) first, and THEN run tracert.

ah this helped, thanks

...maybe i should not try doing stuff like this when i'm half asleep so i FOLLOW INSTRUCTIONS. -_-