Seems to work fine for me (I was affected the last time).

All delayed with similar results from the earlier tracert.

That is probably a proxy re-routing SOME of us and i'm ready *again* to pull out the arsenal against these servers wherever they are and by whomever they are operated.

Could you please re-post the tracert's zyx, so taht we have something in our hands?

Tracing route to i-mod-productions.com [87.118.120.11]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
  2    24 ms    24 ms    29 ms  10.32.163.1
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5

______________________________________________________

Tracing route to 193.22.254.200 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
  2    23 ms    23 ms    24 ms  10.32.163.1
  3    23 ms    23 ms    24 ms  130.81.12.173
  4    24 ms    23 ms    23 ms  as0-0.NY325-BB-RTR2.verizon-gni.net [130.81.20.1
78]
  5    25 ms    24 ms    24 ms  0.so-4-3-0.XT2.NYC9.ALTER.NET [152.63.10.5]
  6    24 ms    23 ms    23 ms  0.so-3-0-0.IL4.NYC9.ALTER.NET [152.63.23.177]
  7    26 ms    26 ms    25 ms  so-1-0-0.IL2.NYC12.ALTER.NET [146.188.15.1]
  8   113 ms   112 ms   112 ms  so-2-3-0.XT1.FFT1.ALTER.NET [146.188.3.202]
  9   114 ms   113 ms   112 ms  so-0-0-0.CR2.FFT1.ALTER.NET [146.188.15.194]
 10   113 ms   112 ms   113 ms  POS1-0-1.GW2.FFT4.ALTER.NET [149.227.17.226]
 11   124 ms   111 ms   110 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12   113 ms   113 ms   113 ms  ffm-145-254-16-73.arcor-ip.net [145.254.16.73]
 13   109 ms   109 ms   109 ms  92.79.213.5
 14   108 ms   109 ms   108 ms  ffm-145-254-1-10.arcor-ip.net [145.254.1.10]
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.

Thanks Dave.

Détermination de l'itinéraire vers ns.i-mod-productions.com [87.118.120.11]
avec un maximum de 30 sauts :

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2     *        *        *     Délai d'attente de la demande dépassé.

Same with all IP suggested.

Thanks Zyx, Keyweb is watching this thread

Dave, you live in NY, right? I need to know the state you are living in. Thx.

yeah, NY

Okay. Let's see what Verizon is good for

Quote (Keyweb):

"Nach einem ellenlangen Gespräch musste mir die Dame vom Support leider mitteilen
dass sie an die Technik nur mit der Anschlussnummer eines betroffenen Teilnehmers
eine Anfrage öffnen kann, es ist nicht möglich direkt eine Anfrage an die Technik
dort zu schreiben   

Könnten sie den betreffenden User im Forum bitten, ob er eventuell bie Verizon
direkt sich melden könnte und da eine Anfrage zwecks den betreffenden IPs öffnen könnte?"

Translation:

"After a long chat, the women from the support told me, that she can only open
a ticket for the technicians with the access-number of the affected attendee,
it is impossible to make a request to the technician there directly 

Could you ask the affected user in the forum, if he could address
himself directly to Verizon to open a request related to the affected IPs?"

So could you please inform Verizon about your problem with that reference, Dave?
You may do the same Zyx.

Sincerly,


-Sven

EDIT: I'll be away for the next 1 1/2 weeks, but I try to use some time at the weekend to be
online here.

Now that the holiday weekend is over, I sent a help request email along with a link to this forum to Verizon.  I'm again unable to access the site and I'm hoping Verizon might be able to help.  I'll post here with any helpful replies they send me.

On a somewhat related note, does anyone know of a fix for the tech tree viewer?  The problem I'm having is that it now will not read a mod's tech tree, it simply lists, "Dummy QTreeWidgetItem" where the race list should be.  Then, when I exit, it says errors have occurred and to check the logfile.  I've tried uninstalling and reinstalling the viewer but no luck.

Thanks for any help.

I was working with Verizon support today who was actually helpful.  It was strange because he was able to access the site with no problem but my two systems in the house weren't able to.  He said I have one of the newer IP addresses and routers for FIOS which could be causing a couple problems.  We narrowed it down to being either an issue with the firewall in the newer model routers (since my tracert fails immediately) or something a Verizon Network Technician will have to fix on their end that's affecting only the newer IP addresses.

I wasn't able to hook up my system directly to the ethernet today because it's a huge hassle with how my house is set up and I'm too tired after work to mess with it today.  I'll test it out in the next couple days which should narrow it down to which one is the problem.  For some reason, I doubt it's the firewall (we set it to low, it has no off).

tell him it has nothing to do with the new router. I have verizon too and my router is a few years old.

Any news yet?

Sorry about that, I was away this weekend so didn't have the chance to follow up with Verizon.  I did complete the test they asked and it has to be something their Network techs will have to take a look at.  I'm on hold to update Verizon with the results right now.

Edit: Ok, this new guy says Verizon is not blocking any sites or contents.  He suggested that either the sites new DNS has not been updated in all the databases since it was changed recently or I can use opendns.  I'll give the opendns a try, he gave me a link for www.opendns.com.  Trouble is, the directions there don't match my router so I'm trying to figure it out on my own since Verizon said they don't support that.  He did say that it poses no security risk.  I'll keep you guys posted.

Edit: Well I figured it out but opendns isn't working for me.  I made sure I flushed my dns cache after every setting I tweaked.  I'm at a loss as this networking nonsense is a bit crazy for me lol.  I can't even ping i-mod and it looks like Verizon is now bent on passing blame back to i-mod.  I'm not sure it's worth all the trouble for you guys at I-mod to try to figure this out if just a few of us can't access, especially if it's a problem on Verizon's end and they just want to be lazy about it (quite possible).

Same with Bell.ca Toronto here.

It's either localized Vista flaws or some of our ISP providers are redirecting bandwidth(s) allocations to a guilty NY state server (and possibly, even more) which has been blocking us all in an attempt to find illegal proxies. They're even getting ready for the border passports gimmick and that in itself shows me how much collectively paranoid the USofA has become. Homeland security or not, they're putting up monitoring junk on the web just to track out anyone who connects TO them.

That's the diagnostic i made plenty of times before and it still stands unless proven otherwise.

That sounds likely Zyx.  We've been hearing alot in USA lately about national cyber security so wouldn't surprise me if they're tweaking things with unwanted side effects.  Believe me, the news here promotes so much paranoia it gives me a headache watching the stuff.  It's always funny just before summer hits and you get the rush of shark attack reports and safety tips.  Fear the beach! lol.

Anyways, only other thing I can add is I doubt it's an OS issue as I'm running XP pro 32 bit if you're running Vista.

Edit: By the way, I fixed the tech tree viewer problem, I must have messed something up when I was editing and it wasn't reading properly.  I reverted to the originals for the mod and it's up again.  I'll have to be more careful.

Could you please check if your support (especially Verizon) can connect to the following IP's?

193.22.254.201
87.118.22.104
95.169.160.38
84.19.188.171


After you could ask if "BGP AS 31103" is available in their routing-table.

-S.

as of last night, i can connect to the site again.

As do i... will it last though?

One thing is certain, i am very curious as to what exactly was responsible for this whole mess. So, Sven or Stefan, care to theorize on or admit what went wrong at keyweb or otherwise?

Nice, I'm connecting as well now.

We don't know - KeyWeb told me, that they did not do anything, so they exclude that the problem was on their side.

Anyways, Verizon verisimilar isn't going to tell what happened exactely.

-S.

Sure, name another big corporate freak such as Verizon which would admit making & causing such a stupid error on their (or anyone's) servers. Whomever looped up redir gimmicks on the web is one more virtual idiot that scrambles flow of communications for illegal reasons.

Mirror this spammers, you flood fiberwires with junk and when the people catch up with anarchy you'll regret every attempts at sabotage with boredom in jail time to teach a tough and definitive lesson; criminals are kept faaaaaaarrrrrr away from society for good reasons & for as long and often as it takes.

It's not better security we need, it's retaliation by repression.

I know a few hackers, want their locations as of this hour of the day?

Okay i still don't know what is happening but i can not get on at home.